• Resolved kombimedia

    (@kombimedia)


    Hi there, since the recent 2.1.1 update I see a critical error in a multisite setup. I use Breeze on other single sites where I do not see this issue.

    Having the plugin activated is fine but as soon as I enable Cache System in the plugin settings all sites break.

    Any ideas?

    Cheers, Cy

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author adeelkhan

    (@adeelkhan)

    Please share the error.

    Thread Starter kombimedia

    (@kombimedia)

    Hi @adeelkhan,

    On the front end there is just the ‘There has been a critical error on your website’ message.

    Looking at the debug.log file I can see that when Caching is enabled a fatal error is thrown by the Central Stock for WooCommerce plugin.

    [20-Dec-2023 20:57:26 UTC] PHP Fatal error:? Declaration of Inpsyde\OneStock\Cache\NetworkProductCache::get($key, $default = null) must be compatible with Psr\SimpleCache\CacheInterface::get(string $key, mixed $default = null): mixed in /home/teq/webapps/teqfit/wp-content/plugins/onestock-for-woocommerce/src/Cache/NetworkProductCache.php on line 40

    This error wasn’t present before the 2.1.1 update.

    Thanks for your help,

    Cy

    Plugin Author adeelkhan

    (@adeelkhan)

    This issue is unrelated to the Breeze plugin. Please reconfigure the key of the OneStock plugin as indicated in the error message.

    Additionally, have you installed a different cache plugin along with Breeze?

    • This reply was modified 1 year, 3 months ago by adeelkhan.
    Thread Starter kombimedia

    (@kombimedia)

    Hi @adeelkhan,

    OneStock plugin has no settings available so I’m unable to reconfigure the key unfortunately, and this error does not appear when Breeze cache is disabled.

    There are no other caching plugins installed.

    Cheers

    Plugin Author adeelkhan

    (@adeelkhan)

    The error suggests a configuration issue, pointing to a potential problem with cache configuration. Specifically, there seems to be an issue at the following path: /home/teq/webapps/teqfit/wp-content/plugins/onestock-for-woocommerce/src/Cache/NetworkProductCache.php on line 40.

    ?it would be great if you contact our support and?create ticket?. We will investigate the point of conflict and also share to our users.

    Thread Starter kombimedia

    (@kombimedia)

    Thanks @adeelkhan,

    I will submit a support ticket.

    Thread Starter kombimedia

    (@kombimedia)

    Hi @adeelkhan,

    Re ‘create a support ticket’, I am not a Cloudways customer. Is this required in order to submit a support ticket for the Breeze plugin?

    Cheers

    Plugin Author adeelkhan

    (@adeelkhan)

    To better understand the issue you’re facing, could you please share the specific line of code mentioned in the file /home/teq/webapps/teqfit/wp-content/plugins/onestock-for-woocommerce/src/Cache/NetworkProductCache.php

    Your cooperation in providing this information will greatly assist in pinpointing the root cause and facilitating a more accurate resolution to the matter.

    Thread Starter kombimedia

    (@kombimedia)

    Hi @adeelkhan,

    public function get($key, $default = null)
    {
        if (!is_string($key)) {
            throw new InvalidCacheArgumentException('key argument must be a string.');
        }
    
        $data = wp_cache_get($key, self::GROUP);
        return ($data) ? $data : $default;
    }

    This function starts on line 40.

    Hope this helps.

    Cheers,

    Cy

    Plugin Author adeelkhan

    (@adeelkhan)

    Thank you for reaching out to us regarding the issue you’ve been experiencing with our plugin. We want to assure you that we are fully aware of the conflict that arises when our plugin is used alongside another specific plugin, due to differing versions of a shared library.

    Our development team is actively working on a solution to this problem. We understand the importance of ensuring compatibility and are committed to resolving this as efficiently as possible. Our approach involves isolating our version of the library to prevent any interference with other plugins you may be using.

    While we are working diligently on this, we do not have an immediate fix at this moment. We appreciate your patience and understanding as we navigate through this technical challenge. Our goal is to ensure that our plugin operates seamlessly within your environment, and we are making every effort to achieve this.

    We will keep you updated on our progress and will notify you as soon as a solution has been implemented. If you have any further questions or concerns in the meantime, please do not hesitate to contact us.
    Thank you for your continued support.

    Plugin Author adeelkhan

    (@adeelkhan)

    The issue has been resolved in version 2.1.4. Kindly update the plugin.

    Thread Starter kombimedia

    (@kombimedia)

    Great, thanks @adeelkahn

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Critical Error Since 2.1.1’ is closed to new replies.