• Resolved inventis

    (@inventis)


    After the plugin updated it disabled itself.

    We re-activated it a few days later when we realised, and tallied all the stock.

    Since then any sales on the website goes through to Zettle, however sales in Zettle do not adjust the stock levels on the website. I have had to go and manually edit the stock levels on the wordpress of 200+ products tonight

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @inventis

    Thanks for reaching out to us, we’re here to help.

    Please first check if the issue still occurs after reinstalling the previous version 1.5.7. You can find it here: https://github.com/inpsyde/PayPal-Zettle-POS/releases/tag/1.5.7

    If the issue persists, it may be related to stock synchronization, which occasionally causes problems for two main reasons.

    1. Plugin conflict
    2. Security measures block the stock sync communication.

    The first thing I would do is to make sure you can reproduce the issue by manually adjusting the stock in the Zettle web interface and checking that it gets updated on WooCommerce. You need to confirm this in order to verify these options are causing the issue:

    2 possible activities to fix the sync issue are:

    1. Deactivate all other plugins (except WooCommerce and Zettle) and see if you can make a stock sync from Zettle –> WooCommerce.
    2. Any installed security plugin would already be excluded by the previous test, so the only security/firewall that needs to be investigated is the one managed by your hosting partner. For this, you need to reach out to them and ask them if they are possibly blocking the JSON webhooks that are required for the stock updates. We are hearing that the hosting partner firewalls are sometimes blocking these requests since they are interpreted as DDOS attacks and block the phpflood that is being seen.

    Please let me know what your findings are.

    Kind regards,
    Krystian

    Thread Starter inventis

    (@inventis)

    Your github link doesn’t work – but I used WP Rollback and straightaway it works with the old version?

    • This reply was modified 5 months ago by inventis.
    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @inventis

    I’m sorry for providing the wrong link.

    Could you please confirm if the downgrade resolved the issue? The “?” at the end leaves me with some doubts.

    Looking forward to hearing from you.

    Kind regards,
    Krystian

    Thread Starter inventis

    (@inventis)

    Hi – yes it works with the old version!

    Why is this the case? Why doesn’t it work with the latest version

    Plugin Support Syde Joost

    (@joostvandevijver)

    Hello @inventis

    This is not something we can confirm, but I would expect this is caused by a change that we made with our last release “Executing shutdown hooks early to improve compatibility”. You have been, so far, the only merchant reporting this issue, so I would expect that another plugin, theme or custom code is using something similar that is interfering with the hooks and causes the problem.

    We can only advise you to perform a full conflict test to isolate what plugin is causing this issue. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for?WooCommerce and?PayPal Payments to see if the behavior persists.

    Here’s a guide that explains the steps in more detail: How to test for conflicts
    Please let us know how this works out for you.

    Kind regards,
    Joost

    Hello,

    We have the same problems.

    I will try to make a rollback, to see if the problems still exists.

    It worked after rolling back to 1.5.7.

    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @inventis & @sebastianjust

    To help us diagnose the issue more effectively, we need access to your system report to analyze the list of plugins you’re using. We suspect the problem might be due to a conflict, as we are unable to reproduce the issue on our end.

    We have another similar case on our private board where we’ve requested access to a staging site to further investigate. Please follow these steps to share your system status report with us:

    1. Navigate to the WooCommerce / Status section in your site’s admin panel.
    2. Click on the Get system report button and then click Copy for support.
    3. Paste the report into our PrivateBin.
    4. After uploading, please share the link here so we can review the details thoroughly.

    We are waiting for your system reports to proceed with the analysis.

    Kind regards,
    Krystian



    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello?@inventis?

    Since we have not received any further communication from you, we are assuming that your issue has been resolved.

    Therefore, we mark this thread as resolved. If you still have any questions or if a new problem arises, don’t hesitate to open a new thread.

    Kind regards,
    Krystian

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.