Hi,
I notice, that not all items have CSS IDs on them. It would help a lot, if you could directly generate IDs for each DIV, SPAN.
In my case (see image) I would hide the complete DIV for a user. This can not be done easily at this time (I believe) - as it has no CSS ID.
If it would have an ID I could use a hook and hide this (or before building the page actually not even generate it).
Maybe the IDs can be autogenerated using a MD5 of the timestamp+fieldname when the field was created in AppGini - that should be unique. This way, you could show that unique ID to the developer and the developer could still rename it to something that makes more sense.
Olaf
More CSS IDs please
More CSS IDs please
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: More CSS IDs please
What about:
You can do whatever you want with your fields like hiding, locking (readonly), moving around, changing labels, aligning fields, ...
You can even create additional tabs in the children-tabs or wherever you want, move fields there, build a multi-column-layout, ...
From my experience, mostly everything can be done by selecting the fieldname and then using JQuery on the element.
So from my point of view there is no need for additional id-attributes.
Best,
Jan
Code: Select all
$j("#fieldname").closest(".form-group").hide();
You can even create additional tabs in the children-tabs or wherever you want, move fields there, build a multi-column-layout, ...
From my experience, mostly everything can be done by selecting the fieldname and then using JQuery on the element.
So from my point of view there is no need for additional id-attributes.
Best,
Jan
Kind regards,
<js />
My AppGini Blog:
https://appgini.bizzworxx.de/blog
You can help us helping you:
Please always put code fragments inside
AppGini 24.10 Revision 1579 + all AppGini Helper tools
<js />
My AppGini Blog:
https://appgini.bizzworxx.de/blog
You can help us helping you:
Please always put code fragments inside
[code]...[/code]
blocks for better readabilityAppGini 24.10 Revision 1579 + all AppGini Helper tools
Re: More CSS IDs please
Hi Jan,
well jquery is kind of a foreign (uncharted) land for me
So I dare to ask: Where would I need to put that code to hide the part marked in the screenshot?
Olaf
well jquery is kind of a foreign (uncharted) land for me
So I dare to ask: Where would I need to put that code to hide the part marked in the screenshot?
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
Re: More CSS IDs please
Hi Jan,
thanks again for your suggestion. I was able to implement this into the hooks _footer function and it works.
Olaf
thanks again for your suggestion. I was able to implement this into the hooks _footer function and it works.
Olaf
Some postings I was involved, you might find useful:
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view
SingleEdit - Prevent concurrent edits on records; Field Permissions; Column-Value-Based-Permissions; Custom (error) message; Audit Log; Backup your database; Two Factor Authentication; Block brute force (failed) logins; Add 2nd SAVE CHANGES button; Place a search on details view