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
-
Not at the moment. If you use {fuel_block('my_block')}, within a layout field in the CMS, it does not get cached the same way and instead executes the fuel_block function during rendering which would escape the caching. Alternatively, you could choo…
-
FUEL currently uses the Dwoo templating language: http://dwoo.org/ http://docs.getfuelcms.com/general/template-parsing
-
That sounds like you may have a routing issue. Do you have a route setup for fuel/ufcm/users? This could be done in the application/config/routes.php file. Or if you create an advanced module, you can add it in its config folder. The Blog module use…
-
Good suggestion. I've posted an update to include tabindex. For fields like enums and dates that have multiple fields, the value needs to be an array.
-
In the 1.0 beta, there is an "exportable" module property you can set to TRUE. This calls the Base_module_model's export method which you can overwrite to fit your needs if the default doesn't work for you. In 0.93, you would have to extend the cont…
-
Thanks for the report. That should be fixed now.
-
There are 2 things you'll need to do: 1. Create a route like so: $route['blog|blog/(:any)$'] = 'news/$1'; 2. Change the "URI" value in the blog settings area to "news".
-
You can't at the moment. You would need to call the model's form_fields method and pass the returned array to the 'fields' value. It would also save the values to the fuel_pagevariables table and not the model's table.
-
If you use the CLI generation tool in 1.0, it will automatically generate permissions for you: http://docs.getfuelcms.com/modules/generate If you don't use the generate tool, in 1.0 you normally create 5 different permissions. An overall permission…
-
I've just posted a fix for that in the 1.0 branch. An alternative would be to use an array syntax like so which does work (note that it's a different block and is using a repeatable field): $config['blocks']['test'] = array( 'group' => 'Section…
-
There is a crucial line missing from the documentation which I've fixed. Add the following below $test_fields variable declaration: $test_layout->add_fields($test_fields); http://docs.getfuelcms.com/general/layouts
-
Is this using FUEL .93 or the FUEL 1.0 beta with the blog module installed (they are separated out in 1.0)? https://github.com/daylightstudio/FUEL-CMS-Blog-Module Also, to be clear, you are wanting your date picker to have the date format of "dd-mm…
-
Try adding this to the $page_init: $page_init = array('location' => 'historyexhibit', 'render_mode' => 'cms');
-
When you say "remove the advanced controller", what controller is that? By default, there is a route setup for the file at fuel/{module}/controller/my_module module.php that appears at the URI of http://localhost/fuel/my_module/. It sounds like you …
-
Did you define the record class as well? FUEL will assume it's the name of your Table class without the plural "s" but in your case, you'll need to specifically add it as a property to your Projects_all_model table class: public $record_class = 'Pro…
-
They are the same as what's used for Form_builder.
-
The correct format would be something like what was mentioned above with the array keys being unique to the set of menu items: $append['products/my_category'] = array('label' => 'My Category', 'parent_id' => 'products'); $append['products/my_c…
-
I'm curious what are you needing that parameter set to TRUE for? If you are wanting access to the query string parameters, you should be able to do that already because the $config['allow_get_array'] is set to TRUE in FUEL 1.0. What you are seeing i…
-
OK... I'm able to replicate that issue and will have a fix here shortly. Thanks for the recreation steps.
-
Normally I'd discourage making any updates to the core files, however, since this is in .93, there are no more changes planned for that branch so if it works for you and your project, I'd say keep it.
-
What happens if you remove the question mark after index.php from the following: RewriteRule .* index.php?/$1 [L]
-
That makes sense. Any break in the URL's parent/child hierarchy will cause the recursive function calling to stop.
-
I believe that particular issue is fixed in the 1.0 beta. The fix was to change the following in the MY_Model::lazy_load method: if ($cache_key == '') { if (is_array($where)) { $cache_key = implode('_', array_keys($where)); } else { $cache…
-
There are a few parameters you can pass fuel_nav that may help: * items - This will tell fuel_nav to use the items you pass it instead of any located in the CMS or views/_variables/nav.php file. So you can pass your custom values to fuel_nav inste…
-
Add the following at the top of your controller: require_once(FUEL_PATH.'libraries/Fuel_base_controller.php'); To add a hook, you can add to the fuel/application/config/hooks.php file like any other CI hook.
-
And you were doing the publish/unpublish in the admin in the comment edit screen correct? And this is still 0.93 or did you update it to 1.0? That URL issue looks like a mod_rewrite / .htaccess issue. What is the value of your "RewriteBase" in your…
-
I forgot to mention that there is "ckeditor_config" parameter you can use with the wysiwyg field type which takes an associative array. That was missing from the documentation and I just added it. Read that, and perhaps try using that method so you …
-
In the 1.0 beta, If you inherit from the Fuel_base_controller, there is a protected "_validate_user" method you can use which will validate if a person is logged in by using the Fuel_auth class (e.g. $this->fuel->auth->has_permission($permi…
-
You can add additional methods to your model if you need to. However, the returned result set will most likely be an array of objects that probably have an "image property on them: $values = $CI->homeslider_model->find_all(); foreach($values a…
-
You need to reference $CI->homeslider_model->find_all() instead of $this->homeslider_model->find_all().