I think this long thread my be the answer you need. You'll need to probably lowercase the controller and model names in the fuel/modules/blog/models and fuel/modules/blog/controllers folder. This is …

Thanks for the report. I've posted a fix for that issue. It had to do with some core changes to how the main CodeIgniter class is executed and required a small overwrite for the show_404 Exception me…

Hi,

I've just checked out the latest version of fuel and done a fresh install of the form module and I have been able to replicate the issue.

This has been added to the develop branch:

I've pushed an update to this in the develop branch so you that there is now an additional "row_delimiter" parameter you can pass to the custom field:

I've pushed a fix for that:

There is a fix in the develop branch that may help which you could try and cherry pick:

Twitter 'image', 'title' and 'description' as CMS fields (maybe 1 extra for 'type'), a helper to do the meta tag rendering (as there is for the OG tags). The social config could hold the account spec…

There is a $config['nav'] array that can be altered in your fuel/application/config/MY_fuel.php

Thanks for the report. I've posted a fix in the develop branch. The develop branch contains CI 3, however, you could cherry pick this commit into your code:

Is this for the backend? I have a CKFinder based replacement for Fuel Assets which will do that.

There was a commit made yesterday to address this:

I just pushed a fix for that:

By default, FUEL uses normal CI cookies sessions which can be configured in the fuel/application/config/config.php file.

It turns out a lot of the permissions are missing from the migration.sql files, based on those listed here: https://github.com/daylightstudio/FUEL-CMS/blob/master/fuel/install/fuel_schema.sql#L166

old permissions:

OK. I've pushed an update to the develop branch for this. The develop branch includes an update to CI 3.0 and may require a bunch of other changes (in particular casing of files) so I would do the up…

I think I see the issue. I've posted a fix to the repo:

This may be a better demo (it's on a slightly older version but more relevant):