Sorry, but I'm unclear as to what you are asking for. Are you wanting the data results returned from the table filtered view to not display all the columns? If so, see my post above about using the select statement.
Are you referring to the select options displaying all of the items or the data result being returned by the filters? I'm not sure what I'm looking at here.
You would need to turn of the event handlers for those links at a time delayed time after the fields javascript loads and instantiates those event handlers. I believe this is wha would turn off that event handler:
$(document).off("click", ".datatab…
In the model's list_items method, add a select like so:
public function list_items($limit = NULL, $offset = NULL, $col = 'last_updated', $order = 'desc', $just_count = FALSE) { $this->db->select('table.id, table.field1, table.field2...'); …
I would test it without your javascripting on the front end and without your CSS on the front end to try and target if it's either of those. Also, I'd made sure the HTML is well structured with all tags properly closed.
How many pencil icons (inline editing variables) do you have on the page? It can become a bit but much when there are a lot of them because there are resize listeners that are firing to adjust the pencil positions.
Hmm... inline editing seems to be working for me. Did you try clearing your cache? Also, the files are essentially concatenated and general whitespace is reduced. Is that not what you are seeing?
Tough to say and that version of FUEL is pretty old. Is the Docker container essentially the same environment from version of PHP and configuration, MySQL, Apache, etc as the Google environment?
What type of field is it in the database? If it's an int type field, an empty string is the equivalent to a "0". If you don't want a "0" then you'll need to set the default value to NULL. You may also need to add some code in an on_before_save model…
What version of PHP and FUEL are you using? Also, if you start removing PHP code that embeds those variables from within your layouts, does it help narrow it down to what PHP block may be causing the issue?
Do you have errors turned on (in the index.php). A lot of times if you see those __FUEL_MARKER__ it means the script has exited before it's had time to clean them up which it does during the rendering process.
This sounds symptomatic of the casing of base_posts_model.php. FUEL 1.4 has the CI 3 which requires models, libraries and controllers to be upper cased to "Base_posts_model.php". If you are on say a Mac (like me), it doesn't care about casing and wi…