News:

Want to get involved in developing SMF, then why not lend a hand on our github!

Main Menu

Upgrade errors (1.1.8 to 1.1.9)

Started by lyrae, June 10, 2009, 12:20:57 AM

Previous topic - Next topic
Print
Go Down Pages 1 2 All
User actions

lyrae

#20
June 14, 2009, 11:54:40 AM
An Error Has Occurred!
Your session timed out while posting. Please go back and try again.


:( :( :( :( ???

Aleksi "Lex" Kilpinen

#21
June 14, 2009, 01:01:17 PM
You could try emptying the smf_sessions table in the database, and then log in again etc.
Slava
Ukraini!
"Before you allow people access to your forum, especially in an administrative position, you must be aware that that person can seriously damage your forum. Therefore, you should only allow people that you trust, implicitly, to have such access." -Douglas

How you can help SMF

Norv

#22
June 14, 2009, 01:04:54 PM
Also, if you change to "use domain-independent cookies", please make sure you erase cookies before trying again.
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker

Also known as Norv on D* | Norv N. on G+ | Norv on Github

lyrae

#23
June 14, 2009, 02:02:12 PM
To be honest I'm almost convinced that the sessions error message is a red herring. I don't really get why emptying the sessions table would help. What effect would others' sessions have on me?

lyrae

#24
June 14, 2009, 02:51:03 PM
Well, I've got it updated now.

I guess the one time I thought the package manager worked for me, last fall when updating to 1.1.18, it didn't. Somewhere along the line some files must not have been updated. For example, PackageGet.php was an old version. I just re-uploaded all the themes, languages and source files, and was able to update to 1.1.9 after doing so. (I never emptied that table.)

The sessions error was a total red herring -- this had only to do with file versions and nothing to do with sessions or cookies. Maybe at some point the error mesages file in the languages directory had some numbers moved and it was returning #304 and #305, but the text for those had been changed?

Who knows.

In any case, thanks for all your help.

Norv

#25
June 14, 2009, 03:04:35 PM
Interesting, thanks a lot for letting us know.
So, rather, you needed to overwrite some .php files with 1.1.8 versions, because you actually had older versions. *sighs*. It will definitely be good to know for next time...
But even more, overall it's good to know you had it fixed!
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker

Also known as Norv on D* | Norv N. on G+ | Norv on Github

Aleksi "Lex" Kilpinen

#26
June 15, 2009, 02:50:34 AM
I'm glad you got it right :)

But,
Quote from: lyrae on June 14, 2009, 02:51:03 PM
The sessions error was a total red herring
Isn't exactly so either. If the package manager files were still 1.1.7 then the message was right, but due to a bug in the 1.1.7 version, that was fixed in 1.1.8.
Slava
Ukraini!
"Before you allow people access to your forum, especially in an administrative position, you must be aware that that person can seriously damage your forum. Therefore, you should only allow people that you trust, implicitly, to have such access." -Douglas

How you can help SMF

Sel_888

#27
June 15, 2009, 11:18:04 AM
I still don't understand that if the upgrade through the package manager doesn't work, why they just don't FTP up the whole thing like the upgrade says to do if you download it through this site....  ;)
I didn't get it wrong, I just found 10,000 ways it doesn't work...

LagunaChapala.com - A community site for South Shore residents
Print
Go Up Pages 1 2 All
User actions
Advertisement: