The header file you made the changes in is for the front end and not the CMS. You can include those JS files and CSS by adding them to the "fuel_javascript" and the "xtra_css" par…

A couple questions:

It depends on your implementation and customizations, but in general these are the steps and things to look out for:

Setting "required" => TRUE from within the form_fields method just adds the asterisk next to the field. A better approach would be to add "required" as a model property. Th…

Possibly. If the page is created in the CMS, and someone hits it from https, it will cache it with that site_url() value.

That fixed it, thanks.

I have the standard FUEL .htaccess file.

'assets_absolute_path' is set to false.

Are you using img_path() or site_url() to insert images? FUEL has added a second parameter to the site_url() function to force it to https if set to TRUE.

I am having an issue where cached pages seem to be served with image assets pointing to https rather than http. Since I do not have a signed certificate, this causes images not to display at all to u…

ok, seems running the cron from the actual cpanel user account, not in cron.d fixed that issue of it not running all the way. Also calling the model is working now. So, it must have been a permissi…

HI, thanks again for Fuel. I managed to get the cli bootstrapworking. https://github.com/compwright/codeigniter-cli-bootstrap with some modifications to the cron.php for some $server params for the …

I've pushed some changes to help with this issue. It involves an update from FUEL (so you can pull) and a change to the blog permissions to install a blog/settings permission:

The module I'm using with v1.0 is:

Has anyone updated this? It appears that GA has changed so much that the script isn't working correctly anymore

I found the issue. It had to do with the name having an underscore in it and the method being used to get the name of the module. That should be fixed in the latest push:

In 1.0 beta there is. It's found in the fuel/application/config/MY_config.php:

I actually saw that earlier today and pushed a fix. It's looking for a template file of {module}_module.php instead of {module).php.

You can create a controller anywhere, it just needs to inherit the Fuel_base_controller or if it's a simple module, the module controller (found in fuel/modules/fuel/controllers/) which itself inheri…

This was the commit that fixed the permission: