timboo
Forum Replies Created
-
@thephrase if i need to take a guess im thinking your woocommerce payments plugin is the one which causes the error with mollie. On my side im only running woocommerce + mollie and this only results in the Error: Call to a member function getProperty() on null
In my case define( ‘WP_DEBUG’, false ); is hiding the error, which is pretty interesting since wp_debug false should only hide warnings if im right.
regarding WP_DEBUG_DISPLAY, this one is by default true and should stay like this, WP_DEBUG is all you need to change. Like mentioned earlier if its an real error WP_DEBUG will not change anything for you.
@niklasinpsyde
It seems at this moment we have two type of errors/warnings
Error 1; Error: Call to a member function getProperty() on null
Error 2; Warning: assert(): assert($billie instanceof PaymentMethodI) f
Error 1 doesnt look to break something sofar, Error 2 looks like a combination with the Woocommerce payment plugin.- This reply was modified 3 years, 1 month ago by timboo.
Same error as, lets centralize over there:
https://ww.wp.xz.cn/support/topic/error-on-screen-after-update-billie-instanceof-paymentmethodi-failed/@thephrase define( ‘WP_DEBUG’, false ); should be sufficient on its own, did you allready tried to disable the other plugin in order to check if the combination of the plugins isnt creating the problem?
This is not exactly the same error but i at least wanted to mention it, im working in a dev environment where i just updated the plugin, over there im running debug true, after recent update its giving the following error (only visible when debug mode true) before the update this was not the case.
Error: Call to a member function getProperty() on null
Versions:
WordPress 6.2
Woocommerce 7.5.1
Mollie payments 7.3.6- This reply was modified 3 years, 1 month ago by timboo.