We're Moving to a New Support Platform – Starting June 1st!
We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.
You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.
While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.
We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.
Thanks for your continued support and trust – we’re excited to bring you an even better support experience!
Ever since the version 3.0 update, a new error has been introduced to my site. More specifically, an error with WPDataTables 'PlaceHolder' feature. Before this update, a user was able to click on a 'Tank' and be re-directed to a 'Tank Details' page that contained specific 'Reads" and other information about that 'Tank'. So depending on the 'Tank' that the user clicked on, the 'Tank Details' page was populated with different information. The way that it was working before, the '%VAR1%' in our JSON feed ( http://wpapi.farmchem.com/Range/%VAR1% ) was replaced with the 'Monitor Number' of the 'Tank' that was clicked on. Currently though, the default 'Monitor Number' we are using for table generation, is not being replaced anymore. So right now, its as if every single 'Tank' has the same information. I will attach a couple pictures that will hopefully simplify what I am trying to say... Thanks!
Edit:
We have reverted our WPDataTables back to version 2.8.3 and everything seems to be working the way it should. For some reason, the %VAR1% placeholders / shortcodes are not being recognized, and were causing the issue.
Hello Dalton
One of our developers is testing this right now. We haven't changed anything in regards to placeholders.
I'll get back to you as soon as I have more info about this.
Kind Regards,
Aleksandar Vuković
aleksandar.vukovic@tmsproducts.io
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
Can you clone your website?
If yes - I'll ask you to install the Duplicator plugin. It will generate a couple of files which you can send me (along with the log-in credentials), and then I can create an exact copy of your website, see what the issue is and try to resolve it.
Please note that the files will be too large to attach to the ticket, so you can upload them via wetransfer.com and just send me the link.
Kind Regards,
Aleksandar Vuković
aleksandar.vukovic@tmsproducts.io
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