Hmm... we have ran into that issue a couple times without much luck in able to track it down or replicate the issue. We issued a potential fix in a Dec 23rd commit, however, this was before v1.4 which would seem that it's still potentially an issue.…
That usually suggestions that the script stops execution during the rendering of the page before it can do the final cleanup of removing the inline editing fuel markers. Those markers are used to create span tags for inline editing and won't show up…
Although it may not have all the features of image crud, you can create a simple module with the fields you want to associate with the gallery and perhaps enable the tags module in MY_fuel_modules.php to create associations. Generating a simple modu…
I'm not quite sure I understand the question entirely but I'll take a stab. Normally we'll create a main navigation which contains all the navigation items of the site. Then we'll use various fuel_nav() parameters such as the "depth", "exclude" or "…
On line 294 of the Base_module_model in the list_items method, you can uncomment the $this->debug_query(); line to see what the actual query is. The display_field value automatically gets included in the filters list. If you don't want that, you …
Do you have a field of "user_name"? If so, is it set as the "display_field"?
LOWER(contestants.user_name) LIKE "%orla% is coming from parent::list_items method call which is referring to the Base_module_model::list_items() method which subsequently…
If you change the hook key from "before_create_whatsons" to "before_create_module", does it run (that is a generic hook name that will run for every module)? Basically, the fuel/modules/fuel/controllers/module.php file "_run_hook" method should be g…
Unfortunately not unless you want to use the"styles" parameter which can mass assign class names to "li" elements. Other parameters need to be added on a per navigation basis.
So just to be clear, this didn't work, meaning your fuel/application/models/Whatsons_model::before_create_whatsons() method was not called?
$hook['before_create_whatsons'] = array( 'class' => 'Whatsons_model', 'function' => 'before_…
I think the issue may be because you specified the "module" parameter to "whatsons", which is actually the advanced module's name (I know that is a little confusing) and you can actually leave that empty.
That's correct in that it needs to be set for each menu item. The "styles" parameter can be applied within the fuel_nav function which can apply to a whole set of menu items but is used only to set classes (like in your example).
The reason why is because, it gets overwritten with a call to Form_builder::set_field_values() method which usually contains the values of the models find_one_array. You can specify an "edit_method" for you module in your MY_fuel_modules.php file wh…
Actually, module hooks only work for simple modules. What you have, looks like it should work.
Just to confirm, you have an advanced module called "whatsons" at fuel/modules/whatsons. In that advanced module you have a model named Whatsons_model a…
Ha... I didn't even no that parameter existed for logging. I've posted an update to the develop branch so that the redirect_404() function call will automatically log the URI path before redirecting (this function will first check for a redirect bef…
By default, the fuel/application/errors/error_404.php file, the same one CodeIgniter uses, is used to display the 404 error. However, there are a couple other ways to create the 404 error page:
1. Create a view file called "404_error". This will be…
So was the navigation in the CMS? If so, it may be using the last connection that was loaded. Perhaps try loading the database again right before calling fuel_nav using:
$this->load->database($dsn, TRUE, TRUE);
Where $dsn is your database conn…
I noticed in your event_fuel_modules.php file that the key is "user" which will conflict with FUEL's "user" module. Each module key needs to be different or they will replace one another. Try using "event_user".
Check your javascript console to see if there is an error in the loading of the list content. It get's AJAXed in and if there is a SQL error it may be throwing a 500 error and won't be properly loading the content into the list view.