[request] Pre-beta 1.2.1 testing

in the last few weeks, the most important outstanding bugs for 1.2.1 have been fixed. Before we release 1.2.1 beta in the wild, I'd like to ask for an additional testing effort, this time specifically targeted at migrating from 1.1.2 or 1.1.3 (and eventually Xoops 2.0.x) to the latest 1.2.1 in the trunk.

Performing upgrade tests
Please make sure you check the following defects to see what should be present in the 1.1.2 or 1.1.3 installation before you perform the upgrade. Verify that everything works ok after the upgrade.

#877 - Upgrade of imagemanager and preloads deletes files ...
#866 - HTML Purifier doctypes not inserted during an upgrade
#927 - DB Upgrade errors from 1.1.2 to 1.2
#928 - Check for duplicate value in configcategory not correct

Be sure to report back what defects you verified. That will give us more confidence in releasing 1.2.1 beta after some test reports have been done.

On to 1.2.1 beta!

Test locally and on a remote host, if possible

I just successfully upgraded 2 remote sites! 1 from 1.2 and another from 1.1.3 (beta!)

upgrade done. from 1.1.3 to 1.2.1beta just i dont know im still seeing the warning message on admin home even if i've done this step
here is the message!
Congratulations, you have just successfully upgraded your site to the latest version of ImpressCMS!
Therefor to finish the upgrade process you'll need to click here and update your system module.
Click here to process the upgrade.

The upgrade from 1.1.3 to 1.2 is handled by the system module - just update the system module and you will see the rest of the update. The upgrade folder is for upgrading from ImpressCMS 1.0 or XOOPS.

i've done that but i still see the warning message! should i just make it invisible ?

You need to see where the upgrade is stopping - at the bottom of the list, you should see where the db version is updating - you need to get to version 39 before the message will go away.

Additional request: are there any issues/updates in the content or profile modules to be merged?

Open tickets for content and profile modules

Sorry - I found a bug in the system warning block, FaYsSaL, but it is easily fixed, and I already have. The check for the need to update the system module was not using the right comparison.

There were some updates to the profile module, yes. I just don't want to release it as a "next" version now (in other words: being forced again by the core).

Could you maybe release it as an 'updated' version ? It would be great to have the latest bug-fixes along with 1.2.1.

Where's the real difference between an updated version and a next version? I can't see any .

For those who want to have the latest version, they are welcome to get it from our repositories. Since there has been quite a lot of cleanups and refactoring without the needed amount of testing I don't even want to release it as alpha yet . I'm not even done with my task. Unfortunately I don't have the time to go on doing it right now. Maybe this gets better in the next week(s).