Doing a fairly routine upgrade from 4.25 to the current version 4.32. I've backed up the db, I went the 'upgrade fresh' route and put my mt-config file in the new version's directory. I got the upgrade screen and the standard long list of database upgrade messages.
Upon logging in, everything seems fine. But when I rebuild my indexes, I notice something strange - all the archive links point to www.sitename.com/archives/ (the main archives directory), so all the links are truncated. This includes the published links, but also inside the MT system the links to "view this entry."
The other behavior I notice is when I make changes to a specific entry - change the text in the entry and publish - the entry saves (and the new page reflects the changes) but the entry does not publish the changes on the public page.
The only other symptom is any activity (rebuilding, different pages inside the MT interface) seem quite slow compared to the previous version.
Related, I've searched the forums. Is there a suggested method of downgrading in a situation like this? Specifically related to mysql - can I attempt to revive the 4.25 directory and allow MT to adjust the tables or should I re-import the db file first and start from there?
thanks!
Reported on Movable Type 4.3
What are your archive mappings on each of your archive templates?
Hi Beau -
On the individual archives I've attempted to publish, there is a custom mapping, the following:
.html
This worked fine in 4.25. (It was my work around for this issue)
The category is : ../%c/%i
page: folder_path/page_basename.html
another category type is: .html
I can understand how this would impact rebuilding my individual entries, but wondering how it would the archive links inside the MT system.
Another piece of information about this install - it had been afflicted by the "time to upgrade" syndrome in 4.25, I had added the schema to the config file (which didn't solve the upgrade problem but when did the upgrades, it didn't rebuild all the comments and revert the templates back to previous versions). One of the reasons to upgrade to 4.3x was to fix the 'time to upgrade' issue.
thanks much
sorry here's the individual archive:
the "another category" is:
Just an update on this one - it seems removing the from the individual archive mapping (and replacing with simple MTEntryTitle dashify="1"$) does fix the problem described above.
So the public index with the truncated links and the ability to write new individual entries works, as well as the links from inside the MT interface.
Now I'm searching for a work-around to doing a date-based switch on the archive mapping...
...removing the Mtifdateafter and Mtifdatebefore... individual archive mappings.
The problem, it seems, is those archive mappings were old, based on the use of the datetags.pl plugin. Upon upgrade, it seems to have reverted to old versions of the archive mappings, since MT didn't understand the mappings without the plugin.
(Sorry for the posting spray)
So sounds like the problem is solved?
Yes! I appreciate your question, which lead me to finding the source of the problem.
Fingers crossed that the "upgrade now" issue is solved!
thanks again...