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 1.0 beta branch is already using 2.1.3. For 0.9.3 you can try it out, but I have not tested that yet. https://github.com/daylightstudio/FUEL-CMS/tree/1.0
-
OK... I think I may have found the issue. The Data_table class uses the records 'id' by default. I needed to explicitly set it to the model's key_field value in the module controller: https://github.com/daylightstudio/FUEL-CMS/commit/cb4c9d1c03d4af9…
-
Are you able to debug it and see if there are any sequel errors after the update in the module::items_precedence method: $this->model->debug_query()
-
I think the best place to start for anyone new to FUEL is with becoming familiar with CodeIgniter. FUEL is built on top of CodeIgniter and augments it's functionality more then changes it. This means that you can use your normal MVC outside of FUEL …
-
I think it's a bug we should probably fix. Does it work for you if you change in the fuel/modules/fuel/controllers/module.php file the items_precedence method, the "id" value in the where array to the following: $where = array($this->model->ke…
-
Regarding using the same controllers and models, it's tough to say. I would hope you could use at least the models perhaps by augmenting them to support those methods. The controller for it to work inside the CMS would need to extend the Fuel_base_c…
-
You can, but you must implement a few methods on the model (e.g. add_filters, list_items, list_items_total, find_by_key, record_count, delete, key_field, get_validation, get_errors, form_fields). The assets_model does this in which it uses the file …
-
You shouldn't have to do anything else. What version of FUEL are you running and what browser? If you look at the browser console, there should be a javascript ajax call after you drag a row to update the table.
-
Try creating a fuel/modules/admin/config/admin_fuel_modules.php" file which has the following: // add additional module config parameters here $config['modules']['openorders'] = array(); $config['modules']['closedorders'] = array(); The advanced …
-
It sounds more like a bug to me then a config issue. But to be sure, is it possible for you to update to the latest 1.0 version? Mostly just the fuel/modules/fuel folder.
-
You need to add it in order for that error message to go away. You can create it in your advanced module with a config file of "openorders_fuel_module.php" with the same info in it (FUEL automatically looks for those files in advanced modules).
-
Is this with the most recent version of FUEL 1.0? To see the changes on the page, you need to close the inline editing window so that it refreshes the page. Are you still not seeing changes after that?
-
Hmm... I would start by looking at if there is something in the that edit_mode.js file or if there is a js file being included that's causing the problem in the fuel/modules/fuel/views/_blocks/inline_edit_bar.php file.
-
Welcome and thanks. If you are just starting out, I'd recommend checking out the 1.0 beta version if you haven't already which includes a lot of new features and bug fixes: https://github.com/daylightstudio/FUEL-CMS/tree/1.0
-
If you remove the jQuery.noConflict(); from the top of the fuel/modules/fuel/assets/js/fuel/edit_mode.js file does it work? The 1.0 beta has that removed due to probably some similar issues.
-
You need to add a Product_model class to that Products_model class that extends "Base_module_record" like so: class Products_model extends Base_module_model { function __construct() { parent::__construct('products', array('key_field'…
-
Yes... boolean fields have been added to 1.0 to distinguish between tinyint fields and a tinyint field that is actually an enum of 1,0.
-
That error message most likely appears because it is looking for a simple module named "openorders". Do you have one defined in your MY_fuel_modules.php file?
-
FUEL 1.0 does support multiple languages. In your MY_fuel.php file, there is a "language" parameter in which you can add to. Having more then one will give you a language dropdown when creating a page. For simple modules, if you have a field of "lan…
-
Great idea. I've never felt comfortable with the current implementation of user/permissions and this seems to help a lot. I've made that change to the 1.0 beta branch that we are working on. If you are interested, I'd recommend checking out 1.0 and …
-
Is the field name still author_id? You can always overwrite it in the fuel_forms method of your model: $fields['author_id']['label'] = 'Author ID';
-
Welcome to the community. Thanks for the clarification. You are right and that the permission docs are out of date. I've pushed a fix for that.
-
Probably the easiest way is to use a field type of "custom" with the 'func' parameter set to a rendering function, or you can use the after_html to insert additional HTML. The 1.0 beta branch introduces the ability to nest Form_builder instances a…
-
Thanks for the note. Am merging in some CKEditor changes including the new version into a local dev 1.0 branch today as a matter of fact. The changes will include using the same link and image input between the markItUp! and CKEditor (so it will mer…
-
With regards to the User permissions documentation being misleading, were you referring to the user management page under the General documentation?
-
Thanks for the reports. I'll look into the permission issues. I've posted a fix for the backup module notification. You'll need to add it to the 'dashboards' parameter in the MY_fuel.php config file for it to show up.
-
Good solution. Thanks for the post back.
-
At first glance, it looks like you are doing things correctly. What seems to be happening? Are there any errors being returned by the validator object (you can use the get_errors() method on that object). If you need to create your own custom valid…
-
If you are using Form_builder, you can use render_divs() instead of just "render()".
-
You would need to use a route to have 2 different URIs pointing to the same controller. Then in the controller, you could decipher which one has the "mobile" segment and change the layout variable accordingly.