Movable Type Community Forum > Error after upgrade affecting dynamic publishing

Full Version: Error after upgrade affecting dynamic publishing

Movable Type Community Forum > Other Product Discussion > Bugs and Odd Behavior

windu2k

Oct 21 2004, 09:58 AM

I upgraded to 3.12 from 3.11 and discovered this error this morning after recieving a few concerned emails this morning:

CODE

Parse error: parse error, unexpected T_LNUMBER in /PATH_TO_BLOG_DIRECTORY/templates_c/%%CF^CF9^CF947666%%mt%3A31.php on line 194

Turning off dynamic publishing of individual archives avoids this, but it slows things down.

bschoate

Oct 22 2004, 06:22 AM

Can you delete the files under the "templates_c" directory and then view one of your individual archives pages and see if it still gives you that error? Either do that or edit your individual archive template which should invoke a rebuild of that template.

Also, I saw on your site where you mentioned that your .htaccess file was missing. I don't know how that could happen, since we never erase that file. There's code in 3.12 that will append to the .htaccess file if the file either does not exist or it does not already have Rewrite rules in it, but it is never erased by the application. Can you share any more details about your configuration? I'd like to get to investigate it further.

windu2k

Oct 22 2004, 10:35 AM

QUOTE

I did both and still got the same error. Those files appear after the first hit to a individual archive page. I cracked one open and there doesn't appear to be any errors inside, just php code. Line 194:

CODE

$email = "{{MTCommentEmail|sanitize:"1"}}";

More details on my .htaccess. It has rewrites and redirects in it. The redirects and the rewrites are to facilitate using FeedBurner to do it's thing to my feed and to make sure that dynamic publishing worked in the first place. I knew it was gone when I got an error message in my email saying that individual archive links didn't work and I had not remembered deleting it (since I had no reason to), so I assumed that MT may have had something to do with it.

Details of my host's config:

* PHP version 4.3.9
* Apache 1.3.31 (Unix)

As far as the upgrade itself went, I simply uploaded the upgrade files and did a rebuild as a check. If there was anything else I needed to do, I was not aware.

bschoate

Oct 22 2004, 01:56 PM

QUOTE (windu2k @ Oct 22 2004, 06:35 PM)

CODE

$email = "{{MTCommentEmail|sanitize:"1"}}";

Uh, that must be coming from code like this:

CODE

<?php
$email = "<$MTCommentEmail$>";
?>

That isn't going to work very well with MT/PHP since MT tags are converted into Smarty syntax which is then compiled into PHP code. So a MT tag in a dynamic template is going to produce a PHP block eventually, which won't parse properly if it's already in a PHP block!

I would recommend using this instead:

CODE

<?php
$email = $this->tag('CommentEmail');
?>

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.