I have a site where I perform a full rebuild (Publish All Files), and - to cut to the chase - it doesn't.
It publishes index, then categories (I think) and then goes into the publishing entry phase. It does that for a bit and then gets into an endless loop refreshing the status page every couple of seconds with the progress bar not shimmering like it normally does, but maybe 5% over. Looking at the pages on the server they are not being updated - I have no idea what MT is actually doing when it gets into this mode.
It behaves like it's publishing some entries and then some kind of timeout happens that causes it to go into this weird state/loop.
Anyone have a clue what might be happening?
Leo
Reported on Movable Type 4.2
Have you checked the Activity Log while you're rebuilding? Check both system and blog views. Also, have you checked the permissions on the directories you're writing to?
Nothing in the activity log while this happens.
Permissions are fine - I can go to an individual entry and Save it and everything publishes fine. It's only in this mass rebuild where things are a problem.
Thanks!
Leo
I just noticed that you did an upgrade from 3.2->4.21. Sorry, didn't connect this with your previous question. If it were me, I'd not do an upgrade from 3.2->4.21; I'd do a clean installation given all of the code that got updated. The time between 3.2 and 4.21 is big enough that a lot of modules got updated, and a lot of database changes got made. Think of it like upgrading from Windows 2000 unpatched to Windows XP SP3. It may work, but you're much better off backing up your data and reinstalling the software.
Oh, please tell me it ain't so. :-)
I've got a couple of fairly large blogs with lots of template work that would be a huge pain to transfer via clean installs.
For the most part the upgrade has gone very well. Now if I could just get all the pages to rebuild I'd be much happier...
Thanks,
Leo
Well, an alternative is that you backup your static data, delete Movable Type and put in a fresh copy. That way, you're just refreshing the Movable Type installation instead of the database as well.