Closed papamoose closed 2 years ago
I have the same problem, had to roll back. Same error message as above.
@thestraycat What version are you using?
I expect this latest image broke a ton of people's wiki's.
@papamoose - I've rolled back to: lscr.io/linuxserver/dokuwiki:amd64-version-2020-07-29
I was finally able to successfully rollback.
Possibly this code didn't run for some reason or there is a bug root/migrations.
Same here. Broken wiki. Thought I might be going crazy :-)
Thanks for the rollback info!
Thanks for posting the issue. I am facing the same issue.
Pull request #45 looks related to this issue.
Latest release (4 hours ago) resolved this issue for me.
Great to hear! Digging into the commit that was part of the pull request for that release, the issue may have been around line 47 of this file.
I had the same issue, with my ls133 container not surviving the ls134 upgrade. I opted for a full rebuild to ls134 just to see the difference and save time, though I wish I'd thought to check here again before I started (didn't notice ls135). :)
I used backed up copies of my local.php file and /config/dokuwiki/data/ directory, and added a volume bind for the latter to make backing up easier.
Closing the loop on this. I updated to version-2022-07-31
aka latest at time of writing. It all works now. I had to edit the nginx config to ensure was set root /app/www/public;
but that was it.
@papamoose - Strange question, but does your 'Admin' button work on the mainpage?
@thestraycat Yes it works.
Latest docker image breaks the wiki:
When the docker-compose example clearly shows:
To get access to my wiki again using the latest version I did the following:
docker-compose exec dokuwiki /bin/bash
cd /app
mv dokuwiki dokuwiki.bak
ln -s /config/dokuwiki /app/dokuwiki
mkdir cache locks tmp log
chown abc:users cache locks tmp log