It sounds like you are maybe wanting a filter on the list view that's perhaps a dropdown of all the events that you can select and filter the list by, correct? If so, are you using the 1.0 beta branch or the current master branch? The 1.0 beta branc…
This was actually something that was fixed in the 1.0 beta version:
https://github.com/daylightstudio/FUEL-CMS/tree/1.0
The fix I believe is to replace line 738 of the fuel/modules/fuel/libraries/Menu.php file with the following:
$links[] = $this-&…
If you view the source of the page, what does it actually output do you know?
The sitemap_xml.php file is there if you want to dynamically create your sitemap.xml file. There are various ways to pull in the locations of the pages (e.g. you can use …
Just to confirm, you have a page created in the CMS or a view file named test.php? Also, the CMS has been enabled in the MY_fuel.php config file correct and the fuel_mode has been set to 'auto' (if you are wanting to pull pages from the CMS)?
Are you sure you have .htaccess enabled on your server along with the mod_rewrite module installed? What kind of server environment are you running (e.g. MAMAP, WAMP, etc).
What if you add this to your MY_config:
$config['tables']['old_users'] = 'users';
And then in your model use:
function __construct() { parent::__construct('old_users'); }
Perhaps try using a different module key like "old_users". There are additional parameters you can set to customize the name, URI path, etc:
http://www.getfuelcms.com/user_guide/modules/simple
I wasn't quite seeing that js error but I think I may know what was causing it. I've posted some additional fixes for that to account for the nested repeatable fields. Please test on your end and let me know of any other additional issues.
Doesn't look like it's working correctly. I'll take a look at it to see if it is an easy fix. Ideally, you should be able to do something like this:
$fields['title'] = array('type' => 'linked', 'linked_to' => 'name');
You should be able to use the $posts array returned by Lance's example above and loop through it in your home view or layout file. If it is done in the CMS, you can use the Dwoo templating syntax in your layout input field:
http://www.getfuelcms.com…
Unfortunately, FUEL does not provide specific permissions to asset files and it is an all or nothing thing unless you create something custom which it sounds like you may be doing.
Both the on_before_post and on_after_post hooks don't actually return values. They should be used to manipulate the $_POST values (as in the case of on_before_post), or perform an action after the post (like change an images dimensions). If you are …
Aren't you specifying the 'active_class'=>'on'? If so, it appears to be working based on the output you've displayed above. Change to 'active_class'=>'active' or simply remove that parameter (since it's the default), and your menu should look…
Are you sure that is what is causing the error? That shouldn't cause a parse error.
http://stackoverflow.com/questions/2829581/why-do-php-array-examples-leave-a-trailing-comma
Isn't there a sidenav too? Also, what happens if you pass in 'active' => uri_segment(1) into the fuel_nav function to tell it which array key to highlight (assuming the uri_segment matches the key value of the menu item you want).
The save_related method was added to make it easier to save that relationship data. However, all it is really doing is deleting records from the relational table that belong to that member and then looping through the post values with a foreach and …
There is now an "asset" field type you can use in your form_fields method on your models like so:
$fields['image'] = array('type' => 'asset', 'folder' => 'images/my_folder', 'hide_options' => TRUE);
The new "forms" section in the user guide…
It's tough to tell what the problem is without knowing the entire $nav array value. However, for the top menu to display, you need to be on a page with a URI location that starts with or is the key value (e.g. home, events, gallery, feedback, contac…