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 having trouble replicating this issue on my end. I did notice some issues regarding changing the password (where it needed to validate that the new password and confirm password match). The password should get saved, it just get's removed from t…
-
You should be able to change them in the fuel/application/config/asset.php file and it won't effect the admin
-
For inline editing you'll need to make the same change displayed above to the following file on line 272: fuel/modules/fuel/assets/js/fuel/edit_mode.js
-
Oops... typo on my end. I've fixed that in the post to avoid further confusion.
-
Actually, your original post should have worked but there was an issue that needed to be fixed. I've updated it on GitHub but specifically the following files where changed: fuel/modules/fuel/controllers/login.php fuel/modules/fuel/libraries/Fuel_b…
-
To render the menu, I'd use the fuel_nav() function. The fuel_nav() function is a wrapper around the Menu class. http://www.getfuelcms.com/user_guide/helpers/fuel_helper http://www.getfuelcms.com/user_guide/libraries/menu We wrote a blog post last …
-
Great. Could you post your solution just in case someone else has the same problem?
-
It sounds like you have a solution but wanted to point out that if you are using a controller, then you will need to render the page by using the Fuel_page library in your controller method like so: function index() { //... your code here... …
-
You'll need to create a route as well in the fuel/application/config/routes.php file like so: $route['news'] = 'blog'; $route['news/(:any)'] = 'blog/$1';
-
I did a quick test a bit ago and was able to get it to render the ckeditor, but it required a significant amount of customization to get the toolbar to work like the MarkItUp editor and that's where I stopped. Regardless, I'll post as many steps as …
-
If you click on my profile picture, you should be able to see my email address.
-
I've added that for the Form_builder class and the other libraries in the documentation.
-
No worries. As an FYI, the CI_Controller is CI 2.0 change and that's why you were seeing that error. I'd be curious to know more about what the problem was that you were having. The example provided in the 0.91 version does require you to set the co…
-
The 0.91 branch has an example website that uses a contact controller you can use as an example. https://github.com/daylightstudio/FUEL-CMS/tree/0.91 However, the page is being pulled from the contact view file instead of the CMS. To have it pulled…
-
Although we may make changes to the users, permissions part of the application, we aren't quite sure the changes you are requesting are in the current scope of FUEL. The permissions system is meant be pretty granular allowing you to create permissio…
-
Thanks. We do need help with localization. There is a localization file at fuel/modules/fuel/language/en/fuel_lang.php that would be a good place to start. We hope to take a better look at it here in the next month or two but meanwhile, any translat…
-
Try uploading now. There was a folder permission issue that should be fixed now.
-
Thanks for the report. That has been updated for both versions.
-
The _process_uploads method in the fuel/modules/fuel/controllers/module.php file contains the logic for uploading the images. It gets called in the create and edit methods in the same file. on_after_save should have that id value. You could also ma…
-
I made a change to the 0.9 version that may fix that issue. I basically explicitly state where to find the FUEL config file. I changed line 34 in the fuel/module/fuel/libraries/Fuel_base_controller.php to the following: $this->load->module_con…
-
They are being updated simultaneously. The master branch has had more downloads and testing behind it however, the 0.91 is catching up.
-
Yes. The 0.91 branch is using CI 2.0 and modular separation for the modules instead of Matchbox.
-
OK... good to know.
-
It's not specific to the blog. You can specify the 'upload_path' for any file upload form field and use the placeholders in the path (e.g. {id}) to substitute in values from the current record you are editing.
-
It's possible that the images were cached but am not sure. What happens if you change the settings for the image upload path to blog/{id}/ ? Answering forum posts is usually a break for me :-)
-
Are you using the 0.90 version or the 0.91 version on GitHub? The 0.91 version uses Modular Separation and CI 2.0. The error you are seeing could be happening around line 88 in the fuel/application/libraries/MY_Config.php file in version 0.90 which …
-
You did the index.php? change to the .htaccess file correct? Did you change the $config['uri_protocol'] = 'QUERY_STRING'; ?
-
The image upload for the blog post is really just a convenience to upload images without going to the assets area. You have to specify where those images will appear in the content of your post either using the image insert button in the content are…
-
Couple more questions: 1. What is the URI path that you are using to see that error (is it just the homepage?) 2. Have you been able to get CodeIgniter projects to work on your server before (http://codeigniter.com)? 3. Do you have .htaccess and mo…
-
The .htaccess is in the correct spot. Are you able to access the FUEL admin (should be link below install directions)? Here is another thread that relates to problems getting errors while trying to access the FUEL admin that may help: http://www.g…