Upgrade 1.1.17 to 1.1.18: it's confused

[a1tsal]

Hi,

A SMF 1.1 site that has been running ~5 years, upgraded version to version.

The single-click upgrade process for 1.1.17 -> 1.1.18 ran, and claimed to have succeeded.

However, the main admin screen thinks it still needs upgrading.

index.php?action=detailedversion reports:

SMF File   Your Version   Current Version
SMF Package   SMF 1.1.17   SMF 1.1.17
Sources   1.1.11   1.1.18
Default Templates   1.1.12   1.1.12
Language Files   1.1.15   1.1.18
Current Templates   1.1.12   1.1.12

Note that it says "current version" is 1.1.17, which is presumably part of why it is confused.

What should I do?

Thanks!

[Dzonny]

Hello there.

Try to go to scheduled tasks and run "Fetch Simple Machines files". Let us know if that helps.

ETA: Sorry, this is 1.1.x only feature.

Do yo have "SMF 2.0.4 | SMF © 2013, Simple Machines" in your footer?

[a1tsal]

Sorry, where do I find "scheduled tasks"?

Thanks!

[a1tsal]

No, it has "Powered by SMF 1.1.17 | SMF © 2006, Simple Machines ".

[a1tsal]

Ah, hmm, now I am getting "You cannot download or install new packages because the Packages directory or one of the files in it are not writable!"

There's probably a permissions problem. I'll look into that. Everything in Packages/ is owned by "nobody", and is marked user-writeable, which seems correct, though.

[a1tsal]

OK, I'm still getting the "not writeable!" error, after doing "chmod -R a+w Packages". So it's confused about that...

Thanks for your help.

[kat]

Sounds, to me, like your host hasn't given you full CHOWN ownership of your files.

Give 'em a slap!!!