Perhaps instead of "1" you could pass the name of the field in the "delete.pdf" field and then you can access that value in the normalized_save_data model property in your hook.
That is currently possible to do if you create the corresponding permissions {module}_{permission_type}) in the permissions module.
We'll look into the create permission as well. It's a little tricky because of how related create and edit are (you …
Another option could be that your link submits the form (would require using javascript):
$(function(){ if ($('.my_delete').click(function(e)){ $('#delete_pdf').val('1'); $('#form').submit(); } });
Then in the model, y…
The close button and new window will be separated in the next release. Having it so close together to the inline editing bar was an issue for me too. Removing the bar is a little trickier and will have to think about that some.
Perhaps you can use a little bit of javascript and some ajax. You can create the javascript file and associate it with the module using the "js" parameter in your fuel/application/MY_fuel_modules.php config. Then, if you specify a method on your mod…
If you look at the fuel/modules/fuel/config/fuel_moduels.php and look at the pages module config, you'll notice a similar array syntax. Instead of "/" though there are "_" and there is a no distinction between creating and editing but there is a per…
Actually, the documentation is correct (I can see where it's confusing). fuel_edit() won't actually output the value, it just places the inline editing markers and by default will look at the pages module (which is why you only see 2 parameters pass…
This is a bit difficult to do because of the hybrid nature of FUEL CMS and that not everything needs to be stored in the database. The fuel/application and assets directory needs to be unique fo every instance with there own database. The other fold…
You'll probably want to add a 'js' parameter to your module that includes all the javascript files required for the auto suggest. The value can be an array or a string with a comma in between each file name. By default, it will look for javascript f…
This looks to be a bug in the fuel/modules/fuel/controllers/module.php on line 1028 or so. It's hard coded '.id' for the field to query on and it should be the primary key field which for the blog users is fuel_user_id. Try changing that line to the…
You can access that value through the "normalized_save_data" property of the model. This is the data that get's passed to the model to save before it get's cleaned:
function on_before_save($values) { if (isset($this->normalized_save_data['n…
Sometimes you get that error if you have a space or return after a closing ?> tag in one of your libraries or helper files. It may be a difference in your versions of PHP as to why it's now showing on your Mac.
I found some stuff in this front end library to be helpful for detecting the appropriate language to serve up.
http://codeigniter.com/wiki/Language_Selection_2
It looks at the URI segment, then a cookie value, then checks the accept header value to…
Use $2 instead of $1 because there are 2 sets of parenthesis. That error message is a bug (that will be fixed in next release). The fix is:
if (!empty($fuel_path[1])) { require_once(FUEL_PATH.'/controllers/'.$fuel_path[1].'.php'); $class = $fuel_…
There currently isn't a javascript language variable used by BaseFuelController (e.g. jqx.config.lang). Perhaps you could create a hidden field in your model's form_fields method that could be accessed by the javascript:
_initDatePicker : function(…
The slated next version will have an updated version of CI which contains the library. With regards to a place for discussing FUEL's development, the forum is currently the place for that. We have been working a lot on the next release which is a dr…
I don't think you are wanting to call parent::form_fields(); more then once like you are for all the $fields_2. It sounds like what you are needing for a dropdown would be something like this:
public function form_fields($values = array()) { $field…
You can also try adding the following to the fuel/modules/fuel/assets/js/editors/ckeditor/config.js
CKEDITOR.editorConfig = function( config ) { protectedSource: [/\{[\s\S]*?\}/gi, /<\?[\s\S]*?\?>/g] };
How are you accessing it in your view? Are you using the object "$this" or the object "$CI". They both represent the same thing but "$CI" is probably what is available for you.
1) There is JSON on the page to return language specific stuff but that's probably not what you are needing. If you are needing JSON for your forms, consider adding that logic in the form_fields method perhaps using an after_html parameter on a fiel…
If you want the button to appear on the list items screen you can add the "list_actions" property to your simple module like so (example is taken from the navigation module):
'list_actions' => array('navigation/upload' => lang('btn_upload'))
…