Topic: SMF Udate 2.0.13 is out

[Maxx (OP)]

SMF 2.0.13 has been released, but I  would wait I tried to update, but failed due to old language files in some old themes. I never had this issue before.. I need to go ing and maybe clean out old themes first? Must dig in deeper on this error!

regards,
maxx

[Skhilled]

Thanks but it doesn't show up in the admin as the current version so there may be other issues with it?

[Maxx (OP)]

Yes I notice that Yesterday..I always update via FTP. to insure the tables get done!

maxx

[Skhilled]

Hmmm, if you try to install 2.0.12 it will tell you the 2.0.13 is the current version but will let you install it anyway. I just created a test site to see how the upgrade would go before going live.

EDIT: LOL! When I went into the admin it shows 13 as the current version (as it should) although I did not upgrade it yet. But no matter how hard I try (clearing the cahe, etc.) I can't make it show on my site or here! I guess it only shows on a fresh install.

[Skhilled]

Got the same as you when I uploaded the upgrade files and tried to run it!

[Maxx (OP)]

Just read over thewre that if you run all maint functions and clear cache, after you install the update all will show good and table will be fixed!

It seems they are still dealing with the Patch, but I never use the patch anyway!
Mine seems good now

maxx

[Skhilled]

I used the patch but there is something wrong with the upgrade for the db. It still shows the same error if you try to run it.

[Skhilled]

OK, did 2 separate tests.

1.  Installed 2.0.12, fresh install. Used UTF8. Upgraded to 2.0.13 using the patch via the admin. It shows "2.0.13" in the admin and the copyright. I uploaded the db upgrade files to upgrade the db but got the language file errors.

2.  Installed 2.0.12, fresh install. Used UTF8. Upgraded to 2.0.13 uploaded all files from the large upgrade package via FTP. It shows "2.0.13" in the admin and the copyright. I ran upgrade.php but got the language file errors again.

I will run a final test without using UTF8 during install. It's the only thing I can think of left to do.

[Maxx (OP)]

That be the language file for the core theme.. still at the old language.

If you update to 2.0.13 via FTP and then go in the admin and do the full/all maintenance it will update all you table and stuff, this should work well. it did for me!

maxx

[Skhilled]

I did that a number of times but still does not work! I even deleted the core theme folders although the error does say "default"

I'm starting to think it's a server issue of sorts.

[Maxx (OP)]

what I mean is the not run the upgrade.php. just load the files via FTP and then do the maint. if you have any issues it will show in the maint process,, the language stuff need be changed by them.. I feel!

[Skhilled]

But if you do not run the db upgrade the db will not be upgraded and errors may show with some mods. It will give the error that says "your database might require an upgrade", etc...

[Maxx (OP)]

Well when I ran the maint, compared the DB, no errors, showed version 2.013 and Not errors in the logs, and I have at least 10 Mods and they all work fine not issues and this what they say at SMF and of course (Used UTF8). I will wait and see what comes up at their site.. and get back but seems all is good at my surfacethemes live site!

[Skhilled]

You are correct but your database is not upgraded to the same version. Only the files are. When you try to install or upgrade a mod that checks the db version you WILL get that error! This has been happening since SMF 1.1 from 1.0.


 

I figured it out!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I initially thought the issue may be related to the UTF setting but it wasn't. The error when you run upgrade.php states that the language files are not up to date. Since the language files are pretty straight forward with very little php coding, I figured there should be something in them that was causing it or would lead me to it. I opened a file and the very first line is this:

// Version: 2.0; XXXXX

The XXXXX = the first name of the language file such as Admin.english.php. In that particular file you'll find:

// Version: 2.0; Admin - get it?

So, I used Notepad++ to search all of the files in the /Language folder for "// Version:". The results should show me every file that has it in it. All of the language files have it so it showed them all to me in a list. Only 2 of the files were different:

index.english.php and ManagePaid.english.php. The first had "// Version: 2.0.12;" and the second had "// Version: 2.0.10;". All of the rest had "2.0" only. So, I changed the numbers to 2.0.13 to see if it would work. If not, then I'd change them to "2.0" like the others. It worked!!! You can now run upgrade.php and actually upgrade your database properly!

I do think that the files should be "2.0" like the rest because come the next upgrade it may not work if they are different. I think the dev who was working on the files specifically numbered them to avoid confusion and they got into the final package instead of changing them to "2.0" again.

[Ken]

You are correct but your database is not upgraded to the same version. Only the files are. When you try to install or upgrade a mod that checks the db version you WILL get that error! This has been happening since SMF 1.1 from 1.0.


 

I figured it out!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

hahahaha!