Announcement

Collapse
No announcement yet.

9.00065 was there, now missing.

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

  • I do have a question - circling back to how I came up with my own theory - the site that had the error was a copy of a site that was MMUI but had the converter run on it. This particular site had a second dev site, that had the same content as the one that failed with the only difference being it was still MMUI - why did it not have the same error when the update was run? I did notice that it was an older version 9.000053 (maybe). It was old enough to trigger a non-compliance fee. It ran through the update without hesitation. I was expecting to have to submit support requests on both of them.
    Leslie Kirk (aka Leslie Nord leslienord)
    Miva Merchant Certified Developer
    Miva Merchant Specialist since 1998
    Previously of Webs Your Way

    Email me: [email protected]
    www.lesliekirk.com

    Follow me: Twitter Twitter Twitter Twitter | Facebook | FourSquare | Pinterest | Flickr

    Comment


    • If it had been sitting around a long time, then it probably never had new database tables created on a server that differed in character set from where it began life.
      David Hubbard
      CIO
      Miva
      [email protected]
      http://www.miva.com

      Comment

      Working...
      X