Thanks for checking that out! I’ll take a look myself and try to reduce resource usage next update.
Hi there. So I ran the P3 profiler on this plugin (as of version 2.0) and it consumes only 0.04 seconds of time at any given point. The load time was only caused on the wp-admin pages, not on the front end.
Besides this, the plugin definitely never consumed 2 times the resources of WooCommerce. I tested before and after the 2.0 update, and it consumed a fraction of the resources WooCommerce does, and only in wp-admin. Load times have been decreased even more.
First thank you for verification and response. You install this plugin and will be back again with the results.
I tried to reinstall the plugin and error here is what I got:
“Module Could not be activated Because it triggered a fatal error.
Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/……/public_html/wp-content/plugins/woocommerce-product-faqs/public/class-woocommerce-product-faqs.php on line 894 ”
Sorry about that. It will be fixed in a hot fix update in the morning.
Update released, thanks for the notification!
Again activation error:
Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/xxxxxx/public_html/wp-content/plugins/woocommerce-product-faqs/admin/class-woocommerce-product-faqs-admin.php on line 71.
I’ve pushed another update – 2.0.2.
I believe the discrepancy between it working for me and failing for you is a difference in server setup – probably that I am running PHP 5.5 and you are running a lower version. Hopefully 2.0.2 will resolve this compatibility issue.
Thanks for your patience!
Maybe that is why I have this error. My server works with PHP version 5.2.17, but my question is: what went though in the beginning? In this case you must specify the use of the conditional plugin using php 5.5.
The plugin doesn’t require PHP 5.5. That is just the version I use on my server and local development environments. I tested it down to PHP 5.3 after the issues were reported. I will not be testing PHP 5.2, as it has been unsupported since 2011.
As you can see in this thread, performance issues were gone through and determined to be inaccurate. Would you consider increasing your review score now that your issues have been addressed?
I would greatly appreciate it, if you think the plugin deserves a higher score.
- The topic ‘Consume too many resources’ is closed to new replies.