That appears to be a bug. I've pushed a fix for it in the repo:

Here you go... just posted it on GitHUB... let me know if you have any issues:

If you are wanting to integrate with a social API, I'd recommend looking at it from a CodeIgniter perspective. Depending on the social network you are interested in, there's is more then likely a Cod…

Is it working for you OK?

Ah... I see. Yes, that is a CI error message.

Is this error message from using CKEditor?

I just created a new repo for this for the 1.0 version. Test it out here:

Also, you may want to look at the 1.0 beta if you haven't already:

The best way is to use GIT and set it up as a remote repository to pull from. Are you familiar with using GIT and setting up remote repos?

Admin, thanks for your reply.

Are you using 1.0 beta or the 0.93 master branch?

That is a repo that we control. We will eventually update the site to list other repositories. I'd recommend creating your own GitHub repo and we can list it here and tweet it out. Keep us posted and…

I ami using https://github.com/daylightstudio/FUEL-CMS.git . not working. Anyway please help to add header(h1 and h2 ) tag with ckeditor integrated with fuel.

Try using this instead:

Thanks. This is updated in the 1.0 user_guide:

The CRUD functions work when you route them to the fuel/modules/fuel/controllers/module.php controller. That module gets generated just in case you don't want to use the CRUD functions for you module…

The CRUD functions of an advanced module would essentially be the CRUD functions of any of its sub modules. The blog advanced module is a good example of this. Not that it has a fuel/modules/blog/con…

You would need to alter the fuel.css or add an $config['xtra_css'] in your MY_fuel.php which points to an additional CSS file that will be used to overwrite the current fuel.css.

Think of Advanced modules as another "application" folder. You can add your own models folder and module configuration file. More can be found here:

After talking with the server admin, the only thing he changed in server settings was to increase the LimitRequestLine value but he had already done that and it hadn't gotten rid of the error.