Hey there, Awesome Customers!
Just a heads up: We'll be taking a breather to celebrate International Workers' Day (May 1st and 2nd - Wednesday and Thursday) and Orthodox Easter from Good Friday (May 3rd) through Easter Monday (May 6th). So, from May 1st to May 6th, our team will be off enjoying some well-deserved downtime.
During this time, our customer support will be running on a smaller crew, but don't worry! We'll still be around to help with any urgent matters, though it might take us a bit longer than usual to get back to you.
We'll be back in action at full throttle on May 7th (Tuesday), ready to tackle your questions and requests with gusto!
In the meantime, you can explore our documentation for Amelia and wpDataTables. You'll find loads of helpful resources, including articles and handy video tutorials on YouTube (Amelia's YouTube Channel and wpDataTables' YouTube Channel). These gems might just have the answers you're looking for while we're kicking back.
Thanks a bunch for your understanding and support!
Catch you on the flip side!
Warm regards,
TMS
I was asked by a client to build an integration between Amelia and Sessions.us. (I would love to see Amelia provide a native integrations with this great alternative to Zoom but until then...)
I would like to use a custom field to store the Sessions.us participant URL in a custom field of Amelia via API. My current issue is that I don't want users to see that custom field in the front end at any times.
Inside custom fields settings page there is no option to hide a field in the front-end (which would be useful).
Also in the DOM I cannot tackle custom fields at all because the devs didn't add any CSS classes/IDs that can be tackled: https://cloud.meer-web.de/zDfs7j1T
Is there any easy way I can hide a specific custom field in the front-end?
Warm regards,
Kevin
Hello Kevin,
Thank you for reaching out to us.
Please try the following CSS for this purpose and let me know if it works or not:
Looking forward to your reply.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Uroš,
thanks for your reply. Yes of course nth-child CSS will work for one static service but it can be hit and miss in the future. What if I use different custom fields for different services in the same catalogue? Then this will suddenly hide fields that are not wanted.
Why not at least add a unique ID to custom fields to identify an input field without risking hiding needed fields with a method like nth-child(...)?
Hello Kevin,
At the moment, this is the only solution as there is no unique identifier for custom fields in Amelia.
I will have this passed to our developers to have this implemented in the future.
In the meantime, please let me know if you have any other questions.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables