CRITICAL SECURITY VERSION UPDATE:
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
admin
About
- Username
- admin
- Joined
- Visits
- 8,800
- Last Active
- Roles
- Administrator
Comments
-
Thanks for the report. I've pushed a fix for that branch: https://github.com/daylightstudio/FUEL-CMS/commit/8e733bbcf5378bdbcd7e7fc1df391148c14c0d0c
-
Thanks for posting that. It appears to be an issue with using the render_format = 'divs'; I've posted a fix under the develop and 1.4_dev branches: https://github.com/daylightstudio/FUEL-CMS/commit/10b7c5ec28270b113fff4d26390fd750f12f5603
-
Can you post your form_fields method?
-
What about giving it a different name of "purchase_year" and then in your list_items method you check for that in the query string parameters: public function list_items($limit = NULL, $offset = NULL, $col = 'completed', $order = 'desc', $just_coun…
-
Thanks for the report a fix for this has been posted in the develop and 1.4_dev branches.
-
You can set the "value" parameter to be the array of selected checkbox values (e.g. 1, 2, 4, 8, 16...etc). This may mean that in the form_fields method you need to create that array since by pulling in the values from that field since it won't be in…
-
The Fuel::$settings error is a bug. I've pushed a fix for that to the develop branch and the 1.4_dev branch.
-
What version of PHP are you running? I've seen this issue with a specific version of MAMP and iconv before. Do you have other PHP environments you cant test it in?
-
If it is just the iframe HTML, this sounds like the xss_clean function may be doing that. By default, modules will run that function to sanitize input. To remove that, add the following to your module's config in MY_fuel_modules.php: 'sanitize_inpu…
-
It may be helpful to debug what that actual query is. To do so, go to the fuel/modules/fuel/models/base_module_model.php around line 327 in the list_items method and uncomment the line that has: //$this->debug_query(); Let me know if that sheds a…
-
What are you seeing instead for the label?
-
Is this for a module form? If so, what version of FUEL are you running? I'm not able to replicate the issue.
-
Filtering on the has_many relationships is a little tricky. It requires joining and filtering on the fuel_relationships table. I would recommend doing the following 3 things: 1. Add the following to your fuel/application/config/MY_fuel_modules.php u…
-
Think I found the issue and posted the fix in the develop branch.
-
Pushed update to develop branch for label_class
-
Good idea!... I'll look into adding that to the dev branch here shortly.
-
Here is some more information on customizing how the search filters for your model: http://docs.getfuelcms.com/modules/simple#filtering
-
FUEL will not automatically do the foreign_key relationship and will skip any fields that end with _id when determining the default display_field (if it is not specified in the MY_fuel_modules.php config). To do the foreign_key relationship, I usual…
-
Are you perhaps referring to the "display_field" field instead?
-
I think what you may be missing is the "styles" parameter for the surrounding li element for products which can be done as follows: <?php echo $nav_arr = fuel_nav(array('depth'=>4 ,'render_type' => 'basic' , 'group_id' => 1 ,'container_…
-
What does it look like if you download the navigation from the CMS (there is download button in the list view)?
-
What is the menu configuration (either at fuel/application/views/_variables/nav.php or in the CMS)?
-
Hmm... if you debug fuel/modules/forms/Fuel_forms.php around line 747 does it have the name of the function? I tested the method above and it seemed to work OK for me. $this->call_hook('post_process');
-
Change the fuel_mode property to 'auto' in fuel/application/config/MY_fuel.php: $CI->fuel->config('fuel_mode') == 'auto'; This will change it to a text field for you to enter in the location you want.
-
That embed API looks interesting. If you do plan on implementing perhaps your own Dashboard with this, I'd love to see it.
-
To use a hook, you can do the following: 1. Create a hook function and place it your fuel/application/helpers/my_helper.php like so: function my_form_post_process($form) { $form->email_subject = 'This is a TEST!!!'; } 2. Then in your fuel/appli…
-
I imagine that the output is being presented somehow in a view file. Does it work if you wrap it with the following in your view file: <?php echo $CI->fuel->parser->parse_string($site_hoze->content);?>
-
$data = array('fullname' => $name, 'password' => $password); $str = $this->fuel->parser->parse_string('my_template', );
-
I just realized that above you said that's what you had in your view? By default, FUEL will not parse template tags in your view files. It will parse content from the database for the content field since you specified the $parsed_fields.
-
The second parameter for parse_string should be an array of data to pass to the template string and not the boolean.