« The Rock : A Tale of Seventh-Century Jerusalem | Main | Islamic Calendar »
پیر 18 ستمبر 2006Monday, September 18, 2006
Movable Type Upgrade
I just upgraded to Movable Type 3.32 and am now running Movable Type on UTF-8 natively (that’s my doing, not Six Apart’s), but more on the Unicode issues later.
Here’s what I like about the changes in MT 3.3.
- Movable Type can now be configured (using the DeleteFilesAtRebuild configuration directive) to delete files made unnecessary by changes made in the administrative interface. Individual archive files are deleted when previously published entries are deleted or unpublished. Category archives are deleted when their corresponding categories are deleted.
- Pings coming from the same IP address with the same Source URL are now silently discarded. A success value is, however, sent to the pinging server so that the doesn’t keep trying to reping. [Not the best approach but better than duplicate pings.]
- The order of attributes specified in template tags is now observed and respected (e.g. trim_to=”10” remove_html=”1” is different than remove_html=”1” trim_to=”10”). In addition, the same attribute can now be processed multiple times if so desired (ie, regex=”abc” regex=”def”). [ Jacques must like that.]
- Added textarea resizing controls to the template editing pages.
- In version 3.2, using certain later versions of MySQL or postgreSQL, some non-ASCII characters were not returned correctly from the database as originally written. This was caused by a mismatch between the character_set_client and character_set_connection variables. To fix this problem, we’ve added a configuration directive, SQLSetNames, which will inform the database of the character set being used by the client. The database character set must match the PublishCharset used by Movable Type. [I had implemented it already in my system.]
- Implemented TrackBack transcoding between many character sets via Encode/JCode modules. This allows for correct display of TrackBacks sent in an encoding different than the recipient’s blog character encoding. [It is good that Six Apart is doing this, but I don’t like their implementation and prefer the one by Jacques Distler which I have been using already.]
I also like the inclusion of tags, though it would take me some time to populate my posts with tags and make any use of them.
The search page is barely working right now, but I’ll fix it soon. If there are any other problems with the upgrade (with commenting, trackbacks or anything else), please let me know.
I have also made some template changes. One is the inclusion of a menu bar at the top so that you can find the most common pages easily. Also, I am now including the sidebar in most pages other than individual entries.
Tags: movabletype, upgrade
Posted by Zack at September 18, 2006 11:23 AM in Internet
Related Entries
Advertisements
Trackback Pings
TrackBack URL for this entry:
http://www.zackvision.com/mt/zv-trbk.cgi/1021
Listed below are links to weblogs that reference Movable Type Upgrade:
» Movable Type and Unicode from Procrastination
Running Movable Type natively in Unicode was not as difficult as I thought but it still required a number of patches to the code. [Read More]
Tracked on November 28, 2006 2:13 PM
Comments
Posted by: Zack (1784 comments) at September 18, 2006 1:26 PM | PGP Sig
Looks good - more managed :)
Posted by: Asma (46 comments) at September 19, 2006 6:30 AM
I personally think that the open source Wordpress was the best Content Managment System and that it was in a big lead from the paid Moveable type but after looking at your Moveable Type version,the things look good and aligned in both my browsers!!!
Hope Moveable type works best for you!!!
Posted by: Khushal (27 comments) at September 20, 2006 4:37 AM
Asma, Khushal: Thanks.
Posted by: Zack (1784 comments) at September 27, 2006 1:20 PM | PGP Sig
Post a comment
Note: Disagreements are welcome, but please keep it civil. Any comments full of hatred, bigotry, trolling or spam will be deleted and the commenter banned. Do read the commenting policy.
Valid XHTML: You have to preview your comment to make sure that it is valid XHTML 1.1. You will see the "Post" button on the preview page.
Urdu: To comment in Urdu, include "p[ur](urdu). " (with a space at the end and without the quotes) at the start of every Urdu paragraph. If you want to write an Urdu word(s) in an English paragraph, do it like this: %[ur](urdu)اردو%. If you want to put an English word(s) in an Urdu paragraph, write it like this: %[en](en)English words%.
PGP Signing: PGP-signed comments are encouraged. However, clearsigning Urdu text with GPGshell produces garbage.
MathML: Select the Textile with itex to MathML text filter. What you'll use is itex, which is a superset of WebTeX and differs somewhat from standard LaTeX.
Text Filters: For regular comments, whether in English or Urdu, keep the text filter setting to its default of Textile 2. Change it to Textile with itex to MathML when writing MathML.
Testing that comments work.
Yes, they do.