• Resolved wfcrafts

    (@wfcrafts)


    Thanks for your update, crashed my 23 client’s ecommerce sites – fecked my friday nite cheers

Viewing 15 replies - 1 through 15 (of 17 total)
  • Plugin Author Austin

    (@austyfrosty)

    Can you provide the different WordPress version(s), PHP Versions, and or error logs?

    @austyfrosty The update crashes any website that uses woocommerce with the following error

    NOTICE: PHP message: PHP Fatal error: Declaration of Automattic\WooCommerce\Container::has($id) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool in /var/www/htdocs/wp-content/plugins/woocommerce/src/Container.php on line 106

    Like @wfcrafts, I just lost 40 websites and am spending my Friday night removing this plugin manually on each server.

    Thread Starter wfcrafts

    (@wfcrafts)

    Quote: Can you provide the different WordPress version(s), PHP Versions, and or error logs?

    Probably, when my feckin phone stops ringing with angry people

    Plugin Author Austin

    (@austyfrosty)

    This is a known error with WooCommerce. I have dealt with this error in other packages and will look into applying the same fix here.

    See:

    Thread Starter wfcrafts

    (@wfcrafts)

    Oh, and by the way, you have even managed to mess with 11 site’s themes too, happy days

    Thread Starter wfcrafts

    (@wfcrafts)

    Quote: This is a known error with WooCommerce. I have dealt with this error in other packages and will look into applying the same fix here.

    Didn’t you think of that before the release

    My lady is not happy

    In fact, lets change the plugin, all I wanted was a client logo when they logged in

    No a night with no nookie

    Feck

    Thread Starter wfcrafts

    (@wfcrafts)

    Seems you caused a lot of damage to several of my client’s sites

    I deleted your plugin via ftp after the upgrade

    Could you please provide your db interactions during upgrade?

    My Saturdays sorting unnecessary shite ain’t good for my karma

    Thank you for your efforts and quick reply on this @austyfrosty. Unlike @wfcrafts, I understand that this is a free plugin and that you don’t owe anything to the end user. Meanwhile, I have rolled back the plugin version on all site and disabled automatic updates for now.

    Plugin Author Austin

    (@austyfrosty)

    Thanks Paul.

    I am looking into a solution to resolve this issue. Also on a Friday night.

    Good stuff, thanks again. Hope it’s a quick fix!

    Thread Starter wfcrafts

    (@wfcrafts)

    Paul Scollon, you are correct it is a free plugin and I should not react the way I did. It is a free plugin and we are most welcome for their efforts to this community in giving users free functionality users require for their user experiences.
    Apologies, I just got back from a great night out when the phone started ringing. To log on and find my server in tears.
    I should have disabled auto upgrade on all sites, I have now.
    To the plugin creators and maintainers I apologise.
    Btw, she’s still talking to me

    Plugin Author Austin

    (@austyfrosty)

    Version 4.0.4 (released last night) resolves the PSR Container compatibility issues with WooCommerce.

    Not sure what’s happening here but I have V4.0.5 and am having issues as per above with the WooCommerce sites. WordPress is rw3porting a fatal error with the following:

    WordPress version 6.0.1
    Active theme: Roseta Plus Child (version 0.5)
    Current plugin: WooCommerce (version 6.7.0)
    PHP version 7.4.30
    
    Error Details
    =============
    An error of type E_COMPILE_ERROR was caused in line 106 of the file /home/narrabun/public_html/wp-content/plugins/woocommerce/src/Container.php. Error message: Declaration of Automattic\WooCommerce\Container::has($id) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool
    Plugin Author Austin

    (@austyfrosty)

    Thanks @gaffercanberra, I’ll take a look. Maybe a regression in 4.0.5 took place.

    Plugin Author Austin

    (@austyfrosty)

    I am hopeful Custom Login 4.0.6 resolves all Container issues.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Thanks for the upgrade and fatal crash’ is closed to new replies.