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
-
When rendering a view from a controller, you'll need to use the Fuel_page class so that it will properly create the inline editing code. To do this, follow the link below and go to the "Using Controllers" section which should help explain it better.…
-
You can then use something like: $id = 1; // generic find by one $record = $this->authors_model->find_one(array('id' => $id)); //OR find by key $record = $this->authors_model->find_by_key($id); $record is an instance of your Author_…
-
That should do it.
-
You can create a normal CI controller to process any form logic and then set the action of your form to that controller (e.g. /forms/process would be a controller named forms calling a method "process"). You may already be familiar with CI controll…
-
Interesting project. It sounds like you would need to create a new controller, views and model perhaps so I'd recommend creating an "assets" advanced module: http://www.getfuelcms.com/user_guide/modules/advanced You may want to try it using the 1.0…
-
Where are you seeing that error message? Also, you'll want to make the entire fuel/application/cache directory writeable (recursive), and in some cases that may mean 775 or 777.
-
Is there perhaps a PHP error that is happening that is causing you to see the FUEL_MARKER instead? Those get cleaned up on rendering and are used for the inline editing to create the pencil markers. If there is PHP error before they've been cleaned …
-
You are right about the edit and delete. You can overwrite those methods in the model like you suggested (for the form_fields), as well as the delete method on the model. You could also create a controller that extends the module controller and over…
-
So the issue is only when sending locally from your machine? Does this thread help? http://codeigniter.com/forums/viewthread/184596/#877153
-
No. You'll need to use: $CI->load->model('ads_model'); $CI>ads_model->record_count(array('cat_id'=>$catId, 'sub_cat_id'=>$subCatId)); fuel_model is a convenience wrapper function around the model.
-
I'll look into adding those parameters. The 1.0 branch on GitHub does give you the ability to create your own field types (email is actually built into the 1.0 beta of Form_builder) or modify existing ones to add additional parameters like you sugge…
-
What kind of platform are you using to run PHP/MySQL/Apache (e.g. MAMP, WAMP, etc)?
-
Do you have a screenshot of what it looks like or any error messages?
-
Thanks for the report. We'll roll it into the 1.0 branch.
-
What's the error message and what is the controller code? Also, you may want to checkout this page in the user guide: http://www.getfuelcms.com/user_guide/general/creating-pages#controller
-
What if you just remove the "Options +FollowSymLinks" from the .htaccess enar the top?
-
Fuel block will return FALSE if the file doesn't exist. So you could try setting it to a variable and then checking the variable's value too.
-
Yes, you will need to edit that file to get it to work. 1.0 would need to have the fuel/modules/fuel/views/_blocks/nav.php file edited.
-
Possibly. It really depends on how complicated the existing database structure is and what needs to be mapped to FUEL modules (either custom or built in) as well as how comfortable you are using CodeIgniter. I think it helps to think of projects fro…
-
The field is rendered by the Form_builder class through the fuel/modules/fuel/controllers/module.php file. For inline editing, there is additional javascript that is included in the fuel/modules/fuel/assets/js/fuel/edit_mode.js file. However, in 1.0…
-
The FUEL blog module is rendered by the fuel/modules/blog/controllers/blog.php controller which inherits from the fuel/modules/blog/libraries/Blog_base_controller.php. I'd recommend perhaps looking at those controllers if you haven't already.
-
I've corrected the typo above. With regards to your issue, is the validator object you are setting register_to_global_errors on the same one you are setting the rules up on and capturing the errors?
-
I think the file you are looking for is the fuel/modules/fuel/models/base_module_model.php "form_fields" method. Alternatively, you can modify the fuel/modules/blog/models/blog_posts_model.php "form_fields" method which inherits from the Base_module…
-
You can also use the "order" parameter: fuel_model('categories', array('find' => 'all', 'where' => array('published' => 'yes'), 'order' => 'name asc'));
-
What is the configuration setting for "assets_output" in the fuel/application/config/asset.php file? That configuration can be set for the front end view of the site whereas the "fuel_assets_output" configuration is meant for the backend CMS. Also,…
-
I think to make that case insensitive you would need to make a change in the core code to the regular expression that is doing the matching. On line 134 of the fuel/modules/fuel/libraries/Fuel_pagevars.php file, there is a line of the following: if …
-
I just posted an update on the inline_edit_bar in the 1.0 branch to detect if jQuery was loaded already and if not, to load it. What was there before wasn't working correctly.
-
Did you create a controller named reports in your advanced module which extends the Fuel_base_controller (fuel/modules/reports/controllers/reports.php)? On that controller you can add a method named "home".
-
Sorry... the fuel/modules/fuel/libraries is the new path in the 1.0 beta. Does it work if you replace the entire Menu class with the Menu class from the 1.0 beta: https://github.com/daylightstudio/FUEL-CMS/blob/1.0/fuel/modules/fuel/libraries/Menu.p…
-
You can also use Query String parameters in the 1.0 branch. https://github.com/daylightstudio/FUEL-CMS/tree/1.0