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
-
That looks to be a bug. I've just pushed a fix for that on the develop branch: https://github.com/daylightstudio/FUEL-CMS/commit/c0b0dd17816a1f8b48ca45df5e7d47d4e8b6e9d7
-
I'm unfortunately not able to replicate this issue locally. Is this happening to you on a fresh install of FUEL?
-
If it's for some of the PDFs and not all of them, it maybe an issue with how the server is sending the mime types or the browser. Are you certain that the mimes being returned are "application/pdf"? I would debug in the CI_Upload::_file_mime_type() …
-
I've pushed a modified fix for the PDF button: https://github.com/daylightstudio/FUEL-CMS/commit/9db1855454e3ce047a1576ad72cbd04336954b98 Regarding the error, FUEL currently doesn't support required file upload fields since it only checks the $_POS…
-
That file name should be capitalized in 1.4.
-
Do you have session_start somewhere else in your codebase?
-
The fuel/application/config/MY_fuel.php $config['fuel_path'] value should be all you need to change without renaming the folder.
-
Thanks for the report. I've pushed a fix here: https://github.com/daylightstudio/FUEL-CMS/commit/3e29c849c6418ff8bc89e1ad49675cd78096bc06
-
If you use the fuel_var method, it will automatically put in that comment which is used for the front end inline editing. A way around that is to simply just use $page_active_top_menu.
-
Are you able to get to what line the CI_Upload::is_allowed_filetype() method is returning false at (e.g. between 885 and 923 in latest release)?
-
If you are seeing that comment displayed, it's usually because there is something that is exiting the script prematurely. Do you have errors turned on and are you able to view source to see if there are any PHP errors being displayed.
-
Thanks for the report. It appears that the CI auto_link function had made some changes that caused the issue.
-
What's the file type you are trying to upload and is it and is that file type in the "editable_asset_filetypes" "assets" key parameter in MY_fuel.php? The default value (which is found in the fuel/modules/fuel/config/fuel.php file and overwritten by…
-
It sounds like you are building this form for the front-end of your forms. There is a fuel/modules/fuel/assets/js/fuel/custom_fields.js that has the initialization function of fuel.fields.datetime_field that will also need to be loaded. You can also…
-
In MY_fuel.php you can set the following which will affect editors globally: $config['text_editor'] = 'markitup'; On a per field basis, you can set a parameter on the field like so: $fields['wysiwyg_example1'] = array('type' => 'wysiwyg', 'editor…
-
With those extra fields, the fuel_relationships table allows you to have only one table to manage lookups instead of creating a table for each lookup relationship like in Laravel. I've done something similar in Eloquent using the following method on…
-
For the language field to show up, there needs to be more then one array value specified in the MY_fuel.php config for language (which isn't in there by default): // Languages for pages. The key is saved to the page variables $config['languages'] = …
-
edival, There are 2 places in the code where that error can be thrown. One is in the CI_Upload class itself. The other is in the Fuel_assets::upload() method around line 166. Is the error being thrown there?
-
Hmm... the values are loaded in from the form_fields method on the model. The MY_Model::form_fields() method is where it tries to get the values for the relationship (around line 2878). Are values coming through for you there?
-
What folder were your changes made?
-
Instead of using displayonly, you can use overwrite the model's form_fields method and use a field type of "custom" which has a "value" parameter of what you want it to display.
-
edival, what filetype are you trying to upload and is the mime type specified correctly in the fuel/application/config/mimes.php file?
-
Thanks for the report. That should be fixed now.
-
I've made a few updates to the documentation to help clarify a couple things: http://docs.getfuelcms.com/installation/installing
-
Are you having this problem with a fresh version of 1.4?
-
Have you set it up as a simple module yet in the fuel/application/config/MY_fuel_modules.php? http://docs.getfuelcms.com/modules/simple
-
Try changing it to without the ending slash: $config['assets_cache_folder'] = 'cache';
-
There is a 'scope' parameter you can pass as an argument to fuel_block's configuration array which can help ensure that those values are unique. The scope value should be a unique string key.
-
Thanks for the report. I've pushed a fix to the develop branch that you can test out: https://github.com/daylightstudio/FUEL-CMS/commit/8cdc2bf3ed3071ecc3bcf64767eeed7d3d7223e6
-
I'm a bit confused... those lines weren't commented out in the original FUEL code correct?