Announcement

Collapse
No announcement yet.

Just a friendly heads up for my fellow shiny penny people

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Rick Wilson
    replied
    The patch plus 10.03.01 us back up and the issue is resolved. If you restored to backup in the meantime you can safely reinstall both patches. If you were one of the 7 sites waiting for us to fix the lost reference data please work through your support ticket.

    Leave a comment:


  • Rick Wilson
    replied
    We're on it, we'll definitely fix the image issue (it appears the image issue is separate from your failed update). Also we will look into forcing Maintenance Mode for future upgrades.

    Leave a comment:


  • Mark Hood
    replied
    They appear to have gotten the update to process however we are currently missing almost all of our subcategory tree images and I sure hope this can be fixed too.

    Leave a comment:


  • Jim McCormick
    replied
    Originally posted by lesliekirk View Post

    Perhaps I should rephrase, I've seen a noticeable "drag" when trying to get back into an admin I logged out of just so I could get the update button to appear when I logged back in. It's nothing major, just annoying. Would be kind of cool to not have to logout/login to get the button
    You can use the global search in the admin to pull up the upgrade wizard instead of logging out and then back in:

    upgrade.jpg

    Leave a comment:


  • Mark Hood
    replied
    If maintenance mode is required you may want to have someone update this https://www.miva.com/upgrade-miva-merchant

    Leave a comment:


  • Mark Hood
    replied
    Just so we're on the same page I'm still waiting for a restore to finish? I have a whole lot of sub category images still missing.

    Leave a comment:


  • ILoveHostasaurus
    replied
    Ah, yes I don't think there's a way to make it check for updates except at login, and even then it may not check every time but I'd need to confirm that. The intent behind that is to not slow or interrupt admin access if there's maintenance occurring on the update server at the time. We also, at times, publish releases in a manner where they may not show as available to 100% of installed copies right away, to allow us to slow the deployment for support reasons, particularly if there are UI changes for example.

    Leave a comment:


  • lesliekirk
    replied
    Originally posted by ILoveHostasaurus View Post

    The update speed has no relation to how many people are upgrading; each copy of Merchant performs its own update routine independently. There are database schema changes where a one store may require an entirely different amount of time to upgrade than another dependent on a number of different record counts in various areas of the store; prods, inventory, cats, etc.
    Perhaps I should rephrase, I've seen a noticeable "drag" when trying to get back into an admin I logged out of just so I could get the update button to appear when I logged back in. It's nothing major, just annoying. Would be kind of cool to not have to logout/login to get the button

    Leave a comment:


  • ILoveHostasaurus
    replied
    Originally posted by Mark Hood View Post
    They're clearly working on it but after receiving a server timeout issue the site has been completely down. Still currently fluctuating between working and not.
    Mark, was the upgrade performed without maintenance mode? At this point our suspicion is shopper traffic, combined with characteristics of your site, created a scenario that caused the upgrade timeout, which in turn left parts of it incomplete. With the store in maintenance mode, the upgrade was able to complete.

    Leave a comment:


  • ILoveHostasaurus
    replied
    Originally posted by lesliekirk View Post

    And this is why I warn to wait until "we" get a chance to break it. I was able to update a dev site but it was slow. I could tell a lot of people had "pressed that button".
    The update speed has no relation to how many people are upgrading; each copy of Merchant performs its own update routine independently. There are database schema changes where a one store may require an entirely different amount of time to upgrade than another dependent on a number of different record counts in various areas of the store; prods, inventory, cats, etc.

    Leave a comment:


  • lesliekirk
    replied
    Originally posted by Mark Hood View Post
    They're clearly working on it but after receiving a server timeout issue the site has been completely down. Still currently fluctuating between working and not.
    And this is why I warn to wait until "we" get a chance to break it. I was able to update a dev site but it was slow. I could tell a lot of people had "pressed that button".

    Leave a comment:


  • Mark Hood
    replied
    They're clearly working on it but after receiving a server timeout issue the site has been completely down. Still currently fluctuating between working and not.

    Leave a comment:


  • Rick Wilson
    replied
    What’s the issue?

    Leave a comment:


  • Just a friendly heads up for my fellow shiny penny people

    I really like being an early adopter and updating as soon as I can however that means breaking the site after a timeout error...
Working...
X