In FUEL 1.0 beta markItUp! and CKEditor use the same image select/upload functionality:

I do see your pull request so thanks. However, it looks like it is merging with the master branch instead of the 1.0 branch? If that is the case, here is some docs on how to do it on a specific branc…

Hmm... i've edited the fuel_lang.php on github. Now there's a patch1: https://github.com/daylightstudio/FUEL-CMS/pull/184

What is the language associated with the user you are logging in as? To change that language value you can click on the user name in the upper right corner and edit the user name value associated wi…

Hi All,

Sure. As an FYI, the FUEL 1.0 beta has added much better support for multiple language sites if you are not already aware:

Are you looking for a "point" type field generated by Form_builder? If so, there currently isn't one but this sounds like an opportunity to add one. I haven't really worked with that field …

This is an older post. A lot of updates have been made in the 1.0 beta regarding better integration with CKEditor. I'd highly recommend checking it out here:

FUEL doesn't really have an articles and pages difference. You can create pages, which have predefined layout fields you fill out in the CMS. Or there are modules that are usually wrappers around dat…

In short, I would say yes. You could use something like relationships in the 1.0 beta to make associations between articles and pages in the CMS.

Are you referring to the 1.0 beta? If so, you can do that by adding a "settings" array that uses Form_builder syntax for form fields in the settings area. The blog.php config file for 1.0 h…

Here's a screenshot of the issue - looking at the source code, the nested "window" is actually a 404 page.

The quickest way would be to use git to merge the latest Fuel 1.0 branch (https://github.com/daylightstudio/FUEL-CMS/tree/1.0) on github & run the fuel_1.0_schema_changes.sql in fuel/install/…

So if you debug the $_POST value on line 22 of the settings.php controller file, do you see that value in there? Also, I believe the 'type' value should be removed from $fields['top_image'] so as to …

So you are associating multiple plans with each plan feature? If so, the 1.0 beta provides a has_many property you can specify in your model which will automatically create a multi select box for you…

The 1.0 beta is:

We currently use Beanstalk for our hosted GIT repositories and they have a wonderful deployment feature that can be set to automatically or manually push files:

The documentation has been improved quite a bit in the 1.0 beta if you are interested:

1. Every project is a little different but our internal experience is pretty painless. There are a couple things to look out for. The User permissions lookup table has been removed in favor of the ne…

Hello,