Paul Scollon
Forum Replies Created
-
Forum: Plugins
In reply to: [YITH WooCommerce Product Add-Ons] Version 4.16 critical error@vanesarodriguez @asaldel thank you guys for the speedy fix and for letting us know!
Forum: Plugins
In reply to: [YITH WooCommerce Product Add-Ons] Version 4.16 critical error@inilerm you can also comment out line 72 in init.php
Also experiencing issues with conditional fields. They are just ignoring the conditions and appearing anyway – which is a problem, as some of them are “required” fields. Thank you.
Any update on this fix? Or is it that all users of the plugin previously now need to enable the following fields in Basic Settings?
- Legacy Inputs Rendering
- Legacy Conditions Script
- Enable Legacy Price Calculations
Forum: Plugins
In reply to: [WooCommerce] After the 8.5.0 update, I encountered an error@seanaus120 I have 8.5 now running on PHP 8.2, after activating WooCommerce -> Settings -> Advanced -> Features -> Marketplace
The problem is not PHP 8.2
Forum: Plugins
In reply to: [WooCommerce] After the 8.5.0 update, I encountered an error@lukaszwozniak that would seem to be a different issue, more likely with woosubscriptions (last updated in December) after the woocommerce 8.5 update.
Forum: Plugins
In reply to: [WooCommerce] After the 8.5.0 update, I encountered an error@jorickvanweelie ah okay, I’m only seeing on storefront sites currently, other sites have gotten to 8.5 without issue (thankfully). Had to use wp-cli to disable the woocommerce plugin then use WP Rollback to revert to 8.4 on the storefront sites.
Forum: Plugins
In reply to: [WooCommerce] After the 8.5.0 update, I encountered an error@webinzicht I’m thinking it’s only sites with Storefront theme?
Forum: Plugins
In reply to: [WooCommerce] After the 8.5.0 update, I encountered an errorSame here. Site inaccessible.
Fantastic! Thank you.
Same here. Completely breaks site.
Forum: Plugins
In reply to: [Restore and Enable Classic Widgets No Expiration] Version 1.8 Fatal ErrorSame here, it’s definitely your plugin that caused it:
[STDERR] PHP Fatal error: Uncaught Error: Call to undefined function wp_get_current_user() in /var/www/html/wp-includes/capabilities.php:1073 Stack trace: #0 /var/www/html/wp-content/plugins/restore-classic-widgets/restore_classic_widgets.php(71): is_super_admin() #1 /var/www/html/wp-settings.php(447): include_once('...') #2 /var/www/html/wp-config.php(86): require_once('...') #3 /var/www/html/wp-load.php(50): require_once('...') #4 /var/www/html/wp-blog-header.php(13): require_once('...') #5 /var/www/html/index.php(17): require('...') #6 {main} thrown in /var/www/html/wp-includes/capabilities.php on line 1073
Forum: Plugins
In reply to: [Simple Social Icons] Google IconClient was using G+ icon incorrectly. Google Reviews is NOT a social platform.
Forum: Plugins
In reply to: [Simple Social Icons] Request: MastodonIt really is actually an easy and quick fix, I’ve done it on https://www.slated.ie (see footer) in less than 2 minutes. However, it really should be in this actual plugin by now, especially with so many jumping ship from Twitter.
Have a look at this tutorial: https://github.com/studiopress/simple-social-icons/wiki/Add-an-additional-icon-in-version-2.0
Or if you are not happy coding in anyway use this below version (includes the rel=”me” thing but will be overwritten by any plugin updates. Hopefully, updates will have same mastadon code!)
https://www.dropbox.com/s/t7wjm7ipthqyg8f/simple-social-icons.zip?dl=1
- This reply was modified 2 years, 4 months ago by Paul Scollon. Reason: Added link to hacked plugin file
Forum: Plugins
In reply to: [Booster for WooCommerce] Critical Error after updating to 5.6.4I too believe both plugins were required originally, @caban13. This must have changed somewhere along the line.