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
-
I'm not sure what that issue may be but would probably start here looking for other folks having CI session related issues: http://stackoverflow.com/questions/6856960/codeigniter-session-expires-frequently
-
If this is using a $has_many property, perhaps to simplify this matter and you always want to use "text" instead of "name" for your option display, you can overwrite the method on your comments_model: public function options_list($key = NULL, $val =…
-
The multi-select field has an options parameter to determine the options. By default it uses the model's "options_list" method which will usually use the first column (id) and the next column that doesn't have an "_id". This can be changed though by…
-
Do you by chance have multiple FUEL sites open on the same server using the same cookie? You may want to try changing the session to use the database and see if that helps (the CI docs above explains how to do that).
-
That sounds like it's hitting the Forms controller process method and it's not honoring the is_ajax() method. Are you able to debug the result in that controller?
-
If you are not logged in as the admin, then you will need to have the permission assigned to you which will be 'blocks/upload' in your case.
-
There is a "template" field type you may want to try using which allows you to use a view file and will pass a $fields and $values array to it: http://docs.getfuelcms.com/general/forms#template
-
Try the following: $fields['passion'] = array('type' => 'custom', 'value' => $data->passion);
-
The idea of an Advanced Module is that it can contain it's own simple modules, or it can be something completely different. Think of it as another "app" directory. All the modules listed here are Advanced Modules, some of which have simple modules (…
-
My bad on that. You are correct (I just did this the other day so should have remembered). You need to define it on the layout itself what model you want to set.
-
FUEL doesn't support url_suffixes.
-
Advanced modules can contain simple modules (the Blog module does this as an example): https://github.com/daylightstudio/FUEL-CMS-Blog-Module Using the blog as an example which has a blog_posts_model, if you wanted to load that in a controller or l…
-
For the module parameter, use the name of the simple module you want to save it to (e.g. news)
-
If you need a field the displays some sort of custom HTML, there is a custom field type. However, it's possible that one of the existing field types may do the trick for you. I'd recommend reviewing and playing out with some of the different field t…
-
If you are using the block field in a module, you'll need to specify the "module" parameter for your block field.
-
BaseFuelController.js redrawTable method
-
There have been some minor changes to the MY_fuel.php file but I think that should be about it and you may not need to update that on your end.
-
If I remember correctly, I think we figured it had something to do at the server level and that it seemed to be caching the requests. When you go to that page, it actually first does the normal non-AJAX request to that page which returns the entire …
-
There is a fuel/application/config/editors.php file that should exist in your config folder that seems like it may be missing according to that error.
-
Perhaps adjusting this setting may help in your php.ini: http://stackoverflow.com/questions/8268624/php-preg-match-all-limit
-
FUEL uses the native CI sessions and there are session changes that can be made in the fuel/applications/config/config.php under the sessions area: https://ellislab.com/codeigniter/user-guide/libraries/sessions.html
-
This looks to be something the xss_clean function is doing. What module are you saving from? If it is your own module, the xss_clean function is used by default for modules but can be overwritten in your MY_fuel_modules.php by adding the following t…
-
I believe this has been fixed in the develop branch: https://github.com/daylightstudio/FUEL-CMS/tree/develop
-
You problem had to do with your main layout on line 8 where you are calling this: $this->load->view($params); The first parameter should be a string value to a view path and NOT an array of values: $this->load->view('_blocks/header',$par…
-
Perhaps. What does your layout look like for that page and it may be good to debug the Fuel_page::render_cms function to see where the issue may be.
-
Are the data results different between the different servers which would cause the difference in memory? I believe that memory usage is pretty normal.
-
This may be a rabbit hole, but we ran into a really strange issue that reminded me of this issue a while back on a MediaTemple Grid server where it wasn't properly creating the AJAX headers and so in the module controller, the is_ajax() function wou…
-
That's really tough to tell from this side and whether it is related to FUEL or something else.
-
The jqx file should be loaded near the footer in the HTML and initialized right after that. Do you see that in the HTML?
-
That is strange and have never seen that before. Sometimes throwing an alert right after the JS error will pause the execution so you can look at the error before it redirects. You can try adding one to the jqx.js file.