Forum
Upgrading to Blog 5.0 - 11,147 Posts
Hi There,
I have upgraded to Perch Blog 5.0, but what I didn't realise is the client has over 11,000 articles to update.
Is there a quicker way of updating this instead of waiting for this - https://goo.gl/p27DvR to cycle through.
Just thought I would ask :-)
Thanks
By the time I wrote an alternative, the update would have already finished. It should only take a few minutes.
Its taken nearly two days and still cant access the blog
I've tried the force update on the blog app but not sure if it was the right process
Really? Is it ticking through? It should do 10 and then reload. Each reload should take about a second.
Yes its ticking through slowly, currently on Page 159 of about 714. But we are expecting a high spike of traffic at 2pm as its Wigan Warriors squad announcement.
Just wondering is there anything I can do to make this quicker or stop it (Without Reverting back) so they can access the blog at least.
It really should only take a few minutes. If it's being that slow, that indicates perhaps that something else isn't right with the setup.
A lot of articles have been imported from an old system. But not sure if that would be the case. How do I investigate if there is a problem with the blog app.
You are right I updated to the latest version of Perch itself and it took seconds, the same didn't apply for blog.
Here is my DR if that helps
My Post.php page is the following
My Post.html template is the following
Any help would be great on this.
How long did it take in staging?
We did it live on the server, I updated Perch and went through quick with no issues, so just thought to myself while i'm here I might as well update the blog big mistake.
So I have left the post updating overnight (from 7pm until 7:30am next morning + plus still running) its 6370 out of 11,000.
The server is a cluster with 1 DB server so I can think that this could be an issue.
How long does each page load take?
Roughly 1.5 / 2 minutes
On a healthy system it should take a second or two at most.
Are the numbers incrementing logically? There's not a chance the process is also being run from another node in the cluster is there?
If you're doing this directly on a live server without testing it first, I'm not sure there's much I can do to practically help. A good step in future would be to test updates in your staging environment to make sure they're going to work for your configuration before putting them live. This advice is also included in the update notes:
Hi Drew,
Thanks for your help on this and your points are noted.
The update process has now completed. One thing I noticed When I ran the update the query string went up to page 1147 so if its 10 posts per page that's 11470 posts.
Well now that the update has completed I went back into the blog and noticed there is only 744 pages (See here - https://goo.gl/reEXiN) which is 7440 posts.
Can't understand why it would go up to over 11,000 posts.
Any ideas?
Thanks Barry
It's 15 per page, so 15 * 744 = 11160. It may be also processing deleted posts which might account for the rest.
11160, Thats the amount of posts that were in the system. But the update went up to page 1116 (According to the query string) so the update must have been processing 10 posts per page.
I will have to look at some other problems that it might be.
This is what our hosting company have said:
I'm not fully clear on what problem you're currently experiencing. What are you trying to fix?
I'm just trying to figure out why this update took over 24 hours to update.
Have you now run it locally to get your dev systems up to date?