Hi @koyurei,
Sorry that you ran into issues with this!
When we’ve seen this in the past, a couple of possibilities usually come up:
– You have an aggressive cache system that is showing old data after your upgrade (less likely). The way to fix is the flush the cache completely after upgrade (server-side)
– You have more than 1 instance of BD pointing to the same database (more likely). We’ve seen this with some hosts where you have a dev site and a prod site, and you upgrade the prod, but the dev site pushes the database back to the “old version” and the prod version suddenly looks like it’s reverted. In order to fix this, you have to find the dev site and make sure it’s upgraded at the same time.
– A more less likely option is that you have some database cron job and it’s reverting your database back to an older version because of something that is happening. This isn’t always the case, but we have seen it a time or two, so I wouldn’t rule it out
Those are the likely causes of this–but it’s something you’ll have to investigate on your site. Not knowing how it’s setup, I can’t say which one you’ll find.
Please try that and let me know if you run into more issues.
