[Snippet] NewsListing 6.3.3

I had the oddest thing happen, and it took me a few minutes to figure out what was going on! I had created some articles, and was using the NewsListing snippet to display the latest full article on the home page. I was using [*longtitle*] at the beginning of the articles, and the longtitle of the home page was appearing!

This is totally understandable, but it shouldn’t be that way. I’m not sure what it would take to make NewsListing respect the source of any document variables like that, or if it’s even possible.

I don’t think that’s understandable at all... down right weird, even!

Are you saying you have [*longtitle*] in the content of each article? If so, NewsListing does nothing about it and the parser executes it with the current page. I can add a line to replace all [*tags*] with their correct values if you wish?

That is correct, in the individual news documents I used <h1>[*longtitle*]</h1> for a heading. Since the articles was actually being displayed on the home page, it was inserting the home page longtitle instead of the news document’s longtitle. It probably shouldn’t do that; one would expect to be able to use the document tags in the article.

Susan here is a quick fix:

Replace:



with:

Nope. Still showing the host document’s longtitle.

Sorry, forgot that the [*longtitle*] is actually in the content field...

Please try the attached PRE-RELEASE version. In my tests this seemed to fix the issue.

David --- I’m still working on an elegant solution to the checkbox dillema (I’ve got an "uguly" one if you need it ASAP).

Yes, that took care of the doc variable issue. Thanks!

Quote from: Mark at Feb 02, 2006, 12:19 AM

David --- I’m still working on an elegant solution to the checkbox dillema (I’ve got an "uguly" one if you need it ASAP).

If you have the ugly one at hand, yes please I could use it

If it’s not copy->paste->send thing and takes time to do, I’ll wait for the release then. Thanks Mark !

Great works Mark !

ps:

In version 6.5 there is again