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've posted a fix for this in the repo. Thanks
-
The caching part still should work as intended. However, it appears that because FUEL modifies the drivers a little, the serialized object it uses (CI_DB_result), it doesn't have all the methods on it that FUEL has extended. I'm looking into that i…
-
That pull should have worked OK too. Would you mind posting your model and SQL or you can email it to me (address is on my forum profile page).
-
I think you may have missed part of the code. Try replacing the whole MY_Model file.
-
Is this with the latest pull from the repo?
-
There is an issue in MY_Model that isn't returning the id after save. I've posted a fix for 0.93: https://github.com/daylightstudio/FUEL-CMS/commit/25c0cea6373cc85f73aa18102fa6741b9bd11dd0 This is not an issue on 1.0
-
Also of note, 1.0 just recently had a new feature named “formatters” added to models which automatically applies functions to field values. The 1.0 user guide talks a little more about it. So you could do the following to automatically apply the mar…
-
There actually aren't any settings to speak of in which you can set in the MY_fuel.php file. However, there are settings that could be changed below: fuel/modules/fuel/assets/js/editors/markitup/jquery.markitup.set.js I also suppose, in 1.0 you cou…
-
You can add it in the MY_fuel.php config file like so to show the latest posts. $config['dashboards'] = array('fuel', 'blog');
-
The FUEL 0.93 demo site came with a contact controller and corresponding view file as an example. Note that you access it at "contact" and NOT "fuel/contact". https://github.com/daylightstudio/FUEL-CMS/tree/demo More information about creating page…
-
That indeed was a bug? Is this with the latest from GitHub?
-
Unfortunately we don't have a timeframe. We have a few supporting things we are working on between client work so it's tough to give an estimate.
-
If you are using AJAX and jQuery, you can simply just request the content like any other webpage. $.ajax({ url: 'forms/example', success : function(html){ console.log(html) } If you are using the "Opt-in" controller metho…
-
FUEL is just a layer on top of CodeIgniter so you should approach the page like you would by just using CodeIgniter and creating a view with the appropriate Javascript, CSS, etc. Are you familiar with CodeIgniter?
-
There is no particular reason, other then when FUEL was initially started about 4 years ago, MyISAM was the default storage engine and as we looked at other CMS's at the time (e.g. Expression Engine, Concrete 5, Wordpress ... changed now), they all …
-
Thanks for the heads up. Those javascript errors happen because the form is generated outside of the context of the CMS and many of the custom field types that are built in rely on some jQX configuration path variables (jQX is under the javascript s…
-
I'm not able to replicate that issue locally. Does it properly pass variables to other pages if entered in the $pages array in the global variables file?
-
I don't think that would be affecting the fuel module. The top 2 load view files from the applications folder and immediately output the contents. The second loads the block view file from the fuel modules, passing it an empty array of variables and…
-
Is there possibly a route being used for "admin"?
-
Try one of the following: $this->load->module_view('flexicart', '_layouts/main', $this->data); $this->load->view('flexicart/_layouts/main', $this->data); Additionally, there is a corresponding module_model, module_library, module_…
-
Could that error be because you are using "$this" instead of "$CI" in your _blocks/header.php file?
-
That is the correct syntax. Blocks will first look in the CMS for a corresponding block if the fuel_mode is set to "AUTO" (which means that you are using the CMS to create pages). If no block in the CMS is found, it will look in the views/_blocks fo…
-
The demo site is not up to date in the repo. We have been working on an updated version of the demo site to use more of the 1.0 features but have not added it to the repo.
-
You can try the following: 1. Add a hidden field in the blog_posts_model form_fields method of something like "categories_exists": $fields['categories_exists'] = array('type' => 'hidden', 'value' => '1'); 2. In the on_after_save_hook of the …
-
When you say dashboard, you referring to the FUEL CMS dashboard and logged in, you are referring to being logged into FUEL CMS correct? If so, that is already part of FUEL CMS. For example, if your session times out while you are inside the CMS admi…
-
This should be fixed in the 1.0 branch. It's no longer using the blog_categories_to_posts_model but instead using the new relationships functionality in 1.0: https://github.com/daylightstudio/FUEL-CMS/tree/1.0 https://github.com/daylightstudio/FUEL-…
-
Sure. Just be sure to load the validator helpers for the view. You can do that in the controller or even the view itself: // from view $CI =& get_instance(); $CI->load->helper('validator');
-
Are you logged into FUEL when you are reviewing those changes (being logged in will always bypass the cache)? Have you tried it in different browsers too?
-
Does this follow up help answer this question? http://www.getfuelcms.com/forums/discussion/1001/i-would-like-to-validate-form-with-validator-class/#Item_2
-
There are a couple validate functions you can use to help with that in the validator_helper. There is a display_errors() function which will output an unordered list of errors and a get_errors() function you can use which will return an array of err…