MT doesn't process MT tags within the entry body. That's why the tag is still in your image when you see its properties.
The easiest way to deal with this is just hard code in your full path; that way your image won't break when you are in archive directories.
Kristine
Full Version: MTBlogURL Parse Error in Entry?
It will not work to put an MT tag in an entry. It won't get processed. 
This goes for *all* MT tags. Honest!
What you're seeing is maybe the "photos/image.jpg" part that you wrote in.
Brenna
This goes for *all* MT tags. Honest! What you're seeing is maybe the "photos/image.jpg" part that you wrote in.
Brenna
No, kadyellebee, you're right. For some reason I thought I had seen the URL in the source, when I must've looked at the image properties. I know better than that. Notice I posted that at 4:00 in the morning? I had been up all night configuring.
OK, I should really go bang my head repeatedly and get some sleep...
I had been up all night configuring.OK, I should really go bang my head repeatedly and get some sleep...
Just started using MT2 and I love it. Good work, guys.
I may, however, have encountered a bug.
I'm using the <$MTBlogURL> tag to point to an image source within an entry body. Basically, it looks like this:
What I get when the entry is built, though, is:
The BlogURL is inserted, but the <$MTBlogURL$> tag remains.
I may, however, have encountered a bug.
I'm using the <$MTBlogURL> tag to point to an image source within an entry body. Basically, it looks like this:
CODE
<IMG SRC="<$MTBlogURL>photos/image.jpg">
What I get when the entry is built, though, is:
CODE
<IMG SRC="http://www.mydomain.com/blog/<$MTBlogURL>photos/image.jpg">
The BlogURL is inserted, but the <$MTBlogURL$> tag remains.
Well, it's getting partially parsed because the URL is being stuck in. It's just not cleaning out the MT tag when it does it.
Seems like a feature that's just not working completely. And if getting a result at all is unintentional, it still seems like a nice thing to be able to use within an entry.
Besides, my image wouldn't break as long as I'm using <$MTBlogURL$>, since it's an absolute path; that's kind of the point.
This:
would be the same as this:
Seems like a feature that's just not working completely. And if getting a result at all is unintentional, it still seems like a nice thing to be able to use within an entry.
Besides, my image wouldn't break as long as I'm using <$MTBlogURL$>, since it's an absolute path; that's kind of the point.
This:
CODE
<IMG SRC="<$MTBlogURL>photos/image.jpg">
would be the same as this:
CODE
<IMG SRC="http://www.mydomain.com/blog/photos/image.jpg">
Treat said:
Nope, its not parsing at all; I'm guessing you are just viewing the source or the properties of the broken image on a page in the same directory that you want it to be in! If you were to view this same entry with the images in your archives (if they are in a seperate directory), I bet you'd see that the path has your archive directory on it!
Make sense?
Kristine
QUOTE
Well, it's getting partially parsed because the URL is being stuck in. It's just not cleaning out the MT tag when it does it.
Nope, its not parsing at all; I'm guessing you are just viewing the source or the properties of the broken image on a page in the same directory that you want it to be in! If you were to view this same entry with the images in your archives (if they are in a seperate directory), I bet you'd see that the path has your archive directory on it!
Make sense?
Kristine
Tee hee, the middle-of-the-night bug hits again - isn't it funny how the light of day brings new insights?!
Kristine
Kristine
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.