Title: dynit's Replies | WordPress.org --- # dynit [ ](https://wordpress.org/support/users/dynit/) * [Profile](https://wordpress.org/support/users/dynit/) * [Topics Started](https://wordpress.org/support/users/dynit/topics/) * [Replies Created](https://wordpress.org/support/users/dynit/replies/) * [Reviews Written](https://wordpress.org/support/users/dynit/reviews/) * [Topics Replied To](https://wordpress.org/support/users/dynit/replied-to/) * [Engagements](https://wordpress.org/support/users/dynit/engagements/) * [Favorites](https://wordpress.org/support/users/dynit/favorites/) Search replies: ## Forum Replies Created Viewing 10 replies - 1 through 10 (of 10 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce PayPal Payments] Payment options enabled without consent!](https://wordpress.org/support/topic/payment-options-enabled-without-consent/) * [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [2 months, 2 weeks ago](https://wordpress.org/support/topic/payment-options-enabled-without-consent/#post-18870392) * Same problem here: all these new payment options were automatically added a couple of days ago. Had this on multiple websites. Worse even: I cannot delete them from the woocommerce payment options screen. I can press ‘delete’, but they come back automatically again. Even on 4.0.2. Big impact, please provide fix. In the meantime I can only disable PayPal altogether. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Pronamic Pay] Error in version 9.17.0](https://wordpress.org/support/topic/error-in-version-9-17-0/) * Thread Starter [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [9 months, 4 weeks ago](https://wordpress.org/support/topic/error-in-version-9-17-0/#post-18610980) * Reverted back to 9.16.0 and everything is fine again. Looks like it’s a compatibility problem with (any) Checkout Field Editor plugin where phonenumbers are filtered out – not requested from customers. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Brevo for WooCommerce] WooCommerce HPOS compatibility?](https://wordpress.org/support/topic/woocommerce-hpos-compatibility-14/) * [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [3 years ago](https://wordpress.org/support/topic/woocommerce-hpos-compatibility-14/#post-16817837) * We would like to know this too. The new Woocommerce performance option ([https://woocommerce.com/document/high-performance-order-storage/](https://woocommerce.com/document/high-performance-order-storage/)) works with different database tables and will be the new default when installing new stores. If it is not updated, the plugin (still branded as sendinblue by the way) will not work on new stores. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Redis Object Cache] Serialization of ‘SimpleXMLElement’ is not allowed](https://wordpress.org/support/topic/serialization-of-simplexmlelement-is-not-allowed/) * [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [3 years ago](https://wordpress.org/support/topic/serialization-of-simplexmlelement-is-not-allowed/#post-16763585) * Update: the problem has suddenly disappeared! Didn’t really do anything, perhaps an auto-update of a plugin has fixed it, or my host changed something. * Of course it would still be great if the drop-in plugin could prevent this problem from happening again. Not sure if that is possible though. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Redis Object Cache] Serialization of ‘SimpleXMLElement’ is not allowed](https://wordpress.org/support/topic/serialization-of-simplexmlelement-is-not-allowed/) * [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [3 years ago](https://wordpress.org/support/topic/serialization-of-simplexmlelement-is-not-allowed/#post-16763335) * I have the exact same problem since a couple of days, also only when opening the (plugin) update page: * **Error establishing a Redis connection** * `Serialization of 'SimpleXMLElement' is not allowed` * The error occurs on both the /update-core.php and the /wp-admin/plugins.php page. Redis seems to still work, but these pages cannot be accessed anymore. * If indeed the cause is another plugin as Till mentioned, then the solution may be to disable all the plugins one by one to find the culprit (if anyone found it, please let us know). I didn’t have the opportunity yet to try this myself. Preferably this is of course handled/prevented in the Redis drop-in plugin itself. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Recencio Book Reviews] How to disable rating](https://wordpress.org/support/topic/how-to-disable-rating/) * Thread Starter [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [5 years, 12 months ago](https://wordpress.org/support/topic/how-to-disable-rating/#post-13013351) * Thanks! That did it 🙂 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] CRITICAL Uncaught Error: Call to undefined function wcs_order_contains_renewal()](https://wordpress.org/support/topic/critical-uncaught-error-call-to-undefined-function-wcs_order_contains_renewal/) * Thread Starter [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [8 years, 1 month ago](https://wordpress.org/support/topic/critical-uncaught-error-call-to-undefined-function-wcs_order_contains_renewal/#post-10219969) * Thanks for the quick response! I will implement this. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] CRITICAL Uncaught Error: Call to undefined function wcs_order_contains_renewal()](https://wordpress.org/support/topic/critical-uncaught-error-call-to-undefined-function-wcs_order_contains_renewal/) * Thread Starter [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [8 years, 1 month ago](https://wordpress.org/support/topic/critical-uncaught-error-call-to-undefined-function-wcs_order_contains_renewal/#post-10219911) * That is correct, I do not have WooCommerce Subscriptions installed. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] 2.6.0 returning cancelled payments to wrong page](https://wordpress.org/support/topic/2-6-0-returning-cancelled-payments-to-wrong-page/) * Thread Starter [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [8 years, 11 months ago](https://wordpress.org/support/topic/2-6-0-returning-cancelled-payments-to-wrong-page/#post-9261541) * My issue is solved! The problem was a webhook that wasn’t called because of an ssl setting on my testsite. Thanks for the support 😉 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Mollie Payments for WooCommerce] Woocommerce 3.0 compatible](https://wordpress.org/support/topic/woocommerce-3-0-compatible-2/) * [dynit](https://wordpress.org/support/users/dynit/) * (@dynit) * [9 years, 1 month ago](https://wordpress.org/support/topic/woocommerce-3-0-compatible-2/#post-9069750) * It works, but it does generate a lot of errors in the apache log: * > payment_method was called incorrectly. Order properties should not be accessed > directly. - This reply was modified 9 years, 1 month ago by [dynit](https://wordpress.org/support/users/dynit/). - This reply was modified 9 years, 1 month ago by [dynit](https://wordpress.org/support/users/dynit/). Viewing 10 replies - 1 through 10 (of 10 total)