As some will know, I've been having major problems with tinymce pop-ups not working. After checking, double checking and triple checking permissions, re-instating files one at a time and running an upgrade the problem still shows.
I ran an upgrade from 4.0.2.1 to 4.0.3 yesterday and although it seemed to take me through the installation process rather than the upgrade process it appeared to work okay. My client has contacted me this morning however to report that many of the images in the CMS now appear different to how they are in the published site. The live site is correct, but the CMS is showing completely different images. I can only assume the database has somehow been re-indexed during the upgrade process.
As far as I know there's no reindexing during upgrade. How did you upgrade?
Did you start with copying the database using SQL manager? I'm asking since one of my clients had massive problems with their installation after copying. Apparently they somehow made a replica copy - this causes SQL server to create a copy without seeding ID's.
To upgrade I just followed the upgrade
instructions in the documentation for v 4.0.3. I did use the asp.net
3.5 config file (needed to run the repeater package I've got installed)
so maybe that's got something to do with it? I don't know how it could
have gone so wrong though to be honest.
How did your client resolve it? The data is correct on the website, so it must be there somewhere.
I'm
in the process of restoring from back-ups now anyhow, so hopefully this goes okay
and doesn't create yet further problems. Then I still need to try to tackle the
original bug again.
Major problems upgrading
Hi,
As some will know, I've been having major problems with tinymce pop-ups not working. After checking, double checking and triple checking permissions, re-instating files one at a time and running an upgrade the problem still shows.
I ran an upgrade from 4.0.2.1 to 4.0.3 yesterday and although it seemed to take me through the installation process rather than the upgrade process it appeared to work okay. My client has contacted me this morning however to report that many of the images in the CMS now appear different to how they are in the published site. The live site is correct, but the CMS is showing completely different images. I can only assume the database has somehow been re-indexed during the upgrade process.
Does anyone know if there's a fix to this?
Thanks all
Hi Dan,
As far as I know there's no reindexing during upgrade. How did you upgrade?
Did you start with copying the database using SQL manager? I'm asking since one of my clients had massive problems with their installation after copying. Apparently they somehow made a replica copy - this causes SQL server to create a copy without seeding ID's.
/Jesper
Thanks Jesper,
To upgrade I just followed the upgrade instructions in the documentation for v 4.0.3. I did use the asp.net 3.5 config file (needed to run the repeater package I've got installed) so maybe that's got something to do with it? I don't know how it could have gone so wrong though to be honest.
How did your client resolve it? The data is correct on the website, so it must be there somewhere.
I'm in the process of restoring from back-ups now anyhow, so hopefully this goes okay and doesn't create yet further problems. Then I still need to try to tackle the original bug again.
I've rolled back to a back-up and the same problem persists. It doesn't seem to be a database thing - it's related to the bug with media items being randomly swapped upon saving.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.