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
-
Nice... will check it out.
-
Does your fuel/modules/forms/models/Forms_model.php have that line in it?
-
The fix was to the master branch of the Forms Module: https://github.com/daylightstudio/FUEL-CMS-Forms-Module/commit/285c2021b3f2d81be0ab647d013a5471abb3f1d9
-
This is how the default version of CI is as well: https://github.com/bcit-ci/CodeIgniter/blob/develop/application/config/profiler.php https://www.codeigniter.com/user_guide/general/profiling.html?highlight=profiler
-
Thanks for the report. I've posted a fix for the get_return_url issue. Regarding setting an initial value, I've added an additional field labeled "Default value" in which you can set defaults that should help.
-
The social blog helper no longer is supported and it looks like the blog documentation needed to be updated to reflect that. There is however a FUEL social helper that may be helpful: http://docs.getfuelcms.com/helpers/social_helper
-
FUEL only supports the mysqli driver.
-
This appears to be an issue with the Form_builder class auto assigning a default value for the min and max. In your case if you view source, you'll see 2 max and min attributes on the element I'm assuming. To fix, in the Form_builder::create_number…
-
The code for that is in the core JS file at fuel/modules/fuel/assets/js/fuel/custom_fields.js around line 241. I've just pushed this fix to the develop branch: https://github.com/daylightstudio/FUEL-CMS/commit/2101231bc08ed81aed830a818b4938c808303…
-
Did you include code in your view file to include the form and have you configured it in the fuel/application/forms.php file? <?=form('my_form')?>
-
Can you replace the parameter value with the full http path? The img_path function should utilize that path and ignore it the generated relative path (it detects the http://).
-
Thanks for you interest jankube and willingness to help. Our current development status is to roll out 1.4 probably later this month which will include the CI 3 update and follow up bug fixes and minor updates. The Asset area is in need of help and …
-
There is also a "parent" parameter which specifies where to start the navigation from in the hierarchy.
-
That's how we normally do it as well using the uri_segment function and concatenating if necessary.
-
Try changing the Controller file name from Cronjobs.php to a lowercase cronjobs.php. Those modules have been updated to work with the upcoming 1.4 release which is on CI 3.x and requires capitalized file names.
-
Try adding the => to make the where condition an assoc array: $tag = fuel_model('tags','one',array('slug' => 'my_tagname')); // INSTEAD OF $tag = fuel_model('tags','one',array('slug','my_tagname'));
-
BASE_URL is defined in the fuel/modules/fuel/config/fuel_constants.php file which is included in from the fuel/application/config/constants.php. This file is one of the first things included upon initialization (see fuel/codeigniter/core/CodeIgniter…
-
I believe these were the links being referenced: http://forum.getfuelcms.com/discussion/comment/9501#Comment_9501 http://forum.getfuelcms.com/discussion/comment/8282#Comment_8282
-
What are some of the errors you are seeing?
-
What system paths are you referring to?
-
I would recommend removing the "featured_image_upload" field and instead replacing it with just the "featured_image" field and set display_input and display_preview to TRUE: $fields['featured_image'] = array('type' => 'file', 'ignore_representat…
-
Also, could you post the table schema you are using for the module?
-
Are you on 1.3.2 (master) or 1.4 (develop)?
-
We should hopefully be rolling it out within the next month and encourage folks to test it out.
-
How are you currently implementing it with both FUEL where it's not working and CodeIgniter where it is working.
-
You are correct in that my suggestions were for if the sites were located on the same server so I'm not sure if what I've suggested above will quite work for you.
-
The fuel/modules/forms/libraries/Fuel_forms.php file has a method in it called rendered_vars around line 1215. I believe a change to that method may help you out as opposed to adding a call to the session library in your forms.php config to set the …
-
The fuel_var function is really only intended for view files if you are wanting to add the inline editing functionality. You can always access a variable simply as the variables name (e.g. $my_var) in your view file too. If you are adding them to th…
-
Because FUEL CMS is a intended to be a hybrid between a CMS and framework, it will depend on how far you go into the framework side of things... meaning, if the sites require their own application directories, modules, view files, layouts etc. Alth…
-
In your form block, are you creating the form fields or relying on the Forms module to generate the form? If you are creating your own fields, the fuel/modules/forms/controllers/Forms.php controller sets a "posted" flash data variable that can be ac…