I have a table (ABR PTES, wpdatatable id=9), that has three columns which are foreign keys from other wpdatatables (10, 11, 12; btw, if I can use placeholders to limit rows on a relation, that would be preferable over having to create a table for every related lookup type :0) ).
All three columns are set up the same, see example screenshot.
All three columns are displayed but not enabled on the front-end add/edit screens, see example screenshot.
I'm sure I'm missing something obvious! Happy to provide access to the site if needed.
It seems you are having an issue with Dropdowns not working only on Front-End;
If i understood, the Back-End is working correctly, right?
1. Please try this first.
Go to the main plugin settings and disable/uncheck the option "Include full bootstrap on the front-end".
Then refresh the page with the table, and check if dropdowns are now working.
2. If that does not fix the issue, this might be a specific Conflict you have on Site, something else might be preventing our Table's Dropdowns from working on front-end.
wpDataTables is a WYSIWYG (What You See Is What You Get) concept-based plugin.
This means that the table should look the same both in the back-end and in the front-end. If your front-end table looks and behaves differently than in the back-end, this usually implies that there is another plugin (or the current theme) that's changing the behavior of our plugin.
Can you please change the theme and see if the issue is resolved?
If not, then please deactivate all other plugins except for our plugin, refresh the page where the issue is, and see if it is resolved (it should be).
If it is, then start activating other plugins one by one, and after each activation refresh the page to see if the issue occurred.
Once it does reoccur, you will have found the plugin causing the issue.
Let me know if you isolate the issue with these steps.
Argh. I should know to start with changing themes and deactivating plugins. It's just been that kind of year, I suppose. :0)
It was not working on either the front- or back-ends, I just hadn't tried the back-end specifically before querying
Anyhoot, it seem it was a combination of using a Full-Site Editor (FSE) theme (e.g., Twenty Twenty-Four) and the Tabs Responsive plugin.
If I switch to a non-FSE theme (e.g., Twenty Twenty-One) -OR- deactivate Tabs Responsive, both front- and back-end editing of wpdatatables work fine. I've been phasing out Tabs Responsive anyhow, so this will just make that go faster.
I am glad to see you isolated the conflict, thank you for passing these details to us.
We are making Note of it, to be aware for the future that the Tabs Responsive plugin has some conflict when used in combination with a Full-Site-Editor Theme.
Our developers will do their best to make some improvement/ or to possibly build a fix in the future, but i can't say a realistic ETA if or when that will be made possible.
For the time being, if that Plugin is not crucial for you, and it seems it is not if i understood, then you can just disable it;
but if it does become crucial sometime in the future, you can contact us again and we can try to debug the conflict with the help of our Developers - if that happens, we will just need a cloned version of your Site.
If anything else comes up, of course, don't hesitate to open new tickets.
I have a table (ABR PTES, wpdatatable id=9), that has three columns which are foreign keys from other wpdatatables (10, 11, 12; btw, if I can use placeholders to limit rows on a relation, that would be preferable over having to create a table for every related lookup type :0) ).
All three columns are set up the same, see example screenshot.
All three columns are displayed but not enabled on the front-end add/edit screens, see example screenshot.
I'm sure I'm missing something obvious! Happy to provide access to the site if needed.
Attached files: 2024-01-08 9.59.59 AM.png
2024-01-08 9.56.38 AM.png
Hi Becca,
Apology for a late reply.
It seems you are having an issue with Dropdowns not working only on Front-End;
If i understood, the Back-End is working correctly, right?
1. Please try this first.
Go to the main plugin settings and disable/uncheck the option "Include full bootstrap on the front-end".
Then refresh the page with the table, and check if dropdowns are now working.
2. If that does not fix the issue, this might be a specific Conflict you have on Site, something else might be preventing our Table's Dropdowns from working on front-end.
wpDataTables is a WYSIWYG (What You See Is What You Get) concept-based plugin.
This means that the table should look the same both in the back-end and in the front-end. If your front-end table looks and behaves differently than in the back-end, this usually implies that there is another plugin (or the current theme) that's changing the behavior of our plugin.
Can you please change the theme and see if the issue is resolved?
If not, then please deactivate all other plugins except for our plugin, refresh the page where the issue is, and see if it is resolved (it should be).
If it is, then start activating other plugins one by one, and after each activation refresh the page to see if the issue occurred.
Once it does reoccur, you will have found the plugin causing the issue.
Let me know if you isolate the issue with these steps.
Thank you.
Kind Regards,
Miloš Jovanović
[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 Miloš ,
Argh. I should know to start with changing themes and deactivating plugins. It's just been that kind of year, I suppose. :0)
It was not working on either the front- or back-ends, I just hadn't tried the back-end specifically before querying
Anyhoot, it seem it was a combination of using a Full-Site Editor (FSE) theme (e.g., Twenty Twenty-Four) and the Tabs Responsive plugin.
If I switch to a non-FSE theme (e.g., Twenty Twenty-One) -OR- deactivate Tabs Responsive, both front- and back-end editing of wpdatatables work fine. I've been phasing out Tabs Responsive anyhow, so this will just make that go faster.
Thanks for your help!
Becca
Hi Becca,
I am glad to see you isolated the conflict, thank you for passing these details to us.
We are making Note of it, to be aware for the future that the Tabs Responsive plugin has some conflict when used in combination with a Full-Site-Editor Theme.
Our developers will do their best to make some improvement/ or to possibly build a fix in the future, but i can't say a realistic ETA if or when that will be made possible.
For the time being, if that Plugin is not crucial for you, and it seems it is not if i understood, then you can just disable it;
but if it does become crucial sometime in the future, you can contact us again and we can try to debug the conflict with the help of our Developers - if that happens, we will just need a cloned version of your Site.
If anything else comes up, of course, don't hesitate to open new tickets.
Thank you.
Kind Regards,
Miloš Jovanović
[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