- This topic has 6 replies, 3 voices, and was last updated 6 years, 3 months ago by .
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP Photo Seller › WP Photo Seller – Warning after checkout
I am using WP Photo seller and the plugin is performing actually according to my needs, however the customers get this warning message after checkout:
Warning: count(): Parameter must be an array or an object that implements Countable in /home/.sites/972/site4696242/web/wp-content/plugins/wp-photo-seller/views/cart-wps-new-tabular.php on line 223
Please let me know what to change in order to get rid of this error message.
What version of PHP is your server running?
This is my PHP settings:
PHP Version: 7.2.8
PHP Memory Usage: 72.45 MB
PHP Memory Limit: 320M
PHP Max Upload Size: 200M
PHP Max Post Size: 200M
PHP Allow URL fopen: On
PHP Allow URL Include: Off
PHP Display Errors: On
PHP Max Script Execution Time: 100 Seconds
We just made a little change to the plugin that should solve this. Can you please load a new copy of the plugin to your site now:
https://support.tipsandtricks-hq.com/forums/topic/re-install-or-load-a-fresh-build-of-the-plugins
Unfortunately I have bad news, I just downloaded your adapted version as instructed (deleting the plugin and then re-installing it) and got now the following error messages instead:
Fatal error: Uncaught Error: Call to a member function clearPromotion() on boolean in /home/.sites/972/site4696242/web/wp-content/plugins/wp-photo-seller/views/cart-wps-new-tabular.php:735 Stack trace: #0 /home/.sites/972/site4696242/web/wp-content/plugins/wp-photo-seller/models/WPSCommon.php(136): include() #1 /home/.sites/972/site4696242/web/wp-content/plugins/wp-photo-seller/models/WPSShortcodeManager.php(92)
I don’t see this issue on the new version. I will send you an email to get access to the site so I can check it out.
The issue has been solved. Thanks for fixing this so fast.