I have updated some plugins today. Now, when I tried to change the price of a product variation, the product variation now displays as "array" on the front end
Please update the plugin to the latest version 3.8.3 and try again.
If you still encounter the error, please provide your website credentials (wp-admin link, username, and password) or create a development or staging site with an identical configuration so I can investigate any issues.
I'll get a staging site set up later today, as the site is live and taking sales and send you a link
I've also noticed that the word 'array' appears in WPC Variations Radio Buttons "custom name" field in the backend. I've deleted it but the site hangs when I save. Also, on checking the console I am getting a admin-ajax.php error. When I view the response I get a 500 internal error.
I was in the process of setting up a dev server when I saw there was an update to the plugin. I installed the update and the problem seems to be solved. Thanks!
I have updated some plugins today. Now, when I tried to change the price of a product variation, the product variation now displays as "array" on the front end
Hi Dave,
Please update the plugin to the latest version 3.8.3 and try again.
If you still encounter the error, please provide your website credentials (wp-admin link, username, and password) or create a development or staging site with an identical configuration so I can investigate any issues.
It's still working well on our demo: https://demo.wpclever.net/woovr/
Best regards,
Dustin
Hi Dustin,
I'll get a staging site set up later today, as the site is live and taking sales and send you a link
I've also noticed that the word 'array' appears in WPC Variations Radio Buttons "custom name" field in the backend. I've deleted it but the site hangs when I save. Also, on checking the console I am getting a admin-ajax.php error. When I view the response I get a 500 internal error.
Hello again, Dustin.
I was in the process of setting up a dev server when I saw there was an update to the plugin. I installed the update and the problem seems to be solved. Thanks!