I am trying to integrate Phil Sturgeon's REST Server (https://github.com/philsturgeon/codeigniter-restserver) and my existing models keep saying the following:

Glad you are finding FUEL CMS useful and thanks for the insight.

You can find an extension for group permissions here:

That is an Apache error. It sounds like it may be something on your server. Sometimes the https web folder is different then the normal http web folder (Media Temple does this on a Dedicated Virtual …

It is via a controller called signup.php that has simple code that replaces http with https if it isn't already there. It's definitely something to do with my web server itself because right now if …

I have the need to encrypt some form pages on my website and I'm basically using a function that redirects to an HTTPS URL and it is giving me a 404 Page can not be found error:

Tried to do something about it, hope it works:

That's a bug. I've pushed a fix for that. Thanks for the report.

I think may already have what you need. By running the "git checkout -b demo origin/demo" command, you've created a local version of the branch. You should have those files locally from the…

Bare with me hear... I'm still not able to replicate it locally, so a couple more questions:

I assume this may be the same problem I am having. I see 3 branches on the GitHub website but the URLs all say https://github.com/daylightstudio/FUEL-CMS.git so this is the version I downloaded. Ho…

With regards to your questions:

Are you using the latest version found here?

I've just posted a fix for this.

I'd recommend downloading the "demo" branch which is kept up to date:

That looks like a bug. I've posted a fix for that. It had to do with the models default_date property being set to '0000-00-00' which is seen as "not empty". It was changed to 0 and it now …

That looks like a bug which I've posted a fix for so you can get a proper 404 error. It happens if you are using a controller that doesn't have a method or in your case you may need to use _remap.

A couple questions?

That is a bug. I've posted an update for that:

Thanks for the report. That's indeed a bug. I just posted a fix. I added 'user_name' to the unique_fields model property: