Title: devbd's Replies | WordPress.org --- # devbd [ ](https://wordpress.org/support/users/devbd/) * [Profile](https://wordpress.org/support/users/devbd/) * [Topics Started](https://wordpress.org/support/users/devbd/topics/) * [Replies Created](https://wordpress.org/support/users/devbd/replies/) * [Reviews Written](https://wordpress.org/support/users/devbd/reviews/) * [Topics Replied To](https://wordpress.org/support/users/devbd/replied-to/) * [Engagements](https://wordpress.org/support/users/devbd/engagements/) * [Favorites](https://wordpress.org/support/users/devbd/favorites/) Search replies: ## Forum Replies Created Viewing 5 replies - 1 through 5 (of 5 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Max Mega Menu] Issue when re-opening the menu](https://wordpress.org/support/topic/issue-when-re-opening-the-menu/) * Thread Starter [devbd](https://wordpress.org/support/users/devbd/) * (@devbd) * [1 year, 5 months ago](https://wordpress.org/support/topic/issue-when-re-opening-the-menu/#post-18206147) * Hi Tom, Thank you 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Variation Swatches for WooCommerce] PHP Warning: Illegal string offset “160-x-230”](https://wordpress.org/support/topic/php-warning-illegal-string-offset-160-x-230/) * Thread Starter [devbd](https://wordpress.org/support/users/devbd/) * (@devbd) * [1 year, 11 months ago](https://wordpress.org/support/topic/php-warning-illegal-string-offset-160-x-230/#post-17846308) * Thank you for your response. The warning is triggered by your plugin, please, see: * PHP Warning:  Illegal string offset “120-x-180” in […]/plugins/variation-swatches- woo/admin/templates.php on line 365, referer: […]/wp-admin/post.php?action=edit& post=[…] * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Product Input Fields for WooCommerce] PHP Warning: strpos(): Empty needle](https://wordpress.org/support/topic/php-warning-strpos-empty-needle-3/) * Thread Starter [devbd](https://wordpress.org/support/users/devbd/) * (@devbd) * [2 years, 9 months ago](https://wordpress.org/support/topic/php-warning-strpos-empty-needle-3/#post-16988663) * Hi, PHP version we use is 7.4.33. WooCommerce version is 7.9.0. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[ShopMagic - email automation] Warning associated with PHPMailer.php class](https://wordpress.org/support/topic/warning-associated-with-phpmailer-php-class/) * Thread Starter [devbd](https://wordpress.org/support/users/devbd/) * (@devbd) * [3 years, 11 months ago](https://wordpress.org/support/topic/warning-associated-with-phpmailer-php-class/#post-15759414) * Hi Bartek, * Thank you for your advice. We’re currently on 2.37.10 version of the plugin but we’completed updates recently, so maybe the issue will be resolved. I posted the support ticket with a short delay, so I’m not 100% sure if the site was on. 09 or .10 when error happened. In this case, we’ll monitor the site and re-open the ticket if needed. * Thank you, * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Shipping Live Rates and Access Points for UPS for WooCommerce] PHP Fatal error: Uncaught Error: Call to undefined function wc_empty_cart()](https://wordpress.org/support/topic/php-fatal-error-uncaught-error-call-to-undefined-function-wc_empty_cart/) * Thread Starter [devbd](https://wordpress.org/support/users/devbd/) * (@devbd) * [4 years, 2 months ago](https://wordpress.org/support/topic/php-fatal-error-uncaught-error-call-to-undefined-function-wc_empty_cart/#post-15478437) * Hi Grzegorz, * Thank you for your advice. The problem is that we are unaware of what action triggers the error (we couldn’t recreate the error ourselves). Therefore, we can’t prepare any reliable test to see if deactivating a particular plugin solves the issue. We only see in our logs that error is getting logged from time to time. * For this reason, we can’t deactivate other plugins, as we would need to keep them deactivated for a quite a long time which in most cases would have an impact on the functionality of the website. * The only plugin we could deactivate at this stage is the one responsible for caching. I’ll deactivate this one, wait a few days and update you if it was responsible. * Regards, Karolina Viewing 5 replies - 1 through 5 (of 5 total)