The "process_saved_values" or the "post_process_saved_values" are essentially a "hooks" but at the layout level. You can load in the models into the hook like so on your Layout class:
public function post_process_saved_values($values){ $CI =&a…
Strange... I swore I responded to this earlier. $this->normalzed_save_data is only a holder of the data that is posted and changing it won't change saved values. I would recommend creating a layout class that implements the method "process_saved_…
I would actually recommend creating a layout class that implements the method "process_saved_values" instead. This method gets passed the values that will be processed for saving before it is handed off to the model to be saved. More on creating a l…
If you want your home controller to handle the /de segment, then you'll need to create a route for it in the fuel/application/config/routes.php file.
Regarding your question about the best way to make a controller responsible for displaying the hom…
Thanks for pointing out those typos in the post (their is a parsing issue when we don't escape angle brackets). Your issue sounds like it's not triggering the javascript for Dropbox. If you view source do you see the call to "https://www.dropbox.com…
Is the server using some sort of security software that you know of like SUHOSIN?
https://suhosin.org/stories/index.html
I'm not sure what would cause that them to block an IP address. It should be doing an AJAX call to fuel/blocks/import/myblock w…
The value should be just an array of the values so try array_keys($articles) instead.
The template field type also has the ability to reorder:
http://docs.getfuelcms.com/general/forms#template
No, it should persist it to the CI config object ($this->config->item('fuel') should yield all the config variables. It doesn't however, persist the data to storage so subsequent calls would still show 1.
Is there any conditional logic in th…
Does the user having trouble have access to all permissions regarding for Blocks? When you say FUEL fails to import the block, is there an error message that appears after importing or is it after you import and save that the page the block appears …
I'm just saying that the variables you want to inline edit need to be variables you can manage in the CMS. To make them manageable in the CMS, you'll need to create the page in the CMS with the layout that contains those fields. Does that make sense?
That error is displayed when the page variables being displayed are coming from _variables files and aren't editable. To fix the issue, add the appropriate layout fields in for the CMS and save your page.
Actually, if your FUEL installation is in a "FUEL-CMS-master" folder, the RewriteBase should be:
RewriteBase /FUEL-CMS-master/
If that doesn't work, then you should check that mode_rewrite and .htaccess is enabled for your Apache server.
You can add the following inside your blocks:
$CI =& get_instance();
Also, is the following in your globals.php variables file?
$vars['CI'] =& get_instance();
The CI 404 error page doesn't go through a normal controller which is why you see in the default fuel/application/errors/error_404.php it includes and requires things for it to render.
If you create a view file of "404_error" or a page in the CMS o…
This answer may depend on what makes sense for how and where you need to render that information.
Most of the time, we will use blocks and either pass in the data or simply include the fuel_model function call at the top of the block to simplify th…
Is it possible that some of the files in the fuel/modules/fuel folder didn't get updated. The fuel.fields.setElementData should be in the custom_fields.js file:
https://github.com/daylightstudio/FUEL-CMS/blob/develop/fuel/modules/fuel/assets/js/fuel…
I'm not quite sure I completely understand your trying to do but will give it a shot in terms of how FUEL finds CMS pages. First it will look at the routes and then if there is a controller/method in place it will use that. If no controller is found…
There are 2 tables used for the data behind a page. The fuel_pages and the fuel_pagevariables. The fuel_pages table saves the location value (e.g. about/history), as well as it's cache and published settings. The fuel_pagevariables table is where al…
I ran into an is_ajax() related issue on a MediaTemple Grid server using CGI a while back. It appeared that the server was caching the pages (thus it was trickier to diagnose and replicate) and subsequently not even returning the proper AJAX header…
Do you mean you need to have a single block layout that has a different model to save to? If so, block layouts only support the ability to save to the set model on the layout.