Tags that were specified like [xxx_payment_button id=”xxxxx”] can no longer be used after the update. It’s no longer usable and the functionality has been downgraded. Can you fix this as soon as possible?
This topic was modified 1 year ago by wrdprss3917.
In order to investigate the issue and find a solution, could you provide a bit more detail on what you’re experiencing? Any additional information or specific examples would be helpful as we look into this further.
Is ” [xxx_payment_button id=”xxxxx”] ” a shortcode?
Did you try clicking one of the buttons in your table to edit it, look for the Advanced option on the bottom right, then after clicking scroll down to the Shortcode field and enter your shortcode. Like this – https://pasteboard.co/GfTzrYyALEau.png
Is ” [xxx_payment_button id=”xxxxx”] ” a shortcode? Yes, it is. I was using this in the bullet points of the “features offeerd”, but it is no longer available.
This reply was modified 1 year ago by wrdprss3917.
To assist you, please confirm with us which plugin you are using the shortcode for. We want to use a shortcode from that same plugin in the table and see what happens. When I tested other shortcodes, it worked.
Thank you for your reply and for sharing the details.
I installed the “Simple WP Membership” plugin and built a PayPal button using the swpm_payment_button shortcode, and it worked on my end – https://pasteboard.co/V5S61DdzpqxS.png
Could you confirm whether you are creating a new table or editing an existing one when adding the shortcode?
Additionally, it would be helpful if you could provide specific instructions on how you created this button. For example, did you follow any specific steps in the plugin settings, or are there particular attributes or configurations you’re using in the shortcode?
Once I have these details, I’ll test it further to help replicate your exact setup.
When I checked, I found that when I created a table with a shortcode, the double quotation marks (“) used in the shortcode were replaced with escape characters. https://pasteboard.co/d4nDQRo0dxl2.png
On the other hand, when I created it on a static page, I was able to make the shortcode work. The double quotation marks remained. https://pasteboard.co/CTYhZyuotSna.png
When trying to publish, an error occurs and it fails, as shown in the image. In this case, the default table is left as is and no changes have been made.
I recommend trying to build a new table going forward.
Regarding the error message, is this for Easy Pricing Tables 4.0.1 or 4.0.0? If not yet updated to version 4.0.1, please try updating and clearing your internet history. If the issue continues, please let us know your WordPress and PHP version on your website.
I wasn’t able to replicate the issue on my own site with the same PHP and WP versions. Let’s try a few more things to narrow down the cause:
Could you try temporarily switching to a default WordPress theme (like Twenty Twenty-Three) to see if the issue persists? This helps rule out potential conflicts with the current theme.
Please try deactivating all other plugins except Easy Pricing Tables and see if the issue still occurs. If the error disappears, reactivate each plugin one by one to identify the conflict.
Would you be able to check for any JavaScript errors in the browser’s developer console while trying to save the table? You can open this by right-clicking on the page and selecting “Inspect” > “Console” tab. Any errors here might give us more insight.
Sometimes, server settings can cause issues with JSON responses. Could you check with your hosting provider to ensure that there are no restrictions (like mod_security rules or other server settings) blocking the requests?
Try clearing any server-side cache and your browser cache. It might also help to clear your database transients, which can be done using a plugin like “WP-Optimize.”
Have you made any changes to the Gutenberg builder? Such as using the classic editor plugin?
I wanted to follow up to see if you’ve had a chance to do further testing to identify what might be triggering the JSON error. We’re eager to get this working for you and are here to assist in resolving the issue.
If you’ve noticed anything new or have been able to try any of the suggested troubleshooting steps, please let us know. Even small details could help us narrow down the cause and find a solution more quickly.
