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
-
Did you clear the cache in the CMS? Those files are stored in the fuel/application/cache folder.
-
I think the issue has to do with there being a sub module the same name as the advanced module (e.g. site_users/site_users). In looking at the logic in the __constructor of the fuel/modules/fuel/controllers/module.php controller, it checks to see if…
-
There was a way to do it by passing 'resize_and_crop' as a parameter to fuel->assets->upload(). However, it wasn't quite integrated into the assets page very well. I made a few changes this morning to help with that so you should be able to pa…
-
I can't see anything wrong in your configuration file. What are the defined routes for this advanced module?
-
Well... to be fair to you, there is a lot of new stuff.
-
Thanks for the report. I've pushed a few changes to fix that issue. It does require a schema change though to the fuel_blog_users table. An "id" column was added and set as the new primary key. It should also only display the list of folks who are n…
-
If you exit the script right before executing the contents of the on_after_post method, can you see the image in the assets/images/gallery/ folder? Also, are you familiar with the new 'asset' field type with 1.0? The section on Forms talks about th…
-
So is that the server path to the image in the assets/images folder?
-
I'll try and answer many of your questions below: 1. The issue with the record model being "Ite_user" is a bug and I've just pushed a fix for it. 2. With regards to the table "users" mapping to "fuel_users", that is because there is a fuel config v…
-
Hmm... I've used that code as well and haven't seen that problem. Is this before the other rewrite rules? Also, is the "index_page" value set to blank in the main CI config file (fuel/application/config/config.php)? Below is an example of a .htacces…
-
The model location value should be blank "" or the word "app" which is used to point to the application directory.
-
I noticed I had in the code above to generate the simple modules "ion_auth_model ion_auth". It should be what is displayed below: php index.php fuel/generate/simple ion_auth ion_auth This will generate the sub-module ion_auth (and generate an ion_au…
-
What's the value of $this->upload().$file?
-
You are right in that it should be "model_name" and not just "model". I'd try changing the "model_name" value to be My_assets_model (note that it's not MY)
-
I've pushed a fix for the generated controller name as well as some improvements to the documentation. In your case, you've only generated the advanced module and the advanced module does not contain any simple modules so you will need to generate t…
-
No problem. Be sure to download and install the user guide module for 1.0 beta. The Form_builder class was overhauled a bit as well as a bunch of new features and bug fixes. https://github.com/daylightstudio/FUEL-CMS-User-Guide-Module Other modules…
-
It looks like that previous fix was only in one area. I've pushed a fix to implement it in the area where it sets the value and saves to the database as well. Thanks for the report.
-
In 0.93 you can't really do it unless you add a " " (an empty space) for the label value and then do an after_html for the field with your label. In 1.0 you can pass a "display_label" boolean parameter to the field to hide it.
-
Are you sure it is rendering the closing div tag or is that the Inspector in the browser displaying it perhaps because it was an unclosed tag?
-
Unfortunately, FUEL doesn't provide granule control of sub folder permissions for asset files. I suppose you could overwrite the assets_model so that it would only look into the folder of the logged in persons ID but may be a little more work. To o…
-
That's a bug in 0.93 and should be fixed in 1.0 branch. To fix it, try adding the following to the Form_builder class on line 1334: 'class' => $params['class']
-
You can certainly just create your forms using CI's form functions. Form_builder allows you to create common form elements using an array syntax. You can pass it a Validator object which will highlight fields that have errors as well. FUEL uses it t…
-
That's indeed a bug. I just pushed a fix to the 1.0 branch: https://github.com/daylightstudio/FUEL-CMS/commit/0d6d6d201ebf0b4107d5b1296522f0163397334e Thanks for the report
-
Try using the type of "enum" instead of "checkbox" which will give you radio buttons. Is this using 0.93 or the 1.0 beta branch? https://github.com/daylightstudio/FUEL-CMS/tree/1.0
-
Is it perhaps localhost is the same as localhost/home with FUEL?
-
Try removing from the if condition on POST: $_SERVER['SERVER_ADDR'] == $_SERVER['REMOTE_ADDR'] I don't think your suggestion to change the .htaccess that way will work because of how CI figures out the URI path. Do you have access to your apache co…
-
One workaround at the moment may be to set the $session->flashdata('success') to a variable and then use that in the if condition.
-
BTW... the problem I'm guessing is due to line 262 in the MY_string_helper under the php_to_template_syntax function.
-
Try adding the following to your MY_fuel_modules.php which overwrites existing module data: $config['module_overwrites']['pages'] = array('sanitize_input' => array('template','php'));
-
It's used to retrieve. With regards to it working before and not now, I'm not sure. I just tested it out locally and it seemed to work OK. Did you try clearing out the compiled files? Also, can you check in the fuel/application/config/parser.php f…