Updating the Forum via Package Manager doesn't work

[natcip]

Hey guys,
my forum is currently on version 2.0.15. I tried to install the 2.0.16 update via the Package Manager in the Admin Center, but afterwards the board is still on 2.0.15.
And when I click the "update your forum"-link again it gives me this message (referring to 2.0.16):

This package is already installed, and no upgrade was found!
You should uninstall the old version first to avoid problems, or ask the author to create an upgrade from your old version.
Please remember to always make regular backups of your sources and database before installing mods, especially beta versions.

All my directories are set on chmod: 0777 btw.

Updating the board with the Package Manager has never worked for me, and I usually ended up having to update everything manually.

[Sir Osis of Liver]

Does the update package install without errors?  Have you cleared forum cache and browser?

[Doug Heffernan]

If you look at the  error message being posted above, it looks like it is about a mod and not the update. I find that odd.

[Illori]

If you look at the  error message being posted above, it looks like it is about a mod and not the update. I find that odd.

the upgrade is a mod, it would give the same error message for a mod or the patch.

[Sir Osis of Liver]

I believe package manager treats an update like any other mod, and will post that error if update is already installed.  Will have to try it.  Not a permissions problem, that would give an unwriteable files error.

[Arantor]

It'll post that error if it *thinks* it is installed even if it isn't - sometimes this happens where the filesystem reported permissions to write but when the time came, it didn't actually occur.

[Sir Osis of Liver]

Hmm, the update your forum link should d/l and install 2.0.17 if .16 is already installed.  What do you see here in package manager?

SMF 2.0.17 fixes a bug introduced in 2.0.16 that could cause significant performance issues when retrieving RSS feeds, and fixes some annoying warning messages that could appear when using SSI.php. You can install this patch (click here to install) to fix your forum and update it to 2.0.17.

[Sir Osis of Liver]

It'll post that error if it *thinks* it is installed even if it isn't - sometimes this happens where the filesystem reported permissions to write but when the time came, it didn't actually occur.

Can't replicate the error.  If the package is marked uninstalled with fix_packages, can it be reinstalled?  Some servers will not allow 777 for security reasons, but that would cause other problems as well.

[Doug Heffernan]

If you look at the  error message being posted above, it looks like it is about a mod and not the update. I find that odd.

the upgrade is a mod, it would give the same error message for a mod or the patch.

Ah ok. Thank you for your reply. I thought that that would have been 2 separate things. Hence why I was a bit confused by the error message.

[natcip]

Hmm, the update your forum link should d/l and install 2.0.17 if .16 is already installed.  What do you see here in package manager?

SMF 2.0.17 fixes a bug introduced in 2.0.16 that could cause significant performance issues when retrieving RSS feeds, and fixes some annoying warning messages that could appear when using SSI.php. You can install this patch (click here to install) to fix your forum and update it to 2.0.17.

2.0.16 isn't installed, even though the message says so. In the Admin center it says my current version is 2.0.15 after I tried to install 2.0.16.


My webhost told me it could be a permissions issue, because he's using mod_php.

[Sir Osis of Liver]

Don't recall any problems with upgrades involving mod_php.  Have you reset your dir/file permissions to 755/644?

[Kindred]

it's a chown issue combined with a chmod/permissions issue

basically,
SMF sends a query to the system asking "can I change these files, in these places"
the system reports  "YUP!"
Smf then proceeds to send the queries... changing those files
the system quietly, with no error, rejects the changes because PHP is not the OWNER of the files and is not allowed to change them....

this happens, most often, when the files were uploaded with FTP (thus uploaded, with the owner being tracked as the hosting account)
*AND* PHP is set up to run as "no one" instead of running as the account or even system.