[pmwiki-users] strange update problem

[Petko Yotov]

Nothing changed between recent PmWiki versions that would cause this. I 
don't use softaculous or o2switch.

When you update your PmWiki version, PmWiki calls script/upgrades.php to 
see if some automatic changes/fixes can be applied, then writes the new 
version number in the page SiteAdmin.Status (in the metadata), then 
redirects back to the page you requested. This is usually transparent / 
unnoticeable.

If you have $EnableReadOnly set, or if the filesystem is read-only, it 
is possible PmWiki tries to do the above and fails, and complains with 
the warning. I haven't tried an upgrade with $EnableReadOnly set, this 
is probably fixable, I'll review this.

You can disable the upgrade checks with this line in config.php:

   $EnableUpgradeCheck = 0;

Petko


On 09/12/2022 08:46, jdd at dodin.org wrote:
> Hello,
> 
> I had a strange update problem right now. I could easily restore
> function, so it's not really important.
> 
> I have a special working system in that my main pmwiki is read only, I
> usually edit an other session, rsynced with the main one each 15
> minutes.
> 
> I just (reading the rant an other user wrote) updated to the last
> 2.3.16 version. This update was done with the softaculous system,
> provided by my hosting provider, o2switch.
> 
> When I first read my wiki after the update, I got a "pmwiki in read
> only mode, can't edit" message. Notice I *didn't* try to edit it, just
> read.
> 
> I accessed the local config through ssh and commented out the readonly
> config line and the wiki was working normally.
> 
> what is specially surprising is that I could immediately remake the
> readonly setup and the wiki still works ok, letting me with no idea
> why it didn't do it previously.
> 
> may be some sort of first run config? or cache? or softaculous trick?
> 
> the web site is simply http://dodin.org
> 
> thanks
> jdd