Hmm... I'm not seeing that locally. Just so I'm sure, are you using the latest version? Also, could it be that it's not selected because the active menu item is not set correct. By default, the active menu item is the current URI path (e.g. about/hi…
There currently isn't a setting for that. However, the area to change that in the code is in the fuel/modules/fuel/controllers/login.php file on line 85 or so. However, any change to that native code will probably be overwritten on any updates.
Yes. The third attribute is an associative array that contains additional parameters you can pass to the function including "attrs"
http://www.getfuelcms.com/user_guide/libraries/asset
If you look at the fuel/application/errors/error_404.php file you'll see that require_once is used to include helpers that are needed to render certain pages. In this case you could use require_once(FUEL_PATH.'helpers/my_helper.php');
You can specify the $view_location property for your controller (above the contsructor), and set it to the name of the advanced module you want to pull your view files from.
$double_encode (not double quotes) is the 4th parameter and by default is set to TRUE for the htmlspecialchars function. That parameter is the second parameter in the prep() method.
That bug was fixed on the master branch a little over a week ago I think so chances are you don't have that fix. It was the change in the Form_builder
https://github.com/daylightstudio/FUEL-CMS/commit/e0b73f20f03ad8366dfcf88eab1353576792ff17
Is this process of loading the text file and generating the images reliant on the user inputted content or is self-contained and something you just want to include on the page? For example, can that logic be put into a library or function? If so, th…
Thanks for the report. That's been fixed in the master branch:
https://github.com/daylightstudio/FUEL-CMS/commit/45fa4d4089e8df21fa0734e103ded6351f4defba
Thanks for the report. I've just posted a fix for that in the repo here:
https://github.com/daylightstudio/FUEL-CMS/commit/a7e89db182b5cf2c65249b3d81f89accdeb1e23c
I think that should work. That would execute the add_edit method in the jqx controller. It just so happens that the name of the CSS class is also "add_edit" but the only relation between the two is that the jqx "add_edit" method contains the code th…
The index.php bootstrap needs to be in the root directory of your server if you want folks to be able to browse to the site at "/" instead of "/site". Depending on where the application and codeigniter folders are, you may also need to change the pa…
That tells jqx which method in the controller to execute on load after the initialization of the controller. The BaseFuelController.js is the default jqx controller loaded if no jqx Controller is specified. However, in some modules, they use their o…
A couple questions:
1. Is the index.php file the bootstrap index.php file?
2. What specific folders exists within the fuel folder?
3. What specific folders exists within the site folder (e.g. assets/... etc?)
It's because the values are getting set by Form_builders set_field_values method in the module controller and overwrites the values set in your form_fields method.
How we get around it in FUEL is to create a new field call 'new_password' and then …
Currently, the javascript functionality for that exists in 2 places. The first is in fuel/modules/fuel/assets/js/fuel/controller/BaseFuelController.js in the _initAddEditInline method which takes care of the admin. The second place is for inline edi…
Have you tried installing just a normal CI instance on the server to see if that works? I'm seeing similar issues in CodeIgniter forum posts with just normal CI installs and thought if it is just a CI issue we could solve that first then work with t…
What happens if you change the 'path' to just '/' instead?
Also, as an FYI, the cookie functionality is native to CodeIgniter:
http://codeigniter.com/user_guide/helpers/cookie_helper.html
Hmm... I just downloaded the demo version, configured the database and made the cache folder writable and am seeing the demo site.
Did you by chance change the fuel_mode in the fuel/application/config/MY_fuel.php to "views"? Also, in the views fold…
You can definitely run FUEL without .htaccess just like a normal CodeIgniter application. You will just need to add index.php to the "$config['index_page']" configuration parameter in the fuel/application/config/config.php file.