-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
Hide Add
- Thread starter automan25
- Start date
cheesegrits
Support Gopher
It isn't an option for the menu, but you can copy the list, turn off the Add button in that, and use that copy for your menu item.
-- hugh
-- hugh
cheesegrits
Support Gopher
You are the first person ever to ask for that feature. When it comes to adding new options, our rule of thumb is we add it if 80% of our users would find it useful.
The whole point of being able to copy lists is so you can configure different "views" onto the same data. The menu setting overrides are just a convenience for overriding some of the most common settings on a per-menu basis, like pre-filters, which elements you display, etc. For "fine grain" stuff like hiding or showing specific buttons or menus, list copying is what you need.
Just to be clear, a copy of a list still sits on top of the same underlying table, operating on the same data. It just gives you a separate collection of list / form / group(s) / elements that you can configure differently.
-- hugh
The whole point of being able to copy lists is so you can configure different "views" onto the same data. The menu setting overrides are just a convenience for overriding some of the most common settings on a per-menu basis, like pre-filters, which elements you display, etc. For "fine grain" stuff like hiding or showing specific buttons or menus, list copying is what you need.
Just to be clear, a copy of a list still sits on top of the same underlying table, operating on the same data. It just gives you a separate collection of list / form / group(s) / elements that you can configure differently.
-- hugh
[/quote]I hear you. You can't add every feature ever requested. 80% is a good rule of thumb for sure. I guess I'll have to start thinking of lists differently then and not be afraid to make a copy if the situation warrants it. I'm just hesitant to make too many though for risk of over-complicating my application.[/quote]
It doesn't really over complicate it. Just think of it as different views onto the same data. Yes, you wind up with more objects in the backend pages, but that's why we provide filters.
Note that when you copy lists, the elements in the copy start of "linked" to the original, so they inherit all their settings from the original. You can opt to unlink individual elements and configure them separately. And if you add an element to the original, it gets added to the copies (although it gets added to the first, default group (the one containing the PK) on the copy, as there's no guarrantee your group structure will be the same on the copies).
-- hugh
It doesn't really over complicate it. Just think of it as different views onto the same data. Yes, you wind up with more objects in the backend pages, but that's why we provide filters.
Note that when you copy lists, the elements in the copy start of "linked" to the original, so they inherit all their settings from the original. You can opt to unlink individual elements and configure them separately. And if you add an element to the original, it gets added to the copies (although it gets added to the first, default group (the one containing the PK) on the copy, as there's no guarrantee your group structure will be the same on the copies).
-- hugh
Last edited by a moderator:
