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
-
You may need to change your MY_fuel.php file so that the fuel_mode is set to "AUTO".
-
Thanks for the report. That should be fixed now.
-
We normally use Git to handle the upgrading by pulling in the desired remote FUEL branch usually into a local "upgrade" branch. This allows us to fix any sort of merge conflicts that may happen in the fuel/application directory (to configs, views, e…
-
We don't have a firm date yet. We are doing internal testing with newer projects to help knock out any bugs.
-
By default, FUEL uses normal CI cookies sessions which can be configured in the fuel/application/config/config.php file. However, you can configure it to use the DB per the documentation: Master branch on CI 2: http://www.codeigniter.com/userguide…
-
I'm not quite sure I'm understanding the question, however, if I were to guess, it would be the first parameter: $this->_CI->fuel->blog->url($tag->get_url(FALSE)), $tag->name, $link_params); That is the URL that is generated from t…
-
Do you have the permissions for blocks, blocks/create, blocks/edit, blocks/edit and blocks/publish assigned to that user?
-
Those query string parameters are from the form fields on the page (some fields are hidden).
-
I guess it depends on where you are wanting to do this programmatically but probably in your own controller. If you generate your simple modules, it will automatically create the general permissions for you: >php index.php fuel/generate/simple my…
-
Thanks for the report. I've pushed a fix for that.
-
Hm... is it possible something may have gotten missed in the upgrade process? Are you able to test this out with a fresh version of 1.3.2 and your code migrated to it?
-
Was it a fresh copy or did you merge/update? Do you have a config value in your MY_fuel of: // The parsing engine to use for FUEL. Options are dwoo, ci and now 'twig'! $config['parser_engine'] = 'dwoo';
-
Does the following syntax fix your problem: public $has_many =array('speaker_id' => array( 'events'=>'speakers_model', 'where' => array('is_disabled' => 0));
-
Where does your "speakers_model" live? If it is in the fuel/application/models folder then I'd try the following: public $has_many = array('speaker_id' => array('model' => 'speakers_model', 'where' => array('is_disabled' => 0))); Note th…
-
OK. I've pushed an update to the develop branch for this. The develop branch includes an update to CI 3.0 and may require a bunch of other changes (in particular casing of files) so I would do the upgrade in a different local GIT branch if you decid…
-
Unfortunately, there is not anything built into FUEL nor have I heard of anyone doing it (not that it couldn't be done). The class that handles the uploading is the Fuel_assets class and would most likely need to be modified: http://docs.getfuelcms.…
-
Are you referring to the hide_options part? It appears that the folder name is working correctly based on the screenshot.
-
What version of FUEL are you running (check fuel/modules/fuel/config/fuel_constants.php)
-
It would be in the $values array that is passed to the form_fields method if you are editing. If it is a new record then it won't exist. Since only form field values get saved in the JSON, you could try saving the __src__ value as just another hidde…
-
Is there a broken image appearing or no image at all. If it is broken, what is the src path being used?
-
I'm not quite sure I follow.
-
Actually group_id will also check if it is a string value or not and if so, will check the navigation group name value instead of the ID. Did you try that yet?
-
A couple people in have complained about this issue. I'm not quite sure what is causing it (if it's a bad cookie or something) nor have been able to replicate the problem. Have you tried deleting any cookies and logging out then back in?
-
I think I see the issue. I've posted a fix to the repo: https://github.com/daylightstudio/FUEL-CMS-Forms-Module https://github.com/daylightstudio/FUEL-CMS-Forms-Module/commit/5e78af0a8c475c0f169ea5165dc88c4c3175f426
-
Try setting the type to just a "select". There seems to be a bug with the rendering of labels on enum field types in that scenario when there are more then 2 options and it goes into a dropdown select.
-
The develop branch uses CI 3.* and is fairly stable at the moment.
-
Yes. You have to essentially return an array similar to the navigation array specified at the link below where you specify a unique "id" value for each item and specify the parent_id value to the child's parent (or NULL / 0 if it's the root element)…
-
Can you show the $field array code that is getting passed to Form_builder as well as the generated HTML code you are seeing?
-
You can add suffixes to your field names that will apply different operators in the comparison. In your case, you want a shop_categories.parent_equal: http://docs.getfuelcms.com/modules/simple#filtering
-
I'm not quite sure I understand "values are lost upon submitting the form". Could you explain that more?