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
-
The error wouldn't appear in the get_errors method. You may want to try and replicate the "is_allowed_dimensions" method on the Upload class.
-
Try using this in the controller instead (the documentation needed to be updated it looks like in the new User Guide gocs which I just pushed). // set your variables $vars = array('page_title' => 'Contact : My Website'); //... form code goes he…
-
This sounds like you are trying to render a page created in the CMS witha a controller correct? If so, this may help explain how to do that: http://www.getfuelcms.com/user_guide/general/creating-pages#controller
-
To get rid of the Upload image button you can add the following to your form_fields method: unset($fields['image_upload']); To not insert the data upon image upload error, you would need to do some validation on the image using the $_FILES array and…
-
We are awaiting the rumored 3.0 release to see how it effects integration. The latest CI release actually breaks some stuff with the queries. I looked on the issues and it appeared others were having a similar issue so we felt it best to await the 3…
-
The CI "db" object is part of the model just like a normal CI model. How were you calling it?
-
I believe the problem has to do with the xss_clean function being ran on the content before savign. Try adding this to your MY_fuel_module.php configuration which will remove the xss_clean filter: 'sanitize_input' => array('template','php'),
-
Check out the 1.0 beta branch and User Guide for more info: https://github.com/daylightstudio/FUEL-CMS/tree/1.0 https://github.com/daylightstudio/FUEL-CMS-User-Guide-Module
-
In order for it to work correctly, the records need to be an array of objects instead of an array of arrays. To make it an object, you must have a "Testimonial_model" (note no "s" after Testimonial) which extends Base_module_record. The class can be…
-
Try adding the $parsed_fields class property to your model. It should be an array of the field names you want to parse. If you use the "_formatted" magic method, you should include that in the list as well. Example: public $parsed_fields = array('co…
-
You can use the "on_before_delete" method hook on your model to check. The blog_categories_model does this so it doesn't remove the Uncategorized category.
-
By default, it will use the 3rd column for a dropdown. However, you can overwrite your options_list method to use a different column like so. The navigation_model does this to some extent.
-
Try the following for $foreign_keys: public $foreign_keys = array('fuel_navigation_id' => 'navigation_model');
-
The Base_model_record just extends the Data_record class and adds a few extra methods used for parsing field information (translating from Dwoo templating syntax). When in doubt, just use the Base_model_record.
-
When you say latest, you mean the latest from the master branch I'm assuming. If so, then there shouldn't be any need to update the database. The 1.0 branch does however, some database changes.
-
Out of curiosity, what was the scenario in which you needed to have an action on creating a record?
-
By default, you need to be logged into the CMS to see the user guide. Also, you may want to check your MY_fuel.php to see if "user_guide" is in the list of "modules_allowed". For markup, you can use the "code" tag.
-
Unfortunately, that is not supported at the moment. Although, it could be easily changed in the fuel/modules/fuel/views/_blocks/module_create_edit_actions.php file so that it is not inside the if condition that checks that the action is "edit".
-
Does changing the item_actions (not "list_actions" or "table_actions") and adding the "others" key not work for you?
-
Adding fuel_set_var should remove the layout. Are you sure it is pulling in that particular page? I noticed that you have "howtousecoffeegrounds" but having prefixed the url value in the ajax with any sort of base path so the link would be relative.…
-
Try putting a space after the opening "{ " and before " }". Alternatively, you can wrap it in {literal}...{/literal} The Dwoo parsing library sees that as an attempt to merge a variable.
-
Overwrite the "get_others" method on your model like so: function get_others($display_field, $id, $val_field = NULL) { return array(); } To add action to the toolbar, I'm assuming you are referring to the area where you edit a module's records an…
-
Thanks for the report. This has actually already been fixed in the 1.0 branch: https://github.com/daylightstudio/FUEL-CMS/tree/1.0
-
What version are you updating to (latest master or the 1.0 beta branch)?
-
I'd perhaps look into creating a post_controller_constructor hook so as not to modify the page_router controller if you don't have to: http://codeigniter.com/user_guide/general/hooks.html Some example code may look something like the following (not…
-
If you are updating to the latest version of the master branch, you'll need to update the fuel/modules folder as well as the files found in the fuel/application helpers, core and libraries folders. However, the 1.0 beta has made it a bit easier to …
-
There is a lang key of "error_not_number" that you would need to change in the fuel/modules/fuel/language/english/fuel_lang.php file. The "auto_validate_field" method in MY_Model is where that validation is being set and you'll see that there are o…
-
This sounds like it's a static view file correct? If so, the parse_view only gets applied to the view being loaded in and not to the header and footer of the layout which is where your "literal" tag is and would explain why it's not being parsed. T…
-
It depends a little on how things were coded, but chances are you may not need to change much if any. The biggest change is that advanced modules are automatically loaded on the the fuel object if you have a library with the same name as the module …
-
Thanks for the report. That is actually fixed in the latest version of the user guide for 1.0: https://github.com/daylightstudio/FUEL-CMS/tree/1.0 https://github.com/daylightstudio/FUEL-CMS-User-Guide-Module