Mark Westguard
Forum Replies Created
-
Thank you again for providing the debug output and I apologize for the inconvenience caused. We did find 2 references to the table names that were not using $wpdb->prefix. We have fixed this and pushed the latest LITE version (1.8.133) which should hopefully solve this conundrum!
I am extremely grateful for your help!
Please let me know if this latest version fixes this particular issue.
Best wishes
Mark
Excellent detective work! We’re going to check that right now! We do take into account custom database table prefixes, but we’re going to double check that particular query.
Thanks again!
That’s correct, I did as you describe and it worked ok.
A couple of thoughts:
1. I wonder if another plugin is clashing with ours and affecting our ability to use Select2 on that search field? We are very careful to only load third party libraries on our admin pages but we’ve seen some other plugins just blanket load what they need on every admin page and that can sometimes cause problems.
2. It might be worth checking the browser inspector for any errors when you search to make sure a security plugin or something else might be blocking the search. Does it say ‘No results found’ after you search?
3. What type of computer (Mac/PC) and web browser are you using?
Thanks!
Mark
I did just check this out for you. I added:
– A location
– A category (Under Sell)I was able to search for both of these as terms in the Post data source without a problem. Our term search actually does a SQL search of all the terms in the database so there should be nothing that would prevent these terms from being filtered.
I tried this with the LITE and PRO versions and both worked fine.
The Sell, Buy etc categories do not appear to be WordPress terms, but you may wish to reach out to the plugin developer to confirm this.
There should not be any code you need to add.
If you could send an export of your form to support@wsform.com we’ll be happy to take a look at it to investigate further.
Thanks!
Mark
Hi!
Thanks for your inquiry.
Are you using the LITE or PRO version of WS Form?
Thanks!
Mark
Great! Thanks for letting us know!
Hi Bianca
Thank you for your inquiry and feedback!
There are two ways you can do that.
If you no longer want WS Form to save submissions, you can simply disable or delete the ‘Save Submission’ action. Click the ‘Actions’ (lightning) icon at the top of the layout editor to access the actions.
If you want to hide the submissions options altogether for certain users, we do have user capabilities that you can use with any popular WordPress user role editor.
https://wsform.com/knowledgebase/user-capabilities/
Many thanks
Mark
Hi Bjarne
Please upgrade to version 1.8.90 which is our official release for WordPress 5.8.
Thanks
Mark
Version 1.8.88 contains the fix for this.
Many thanks!
Mark
I was unable to recreate this error but I suspect there may be a certain condition in Pods that is resulting in our check for their forthcoming 2.8 release to fail. Our Pods integration takes advantage of some of the newer features that 2.8 has to offer, including groups.
We’ve made a very slight change to that check which should remedy this error and we’ll get it pushed shortly once testing is complete.
Thank you again for letting us know about this.
Mark
Ooh that is an impressive one! Let me set up the same test environment with 5.8 release candidate 4 and see if I get the same error. We’ll push an update ready for 5.8 if necessary.
Thanks for letting us know!
Mark
The cached version of the page does not represent what Google is indexing. It is just a cached version of the page source code. Google can and does read content generated by JavaScript and has done for many years, you can see this by using the Page Speed Insights:
Here is another example of searching for ‘consent to’ on Google on our domain, you will see that phrase ‘consent to’ is found on many pages containing our forms:
https://www.google.com/search?q=site%3Awsform.com+%22consent+to%22
I hope this helps.
Mark
Hi
This is a link to a page cached by Google. I see a form and everything appears normal.
If you have any further information you can provide, please email support@wsform.com and our support team will be happy to help further.
Many thanks
Mark
Hi
The forms do not use AJAX to render, the field data and form configuration are loaded with the page and are rendered with JavaScript to reduce server load.
If you test a page with PageSpeed Insights you will see that Google is able to read the form and all of the fields and content within it.
Many thanks
Mark
Forum: Plugins
In reply to: [WS Form LITE - Drag & Drop Contact Form Builder] Personal Data Export empty?Hi Bjarne
We found the gremlin! Data export was one of the very first things we coded into WS Form because we wanted to be GDPR compliant. Since then we’ve added a few new features to each submission record and we discovered a particular condition that was causing empty exports.
We’ve corrected this in 1.8.77 which we just uploaded. Please try upgrading to that version.
Many thanks for letting us know about this!
Mark