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
[This is similar to ticket #13002 which has no solution]
My tables containing 2 fields that are editable with dropdown menus (single-value inputs) have the following issue:
- The fields with dropdown menus are overwritten when another field is edited.
- Their value is replaced by the 1st value in the dropdown list.
I can't give you access to my website. Thanks for your support.
Emma
PS: I solved it using SQL routines to catch the overwritten values. It works, but it's not clean.
Hi Emma,
I didn't get access in that case either. It is really difficult to fix this if can't see the problem. I tried it in my local environment, based on your instructions, and I couldn't replicate the problem. If you positive about not giving me access please send me some screenshots of your table data as well as table and column settings so I can get a clearer picture of what is going on. Any additional information could be helpful.
Also you can try in our
sandbox site
user: demo
pass: demo
to recreate a problem just to see if this is a bug in plugin or the problem is your setup specific
Hi Miljko,
Thanks for trying to recreate the problem. It's difficult to recreate on my side too. I made several views of the same SQL table (with small differences in fields & conditions of the related SQL queries) and they behave differently. I could not find the settings that yield the bug.
The bug disappeared after rebuilding the view as follows: 1) Take the field out of the view; 2) Put back the field, with "in-line" editing and without changing the field label; 3) Set the editing option to "single-value"; 4) Set the field label.
With this procedure I wanted to recreate the bug, and instead it solved it. Besides, the bug never occurred if the editing was set to "in-line".
Let me know if I could provide more information,
Emma
Hi Emma,
I'm glad to hear that that the bug is gone now. It looks like some settings was wrongly saved and that they are causing this bug. If this behaviour reaper please note your last steps so we can reproduce it and solve it. Thank you for reporting this