• Resolved jaydisc

    (@jaydisc)


    Looking through the support threads and reviews here, it’s pretty apparent that this major update of the plugin isn’t going well at all. How about rolling it back to the previous version, and restarting your QA procedures?

Viewing 15 replies - 1 through 15 (of 23 total)
  • Thread Starter jaydisc

    (@jaydisc)

    I have a backup, so I can do this myself. Are there any concerns with reverting? I’ll disconnect first.

    Plugin Support con

    (@conschneider)

    Engineer

    Hi there,

    Downgrading only works if you have a full backup that also reverts the database. When rolling back most people will also need to export / import store data to account for new orders etc.

    > Are there any concerns with reverting?

    Yes. Keep in mind that only a full rollback will work. The database structure was changed during the Square Update. Changing the plugin files only will brick the Square plugin and your site probably with it.

    Rolling back with a backup means you will loose all new data since the backup. Any customers, edits, orders will have to be exported / imported. However this new data has a different database structure, so you will need to migrate it manually. My recommendation would be to rollback and then add any new data manually. I would stay away from data imports.

    Last but not least test the rollback on staging (don’t work on your live site) and then deploy.

    Other then that we are working full throttle on fixing all the things ??.

    Kind regards,

    Thread Starter jaydisc

    (@jaydisc)

    Well, I can happily report that I:

    1. Disconnected 2.0.5, Deactivated/Deleted the Plugin.
    2. I restored v1.0.38
    3. I had to Connect to Square
    4. I performed a full WC → Square sync

    And everything went beautifully. I did not do a database restore.

    I noticed that v2 of the plugin created these strange single variations of every product. (screenshot link):

    If I didn’t have any sales against any such products, I deleted all such Frankenstein products from Square, and performed another WC → Square sync, and clean, simple products were restored.

    I don’t use Square for payment, so can’t comment there, but the procedure I performed above, worked without a hitch.

    • This reply was modified 5 years ago by jaydisc.
    lances

    (@lances)

    my live site is having 1.0.35 and staging 2.0.5. But after testing and reading comment here, I may not want to upgrade my live site to 2.0.5 due to several issues on testing:
    – not support multiple variation attributes
    – not sync from woo to square upon importing, cancelling orders etc

    However there is another issue with 1.0.35 that after adding new product on Woocommerce and it auto sync to square, the Product title disappeared. I’m thinking of updating to 1.0.38 in case it can fix. My question will be whether it is safe to update to 1.0.38? I know people got issue with reverting from 2.x to 1.0.38.

    Thanks.

    Thread Starter jaydisc

    (@jaydisc)

    I’ve used the following versions, from the following dates:

    1.0.29 (2018-05-07)
    1.0.30 (2018-06-01)
    1.0.31 (2018-06-06)
    1.0.33 (2018-09-27)
    1.0.34 (2018-11-08)
    1.0.35 (2019-02-04)
    1.0.37 (2019-04-19) <– Heavily battle tested – passed w/flying colours
    1.0.38 (2019-07-07)
    2.0.4 (2019-09-25) <– When it all went downhill
    2.0.5 (2019-10-21) <– Not much better

    I never had issues with 1.x, including disappearing product titles. Are you using any hooks or other plugins that modify the product title?

    lances

    (@lances)

    I got issue recently only with product title and only after syncing to Square it losts the title for new products. Old products are ok. Very strange.

    1.0.37 :do you mean it has lots of issues that need to test carefully?

    Thread Starter jaydisc

    (@jaydisc)

    No, with 1.0.37, I did A LOT of testing, and it worked very well.

    lances

    (@lances)

    thanks

    Plugin Support Ryan Ray, a11n

    (@ryanr14)

    Hi @jaydisc,

    And everything went beautifully. I did not do a database restore.

    Glad your downgrade went smoothly and things are working as you’d like. I think somewhere in there you’ve got lucky, so knock on wood! ??

    Plugin Support Ryan Ray, a11n

    (@ryanr14)

    Howdy @lances,

    I may not want to upgrade my live site to 2.0.5 due to several issues on testing:
    – not support multiple variation attributes
    – not sync from woo to square upon importing, cancelling orders etc

    To clarify Square itself hasn’t supported multiple attributes since its inception. There are workarounds for that described here. –> https://docs.woocommerce.com/document/woocommerce-square/#faq-attributes

    When you say issues from syncing from Woo -> Square upon importing, do you mean upon the first sync? If so what is your system of record and what issues do you notice in that sync?

    Beyond that could you explain more for what you’re seeing when you mention cancelling orders?

    Thanks!

    mattsingley

    (@mattsingley)

    I was experiencing the same WC -> Square inventory sync issues with 2.0.5 with multiple variations per product. Per this thread, I uninstalled 2.0.5 and installed 1.0.38 and it was very smooth. No bricking, no sync issues…everything now pushes from WC to Square without issue (or at least none that are currently known).

    Hopefully this is on the dev radar as a critical issue…I think most modern stores are likely to sell products with multiple variations. Combining the variations, as I have seen suggested elsewhere, just isn’t a viable option, nor is it scalable.

    So glad 1.0.38 is working well, looking forward to a 2.x.x update that syncs and is stable.

    Plugin Support con

    (@conschneider)

    Engineer

    Hi again,

    Hopefully this is on the dev radar as a critical issue…I think most modern stores are likely to sell products with multiple variations. Combining the variations, as I have seen suggested elsewhere, just isn’t a viable option, nor is it scalable.

    You bet. We are doing as fast as we can.

    So glad 1.0.38 is working well, looking forward to a 2.x.x update that syncs and is stable.

    Cheers.

    rprice54

    (@rprice54)

    I’d be all for a rollback. They broke the plugin with version 2

    Plugin Support Ryan Ray, a11n

    (@ryanr14)

    Howdy @rprice54,

    There were bugs in the 2.0+ rollout, we have no problem admitting that. I was just curios though if you had experienced anything specific? If so we’re here to try and help figure out what might be going on in your situation/site.

    rprice54

    (@rprice54)

    I’m having several of the issues that are being discussed on this forum.

    Items are no longer syncing from Woo>Square consistently. It’s hit or miss.

    I constantly get the ‘there may be a problem with your square connection. Please disconnect and reconnect…’

    If I make any changes to a product the quantity gets reset to zero.

    Often the quantity gets stuck at zero and I can’t update the quantity without disabling square sync first. Save. Update. Then re-enabling sync.

    It’s so bad I’ve just disabled the plugin completely. I’m having to enter all my stuff into square manually now. Hopefully v3 is better.

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘How about restoring the old version while you sort this out?’ is closed to new replies.