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,799
- Last Active
- Roles
- Administrator
Comments
-
The slug value for the forms module doesn't directly relate to the page in which you view the form but the page in which it gets submitted to. To embed the form, you can use: <?=form('contact')?>
-
You can copy that file to fuel/applications/views/search.php and paste in the code from that fuel/modules/search/views/search.php into it so it allows you to update the search module codebase without affecting your custom changes. The default value …
-
For the block layouts, you'll need to set the model property to be your module's model. By default, it will pull values from the Fuel_pagevariables_model. $my_block_layout->set_model('my_model');
-
Thanks for the report on the fuel_layouts page. That has been fixed. Regarding your issue, is it saving to the fuel_pagevariables table?
-
You would need to create a custom plugin for either markItUp! or CKEditor depending on which editor you are using.
-
To get the variables for a page including global variables you can use pagevars: $CI->fuel->pagevars('mylocation');
-
You'll want to make sure that your Model has a record class associated with it as well. This link provides an example half way down. So one class that extends Base_module_model and another class that extends Base_module_record which usually resides …
-
Is $award_list returning an array of "Award" record objects? Also do you have an Award_items_model specified?
-
Is there a specified route in the routes.php file for this Controller?
-
It may have something to do with the sanitization being done on save for the module. For your module's config, add the parameter: 'sanitize_input' => array('template','php'), The default is the value of "TRUE" which is an array of array('template…
-
This should be updated in the develop branch. https://github.com/daylightstudio/FUEL-CMS/tree/develop
-
What do you mean by it doesn't work? Is the controller's first letter of the file name capitalized?
-
This looks like it may be an issue with that particular field type with sorting set to true and may take a bit of time to debug.
-
Try this: https://www.codeigniter.com/user_guide/installation/troubleshooting.html
-
That's correct. So are you experiencing this issue with both the multi and the select2 or just the select2?
-
So you are using a "select2" instead of the "multi" field type to handle this? Does this happen if you use a "multi" field type?
-
This was more an issue I believe with older versions of CI when the session info was saved in a special CI_SESSION cookie that had a 4K limit and would cause issues with too much data. I would set it to the number of modules that you have and see ho…
-
Is it selecting the item you just added?
-
There seems to be something strange going on with your server and I'm not able to debug it from here unfortunately.
-
Did you create the Youtube plugin or is that something you found elsewhere? If elsewhere, would you mind sending a link to it?
-
Is this error if you navigate to any page or a specific URI?
-
What version of PHP is running on the instance on the server (only one of those is running)? You can use the phpinfo() or phpversion() functions.
-
That is happening in the MY_Model::process_relationships() method around line 3346. The Fuel_users_model has a has_many relationship to the Fuel_permissions_model which gets processed via the on_after_save hook.
-
And it works locally for you but not on the server? What are the specs locally vs. the server?
-
I've never seen this error before. What's the full backtrace?
-
Does it work if you apply this fix (I just pushed to the develop branch)? https://github.com/daylightstudio/FUEL-CMS/commit/ab0170b48275224c6743c0ca2e2bf2a392d23673
-
Remove line 161 and 204 in the fuel_schema.sql file and try.
-
Looks like not all the tables have been loaded. Try dropping all the tables (assuming you haven't added anything to them yet) and loading in the fuel/install/fuel_schema.sql file again.
-
This seems to be a bug. I've posted a fix in the develop branch for what I noticed when debugging your issue: https://github.com/daylightstudio/FUEL-CMS/commit/7f743339bb8e59084fabeaefd136764c1d57d229
-
Does your fuelcms database have tables in it and in particular the fuel_users table?