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
-
The on_after_post hook happens after the save and is also when the image processing of uploaded files happens. So if you need to run image validation before saving, then you'll need to create an on_before_validate hook to process/validate the image.…
-
The settings change is used to control what the generated links display. The last step is to create the route in your route file like so: $route['news'] = 'blog';
-
If you are using 1.0, try the following instead of using the class: $fields['promo_asset']['folder'] = 'pdf'; The folder must also be writable.
-
The on_after_post model callback is intended for things like that. Why aren't you wanting to use it there?
-
To create a custom form field type I'd recommend the following: 1. Create a class or function that contains the logic for creating the field. The fuel/modules/fuel/libraries/Fuel_custom_fields.php is a good place to look as an example. A $param of o…
-
I'll post that as a fix so you can pull from it later today.
-
OK... I think I have another solution although I believe yours will work as well. If you go to the fuel/modules/fuel/libraries/Fuel_custom_fields.php on line 1120 change: 'exists_'.$params['name']; TO 'exists_'.$params['orig_name']; does that work?
-
Ah... OK... let me see what I can do here.
-
What if you change it the 4 to a 6 like so: foreach($posted as $key => $val) { if (strncmp('vars--', $key, 6) === 0) { $new_key = end(explode('--', $key)); $vars[$new_key] = $val; } }
-
Can you provide the layout configuration that's having the issue in MY_fuel_layouts to see if there is anything there that be be causing the problem? It may be a hidden field but probably not the one you posted (it's a different name).
-
What does the $posted variable look like? Is it perhaps overwriting the key "widgets_on_page" in the lop? Maybe there is a "vars--widgets_on_page" and a "widgets_on_page" post param?
-
Hmm.. that appears to be an issue with 0.93 but not for 1.0 and am uncertain at this point if it is the version of CI being used or the HMVC modular separation piece of it. Sorry, but I think at this point, your best bet is to either upgrade to 1.0 …
-
OK... next step will be to see what's getting sent on save. So in the same controller, under the "_save_page_vars" method, there is a foreach loop around line 477 that loops through the fields for your layout and checks a $vars variable for a corres…
-
I'm a bit stumped at the moment. If you've updated the database and files correctly then the changes should match what you are seeing in your dev environment. Is there perhaps some sort of load balancing on your production server? BTW, FUEL 1.0 all…
-
No problem. Glad you like FUEL CMS. The span "_val" is the index to the corresponding value. The select widget looks correct as well. The next step would be to see what that looks like in the post or right before it's getting saved. To do that we'…
-
just add 'class' => 'no_editor' as a parameter to your field
-
What are the values associated with each option? If you inspect the DOM, you should be able to find the actual select field being used to generate what's on the screen. Or you can add 'class' => 'no_combo' as an attribute to the field type and it…
-
Are you looking for a "point" type field generated by Form_builder? If so, there currently isn't one but this sounds like an opportunity to add one. I haven't really worked with that field type before, so what were you envisioning that field type lo…
-
I just pushed a change to the 1.0 beta that will for that to multi mode if "sorting" => TRUE
-
Add the following parameter: 'mode' => 'multi' Without it, it will default to checkboxes if there are less then or equal to 5 options and the sorting doesn't work with that.
-
Was the Production environment completely updated including the database tables?
-
Hmm... it seems to work for me at first glance. Is this 0.93 or the 1.0 beta? Also, when you say it doesn't work, do you mean that it simply still just displays the homepage?
-
This is using the 1.0 beta (I'm guessing because you mention tabs which is a 1.0 feature)? If so, try the following in your MY_fuel_layouts.php in the appropriate layout: .... 'widgets' => array('type' => 'multi', 'model' => 'widgets', 'sor…
-
In 1.0 beta you can do the following: $CI->fuel->page->id In .93 you can do: $CI->fuel_pages->id
-
That sounds like you need to define the view for that URI path since that view file technically doesn't exist (views/ad does but views/ad/1 does not). To do that, add the following to your fuel/application/views/_variables/global.php file (or it cou…
-
Does it work for you when you change the default_controller route to 'blog' instead of 'fuel/page_router'? $route['default_controller'] = 'blog';
-
Where specifically were the changes made? Things in the admin don't get cached (only the front end pages).
-
This is an older post. A lot of updates have been made in the 1.0 beta regarding better integration with CKEditor. I'd highly recommend checking it out here: https://github.com/daylightstudio/FUEL-CMS/tree/1.0
-
FUEL doesn't really have an articles and pages difference. You can create pages, which have predefined layout fields you fill out in the CMS. Or there are modules that are usually wrappers around database tables that provide managementIt of data wit…
-
In short, I would say yes. You could use something like relationships in the 1.0 beta to make associations between articles and pages in the CMS. https://github.com/daylightstudio/FUEL-CMS/tree/1.0