I just tweeted it out:

There is an issue in MY_Model that isn't returning the id after save. I've posted a fix for 0.93:

The FUEL 0.93 demo site came with a contact controller and corresponding view file as an example. Note that you access it at "contact" and NOT "fuel/contact".

This should be fixed in the 1.0 branch. It's no longer using the blog_categories_to_posts_model but instead using the new relationships functionality in 1.0:

I'll try and answer many of your questions below:

No problem. Be sure to download and install the user guide module for 1.0 beta. The Form_builder class was overhauled a bit as well as a bunch of new features and bug fixes.

That's indeed a bug. I just pushed a fix to the 1.0 branch:

Try using the type of "enum" instead of "checkbox" which will give you radio buttons. Is this using 0.93 or the 1.0 beta branch?

That error is because of the route I think and it's defaulting to the module.php controller which in this case we don't want since Flexi cart has it's own controllers.

No problem. The documentation is under the Fuel Pages Class in the 1.0 user guide. If you don't have the 1.0 user guide, you can download it on GitHub here and install it as a module in your FUEL ins…

I believe this issue has been addressed in the 1.0 beta where it grabs the final uploaded file name from the Upload classes data function before saving:

Did you perhaps download the newer 1.0 beta branch?

If you are using 0.93 (the master branch), you can follow the directions here:

FUEL does not have anything out of the box unfortunately.

There is in the 1.0 beta branch (along with a slew of other new features):

Is the upload happening from within your own module or is it happening in the Asset module? Is this with the .93 branch? If so, you may want to try out the 1.0 beta branch which has addressed a coupl…

I just found a couple issues with this function when trying to use a model and have it pass data to the view. You can also use the generic variable "$data" as well as "$poll_questions&…

Thanks for the report. I've just pushed a fix for this in the 1.0 branch:

Check out the 1.0 beta branch and User Guide for more info:

You may need to have a route for tools/index/$1. IE explicitly set the method to index.