Add "mode" => "radios" which will force them to be radios.
With regards to combining form_helper and form_builder, I'm not sure I understand how you would want to combine them. Form_builder generates entire forms and form_helper generates single…
1. You can use the lang('my_key') function to echo lines from a language file (the language file must be loaded first.
2. Is this a text field with the markItUp! editor and you are inserting the image from markItUp!?
As a side note, the 1.0 beta h…
You can use an array syntax for the function call like so array($this->validation, 'numeric'), or you could simply use the native "is_numeric" function. The CI validation library must first be loaded though.
You can use a "code" tag to put code in the Forum.
I don't see any issue with your method to use a controller and route to get the contact-us page.
As a side note, if you are just new to FUEL, I'd recommend checking out the 1.0 beta branch. Lots o…
That is usually an indication of mod_rewrite not working. Another possible thing to try is the following:
http://ellislab.com/codeigniter/user-guide/installation/troubleshooting.html
It sounds like you are wanting to have multiple websites with a single installation? If so, FUEL does not really support that unless you setup a completely different application directory and database for each site.
The view locations correlate to …
So it sounds like is FUEL installed in a "foo-fuel" subfolder? If so, these should be the links to your home page:
http://184.154.x.x/foo-fuel/ (HOME)
http://184.154.x.x/foo-fuel/home (ALSO HOME)
http://184.154.x.x/foo-fuel/index.php (ALSO HOME)
Th…
I'm not quite sure I understand the last part where you say it "only works the front-end". If the page is deleted, in the CMS, then it will default to the home.php view file if it exists and if the "fuel_mode" in the fuel/application/config/MY_fuel.…
To get rid of the markers you need to get rid of the errors. To get rid of the errors, you'll need to pass in those variables in your controller like so:
function index() { $vars = array(); $vars['css'] = array(); $vars['js'] = array(); $vars['body…
If you are a newbie, I'd perhaps look at the 1.0 beta branch which uses the jQuery UI datepicker. It also allows you to create custom form fields with there own css and js. The user guide module provides a lot more information too.
https://github.co…
With 1.0, those are now separate modules which can be found at the link below. To install, you can download the zips and put them in the modules folder with the same names used in 0.9.3.
https://github.com/daylightstudio?tab=repositories
Thanks for sharing. We have thought about it and it is something we will continue to evaluate. It would be a massive undertaking and wouldn't happen quickly but does sound intriguing.
Thanks for sharing. I commented on it about the 1.0 beta and to clarify a couple things about the name.
http://phpmaster.com/getting-started-with-fuel-cms-1/#comment-58490
We added prefixes to model names which caused the blocks_model error. The FUEL authors error had to do with another fix. I've pushed fixes up for both those errors. Thanks for the report.
Nope. It's just separated out into it's own module along with others (e.g. user_guide, backup etc)
https://github.com/daylightstudio
To install, download the zip file:
https://github.com/daylightstudio/FUEL-CMS-Blog-Module
Then place it in the fue…
I would try debugging the $posted variable around line 712. That is where it looks in the $_FILES variable for related $_POST values to set in this case the file name.
By default, models come with the following property that will auto validate fields. The key is a regular expression to match the field name and the value is the function it maps to:
public $auto_validate_fields = array( 'email|email_address' =>…
For the navigation module, it should be automatically clearing the page cache when creating/editing in the CMS. Were you needing the Dwoo compiled cache cleared in addition to the page cache for the navigation module? The Dwoo compiled cache holds t…
it's because you are using a join that has a name field in it. Try prefixing the column name with the table name before adding it to the order_by statement
Have you tried removing the order_by part that you added? You will also need to change the second to last line to the following:
parent::list_items($limit, $offset, $col, $order);
If you are needing to sort it by default you can use the "default_co…