Corrupted upgrade files OF SMF 2.0 RC1

[Akyhne]

I tried to download the small (Beta4 to RC1) upgrade.

The .zip and the .bz files are repported corrupted when trying to upload them. The .bz2 is said to not being the right filetype.

I can open the files on my computer. I even tried to download the files with different browsers.

Isn't it possible to upgrade SMF 2.0 Beta 4 through the admin panel?

[Oldiesmann]

You can't upgrade to RC1 through the admin center. You need to extract all the files to your computer, upload them to your SMF directory and run upgrade.php. There are way too many changes between Beta 4 and RC1 to support upgrading through the admin center.

[Akyhne]

Ok, thx.

[Tiribulus]

It took me a minute to figure this out too.

[karlbenson]

It will only be possible to do it via package manager AFTER smf 2.0 goes final.

[Akyhne]

So I have been spending all day upgrading several forums I have. I had troubles with half of them (SMF 1.1.7 and 2.0 beta4).

But now I'm upgrading an almost new SMF2.0 Beta 4 forum. I uninstalled the few mods I had with no error, then uploaded the small upgrade package. But now I get this error when trying to upgrade:

Updating Your SMF Install!
The upgrader found some old or outdated files.

Please make certain you uploaded the new versions of all the files included in the package.

Click here to try again.

If it could at least tell me what files were outdated. I have no idea where to start. Should I use the big upgrade package?

[metallica48423]

Should I use the big upgrade package?

Yes.

Make sure all of your language files were updated to RC1 versions as well.

[Akyhne]

But the text in the download center says:

"Using modifications, or not using SMF 2.0 Beta 4.x? No problem, this is what you need."
That's not my situation


"Using SMF 2.0 Beta 4.x? This small package will get you up to speed."
That''s my situation and the file I used.

Anyway I tried to upload the update package this morning, and ran the upgrade.php again. It suddently worked. But Danish characters in the forum was shown with funny A's.
The forum was before the update running UTF-8 - Danish. So I checked my database and everything was shown as they should - æ showed as æ etc. I then created a post and now that particular post was shown with strange a's in the DB. Then I ran the option in the forum to convert to utf-8 (even the db already was).
And then it all worked as it should. Æ was still shown as æ in the db, so something must have changed in the forum´s files itself. The new post I had created was completely wrong with strange ? turned on the head. etc.

The collation was right for each table before the upgrade and after the upgrade. The forum output was in UTF-8 format before the upgrade and after the upgrade.

So something must have gone wrong during the upgrade, I just don't know what. Should I be ok now, or do I need to run the large upgrade?

[metallica48423]

I'd suggest using the large upgrade just to make sure everything is fresh and good to go, so there's no questions about it.

[Akyhne]

So that will do no harm to run the big upgrade on the already small upgrade?

[metallica48423]

Not that I can think of.  If it doesn't need to change anything in the database it wont.  But the upgrade.php's between both should do the same thing

I was more referring to files than the database.

[Akyhne]

So basically just copy the files from the big package over the old ones and upload without running the upgrade file?

[metallica48423]

pretty much yes. 

[Akyhne]

Well I checked the versions in the file version compare tool in the forum. It actually says that my files are ok, but a few of the "current" files just have a

[metallica48423]

which have a

[Akyhne]

Look at the attachment above..

[Akyhne]

Anyway I tried to upload the update package this morning, and ran the upgrade.php again. It suddently worked. But Danish characters in the forum was shown with funny A's.
The forum was before the update running UTF-8 - Danish. So I checked my database and everything was shown as they should - æ showed as æ etc. I then created a post and now that particular post was shown with strange a's in the DB. Then I ran the option in the forum to convert to utf-8 (even the db already was).
And then it all worked as it should. Æ was still shown as æ in the db, so something must have changed in the forum´s files itself. The new post I had created was completely wrong with strange ? turned on the head. etc.

The collation was right for each table before the upgrade and after the upgrade. The forum output was in UTF-8 format before the upgrade and after the upgrade.

So something must have gone wrong during the upgrade, I just don't know what. Should I be ok now, or do I need to run the large upgrade?

I just tried this in another forum I got. Same issue. This must be a bug.

[Akyhne]

It can be replicated in a clean installation and then upgrading on that. Same error. I also have issues with forum time, non-hidden IP's, core features not being saved.

The issue with Core features not being saved and IP's not being hidden seems to be related. They both vanished by saving the settings in the forum. They were in two different forums, two different servers in two parts of the world.
The forums have this in common:
Both pretty new installations, both only had a few mods that were uninstalled before upgrading, both running Danish UTF-8 from the beginning... and both were upgraded from beta 4 to RC1 a week ago.

No errors in the log, no troubles at all during upgrade, no issues at all. Only the mentioned issues after upgrading.