I always had some doubts with that "disable" option. The update instructions are telling you to to delete all files except "ext, images, ets" .. But when you delete your board files, the "disabled" message is not showing because everything is gone ...?
Matthew G. Saroff wrote: ↑Thu Jun 14, 2018 8:39 pm When I do an update, I expect the board to be down, and as opposed to posting in a pinned topic (where it is frequently missed), I'd like to have a page come up with the message, and then they would have to click through, so that the get the notice.
Exactly, also in those moments our friend google indexes the site with his mistakes, doing damage imaginable.Froddelaar wrote: ↑Thu Jun 14, 2018 9:24 pm I always had some doubts with that "disable" option. The update instructions are telling you to to delete all files except "ext, images, ets" .. But when you delete your board files, the "disabled" message is not showing because everything is gone ...?
You could create a copy of your site and database, upgrade the copy, then move of the old installation in a backup directly and immediately after move the files from the upgraded one, and you'll have more of a seamless transition.Froddelaar wrote: ↑Thu Jun 14, 2018 9:24 pmI always had some doubts with that "disable" option. The update instructions are telling you to to delete all files except "ext, images, ets" .. But when you delete your board files, the "disabled" message is not showing because everything is gone ...?
Actually, I'm worried about the unparsed posts throwing errors for a few weeks, there are over 500,000 posts on the board, and I figure that it would take a few weeks for the background task to finish that.Toxyy wrote: ↑Fri Jun 15, 2018 12:17 amYou could create a copy of your site and database, upgrade the copy, then move of the old installation in a backup directly and immediately after move the files from the upgraded one, and you'll have more of a seamless transition.Froddelaar wrote: ↑Thu Jun 14, 2018 9:24 pmI always had some doubts with that "disable" option. The update instructions are telling you to to delete all files except "ext, images, ets" .. But when you delete your board files, the "disabled" message is not showing because everything is gone ...?
How do you expect them to throw errors?Matthew G. Saroff wrote: ↑Fri Jun 15, 2018 2:22 am Actually, I'm worried about the unparsed posts throwing errors for a few weeks, there are over 500,000 posts on the board, and I figure that it would take a few weeks for the background task to finish that.
Going from 3.0.12 to 3.2.2.Toxyy wrote: ↑Fri Jun 15, 2018 3:30 amHow do you expect them to throw errors?Matthew G. Saroff wrote: ↑Fri Jun 15, 2018 2:22 am Actually, I'm worried about the unparsed posts throwing errors for a few weeks, there are over 500,000 posts on the board, and I figure that it would take a few weeks for the background task to finish that.
And with a board that large you can export the database using cli, download it, update the board using xamp or mamp or something, upload the upgraded database, install the phpbb3 files somewhere, then update some blank database that installation uses with the upgraded one, again in cli. That would make it faster.
That probably doesn't answer your issue though about post errors which I don't fully understand?
Code: Select all
/usr/bin/php7 ./bin/phpbbcli.php db:migrate -vvv
Code: Select all
/usr/bin/php7 bin/phpbbcli.php reparser:reparse post_text --range-min=600000 --range-max=625000
Which is why I always use the "changed files" update/upgrade option. That way there is less likelihood of a relevant file not being available as at worst you will be overwriting a file which will take next to no time, and it may even be cached anyway.Froddelaar wrote: ↑Thu Jun 14, 2018 9:24 pm I always had some doubts with that "disable" option. The update instructions are telling you to to delete all files except "ext, images, ets" .. But when you delete your board files, the "disabled" message is not showing because everything is gone ...?
I just did AAMPS (much like XAMP) and got about the same speed for reparsing.Toxyy wrote: ↑Fri Jun 15, 2018 3:30 amHow do you expect them to throw errors?Matthew G. Saroff wrote: ↑Fri Jun 15, 2018 2:22 am Actually, I'm worried about the unparsed posts throwing errors for a few weeks, there are over 500,000 posts on the board, and I figure that it would take a few weeks for the background task to finish that.
And with a board that large you can export the database using cli, download it, update the board using xamp or mamp or something, upload the upgraded database, install the phpbb3 files somewhere, then update some blank database that installation uses with the upgraded one, again in cli. That would make it faster.
That probably doesn't answer your issue though about post errors which I don't fully understand?