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
-
It could be an error. I'm sorry but that error doesn't appear to be something that is specific to FUEL and may be something specific to the server environment setup but am not sure. We have FUEL working on IIS and haven't seen that error yet.
-
So it looks like this: Error
-
If you view source, is there any other content or does it simply just say "Error"? If so, I'm not aware of a place where FUEL will throw an error that says just that.
-
You may be able to do this using FUEL 1.0 and custom fields which allow you to associate a field with it's own javascript and CSS: http://docs.getfuelcms.com/general/forms
-
I am not aware of anyone integrating TinyMCE editor. FUEL only supports CKEditor at this point.
-
That module may have worked with a few tweaks probably to the routes file. However, it was out of date and not taking advantage of a lot of the 1.0 stuff including the ability for you to use it in your own code. So I basically just rewrote it: $summ…
-
Can you view source of the Error page and paste it in here (if it fits)? Or perhaps send a screenshot of the error message?
-
I just created a new repo for this for the 1.0 version. Test it out here: https://github.com/daylightstudio/FUEL-CMS-Campaign-Monitor-Module
-
If you can access: http://localhost/latihfuelcms01/index.php/fuel/login But not: http://localhost/latihfuelcms01/fuel/login Chances are that you need to turn on mod_rewrite for .htaccess. Here are some instructions for enabling it that may help: h…
-
Also, you may want to look at the 1.0 beta if you haven't already: https://github.com/daylightstudio/FUEL-CMS/tree/1.0 http://docs.getfuelcms.com
-
It depends on the amount of customization that's been done. In most cases though, it's not too bad. I would do the following: 1. Create a new project folder and clone the repo into that folder. I recommend using GIT as opposed to just downloading th…
-
If you are using 0.93, you will need to do the following: $CI =& get_instance(); $CI->load->library('fuel_blog'); $posts = $CI->fuel_blog->get_recent_posts(2); For 1.0, you can just call the following: $CI = & get_instance(); $p…
-
If you are using 0.93, I would. I do remember there being issues with checkboxes because they don't present a value to save if you don't check them so I always opted for radios. 1.0 you can use checkboxes.
-
Nice! Glad you got everything working.
-
Is this .93 or 1.0 beta? Also, when you say you aren't getting a value, is it when the checkbox is checked or unchecked. Forms don't submit unchecked checkbox values. An alternative is to use an enum with a 'yes'/'no' value.
-
Use $meta_no_index. fuel_var is a function that will output the inline editing code unless you set the third parameter to FALSE
-
And this is an updated version of the 1.0 branch correct? Are there any special unique indexes on the table?
-
I used "explorepics" simply because I thought that was the name of your advanced module folder that you set up (e.g. fuel/modules/explorepics). It could easily be "jbproject". To do that you'll need to change your module folder name to fuel/modules…
-
I think I understand. Because the template field is stored as one serialized array variable, when you edit using fuel_edit you have to edit the whole thing so unfortunately, there isn't a way right now to just edit a single block if you are using a …
-
When you say "edit the fields within the block", do you mean editing the "name" and "view" fields of the actual block from the CMS or editing the layout variable fields that get applied to that block that you set in your MY_fuel_layouts.php file? If…
-
The path to the controller should be the advanced modules folder name "explorepics" then the controller name. So a controller located at fuel/modules/explorepics/controllers/jbproject, should have a non-routed path of "explorepics/jbproject/{method}…
-
I would keep the fuel/modules/fuel/controllers directory untouched in case there are updates. Move your controller to the fuel/modules/explorepics/controllers/ folder and change the route to the following: $route[FUEL_ROUTE.'jbproject/explorepics'] …
-
So browsing to the following URL gives you a 404 (substitute localhost with your server)? http://localhost/fuel/jbproject/explorepics/editgallery Is your routes file being loaded (is it named fuel/modules/jbproject/config/jbproject_routes.php)?
-
What are the URL requests being made that are giving the 404 errors?
-
In your form_fields method on your model you can change the "type" attribute of your field to a select and then set the options to the set values you want: ... $fields['my_field']['type'] = 'select'; $fields['my_field']['options'] = array('opt1' =&g…
-
What are your routes and what are the POST and AJAX call requests being made?
-
Yes. Not sure when yet but the 2.1.4 changes look pretty minimal so don't expect any issues (in fact the Migrations library fix was something we already had in FUEL): http://ellislab.com/codeigniter/user-guide/changelog.html
-
There was a regression bug added in a previous commit which has been fixed. Try doing a pull from the 1.0 branch again.
-
The fix actually created a regression bug that would occur when using the blog_comments module. This has been fixed now in the latest FUEL 1.0 commit.
-
When you say an "ExplorePics" module, do you mean an advanced module in the fuel/modules/explorepics (be sure to use all lower case instead)? Or do you mean a simple module in your MY_fuel_modules.php file? Or do you mean you added a controller to t…