Hey guys. I need some help. I was updating one of my client websites and something has happened to my blog section. This is a Perch CMS enabled site that is pulling data from an SQL database. Although the news (blog) and archive pages are still working fine. The post page is not and I can’t figure out why.
I contacted Perch and Rachel is basically saying I didn’t follow their video, even though the blog was working fine for the past year prior to the latest Perch update. Here’s the link to that support discussion as well: http://support.grabaperch.com/index.php?pg=forums.posts&id=9251
I checked all of my paths and they seem to be fine. I am totally perplexed. Help!
The problem is when Perch updates its app, it often changes the database schema so if I upload a previous Perch SQL file the new Perch core may not recognize the old fields.
Drew is on the case now and he too suspects an upgrade issue. I’ve offered to send him the MySQL database for closer examination and perhaps some manual correction. I’ll keep you posted. (fingers crossed)
That’s why I asked if you also backed up the old perch folder in addition to the db, for exactly this reason. Before upgrading I always duplicate the entire perch folder so if it all goes $!$s-up it’s a simple swap.
Todd
The problem is when Perch updates its app, it often changes the database schema so if I upload a previous Perch SQL file the new Perch core may not recognize the old fields.
If you’re sure the backup folder and db were created at the same time then yes, it’s a simple swap. I’ve done it this way myself without issue. However, if the backup folder and db were created on different dates then it’s riskier because there might be crucial differences; maybe you upgraded a specific app etc.
Todd
So I should be able to just replace my entire Perch folder and the db, correct?
Going forward with updates I would also suggest you first upgrade your non-critical dev copy, not the live site. Better to find and fix issues there. I had a similar issue two days ago with a MODX add-on update which broke part of the site but I was able to spot it locally before I attempted a live site update. Saved me a lot of trouble.
Usually, I’m pretty good at catching this stuff so any problems never make their way on to the live server. But I totally blew this one. I’ll need to review my workflow and backup procedures to ensure this doesn’t happen again.
Since it appears that only the Blog fields are affected, do you think I can simply delete the fields associated with the blog and have Perch recreate them?
I would check with Drew first. I once had a Perch Gallery problem where a client decided to muck about with the actual db structure (do not ask me why!) and needless to say they made a mess. After consulting with Drew I was able to manually delete some stuff from the db and was able to get it running again. I don’t suggest going this route without first consulting the devs.
Todd
Since it appears that only the Blog fields are affected, do you think I can simply delete the fields associated with the blog and have Perch recreate them?
While we’re on this subject, may I ask how you handle backups? In other words, do you create backups for both your live and development copies or just one or the other?
Yes. I prefer to maintain a clear distinction between the two.
Todd
While we’re on this subject, may I ask how you handle backups? In other words, do you create backups for both your live and development copies or just one or the other?
Good news! Drew said give it a try so I deleted ALL of the Perch Blog tables in the db and reinstalled the Blog app. Everything is working great, although I have about 1-2 hours of blog restoration ahead of me.