For your second question, try using just the model instead of the fuel_model function. That function has limited methods it can run on it (the find methods) and is just an alias to the model's methods. The reason is because it is one of the function…
Sounds like we need to track down which method is causing that SQL error. To do that, I would check the fuel/modules/fuel/controllers/module.php in the list_items method and see if you can track down which method in there is throwing the error.
The issue for number 2 has been fixed in the next release. The fix is the following in that file:
function pre_controller() { // if called from same Wordpress, the the global scope will not work global $method, $class, $RTR; $class_methods = get_…
Does it work if you remove the cookie and try again? If you continue to have a problem, you can try using the database to store your session (FUEL uses CI's Session library). Below is a link to more info:
http://codeigniter.com/user_guide/libraries/…
If you are using it for filtering the list view, then the _common_query won't apply. What does the query look like when you do $this->debug_query(); before the data is returned?
It sounds like you are getting a 404 error page. By default the header and footer are pulled into the 404 error page (see the fuel/application/errors/error_404.php). Is there a view file or controller that serves up that page?
Is this in the editing area? If so, you can add additional javascript by adding the "js" parameter to your simple modules configuration that contains the onclick javascript for the print behavior.
Sure. The function can be put anywhere and would recommend perhaps in your fuel/application/helpers/my_helper.php file which is meant for site specific functions and is automatically loaded:
// can exist in a helper function my_menu_func($label){ …
If you need a span tag injected, you can use the "pre_render_func" parameter, which takes a string value of the name of a function in which to do further processing:
function my_menu_func($label){ return = ''.$label.''; }
The container tag is t…
You can wrap your code with a tag to have it appear.
To use the fuel_nav function, you pass the parameter to it as a key/value associative array. With regards to your menu, can you just wrap the fuel_nav with your div like so?
<?=fuel_nav…
If you are still using the base module controller to render that list table view, then there is a variable called $pagination you can merge into your page.
There is a property set on the model called "upload_data" which contains an array of the uploaded data that you should be able to access from within your on_after_post hook
You can pass the parameter "filename" to the "file" type upload field. If you have a field that ends with "image" or "img" and it automatically creates the text field and upload field, make sure to target the file upload field in your form_fields me…
Unfortunately not at the moment.
However, the next major release we are working on will allow you to create different fieldsets as well as tabs to group fields together. Look for something at the end of this month.
Does it make a difference if you set the MySQL field type to "year" and remove your own custom validation.
For #4, it looks like it may be a typo... it should be $this->validator->add_rule(...).
With regards to usage, I would recommend using…
#3 and #4 should work but you may want to change the '4' to an int of 4. Also, if you set the field type to "year" the validation will be automatically made for you and you shouldn't have to add anything to your model.
What does the query look like after applying the search filter?
The query runs twice is expected and is used the second time to calculate the total number of rows for pagination (so no limit in the query).