1) add a key called 'extended' and test for it using the IfKeyMatches tag

2) use the IfEmpty plugin (also found here) and test the EntryMore value (or KeyValuesStripped if you're not storing them in the extended entry field) like this:
<MTKeyValues>
    <MTIfNotEmpty var="EntryMore">
        (there is info left in the extended entry field)
    </MTIfNotEmpty>
</MTKeyValues>

One of those should work for you.

<MTKeyValues source="[MTCategoryDescription]">
<MTKeyValuesStripped>
</MTKeyValues>

... but when I rebuild I get this error:

Build entry 'The California Boom' failed: Build error in template 'Category Archive': Error in <MTEntries> tag: Error in <MTKeyValues> tag:

With no detailed error message. Perhaps it doesn't know where to get MTCategoryDescription from? I tried it with random source strings ("MTFoo") and get the same message. If I use MTBlogDescription it works. I've had a dip into the code and the MT perldocs, but the learning curve to figure this out myself looks steeper than just asking!

Thanks for the plugins,
Kief

I know you told us it is "not formally ready for release" and on the MTForum you advised on August 23. that there was an update to 1.1 version.
Will you be releasing this after all? or will it maybe get obsolete by MT2.5?
Is there a problem with it for its unofficial state?

Sorry just curious, (also about Seth, how is he?)
Lawrence

Am I right that once you use this plugin, you should put it in every template which has {MTEntryBody} just to be sure formating on main index will be the same as on all the individual etc. pages?

Would it be usefull if it could be applied to {MTCommentBody} as well, or does this work already? (like apply_macros="1")?

On Seth: have you thought about Preventmefromdrivinginsane.com and let your visitors change dipers en do midnight feedings?
Lawrence

<MTEntries category="Feature" lastn="1" process_tags="1">
<MTKeyValues>
This works: <MTKeyValue key="asin"><br />
<br>
<MTIfKeyExists key="asin">
Found asin -- this shows up
<MTAmazon method="Asin" search="<MTKeyValue key="asin">" lastn="3">
... never reaches here ...
</MTAmazon>
</MTIfKeyExists>
</MTKeyValues>
</MTEntries>

Any suggestions?

I've used the KeyValues for a bookreview site of mine and it all worked just fine. I made two lists, one sorted after author and one after title.

The problem is as we entered into 2003 all my reviews from 2002 don't get listed anymore.

Any idea why?

You can see the original discussion here:
http://www.movabletype.org/cgi-bin/ikonboard/ikonboard.cgi?s=3e15b1ad6254ffff;act=ST;f=14;t=11157;st=0

Thanks in advance! :o)

Just wanted you to know, I use a great many of your plugins and while they are all great, I've found this one to be amazingly useful!

Keep up the good work!

If I didn't make any sense, I do apologize!!! ;)

The line you have:

<MTAmazon method="Asin" search="<MTKeyValue key="asin">" lastn="3">

Should be:

<MTAmazon method="Asin" search="[MTKeyValue key='asin']" lastn="3">

All the best,

--
Ian

What I'm seeing is that the header tag contents get shown on every iteration, and the footer tag contents are never shown.

For example, as input:

<MTKeyValues iterate="1" source="[MTEntryKeywords]">
<MTKeyValuesHeader>
Here are the keys:<br />
</MTKeyValuesHeader>
<MTKeyName>: <MTKeyValue><br />
</MTKeyValues>

Output:

Here are the keys:
KEYA: AAA
Here are the keys:
KEYB: BBB
Here are the keys:
KEYC: CCC

Is there a known problem in this area, or is there a misunderstanding at my end?

I can now get the MTKeyValuesHeader tag working by

(a) adding an $i++ before the end of the loop at line 115 and

(b) replacing the "!defined" clause in line 111 with 0 (false).

However, making the footer tag work looks like I would actually have to know what I was doing, so it will have to wait until tomorrow...

The good news is that just adding an "$i++;" line before the end of the loop (a new line 115 in this version) fixes both problems.

The following hack in keyvalues.pm fixed the extra delimiter:
add this line: $value = substr($value,1);
after this line: if ($value eq $delimiter) {

I think the KeyValue Plugin is great. I had no problem copying it into my mt install.

I do however have a question about the MTKeyValuesStripped tag. You see I'm running a news and events Web site. And it was my intention to use key/value pairs to rank certain articles as more important than others. I was able to do this by placeing a key/value pair in the extended entry field, TopNews=T. However I still want to use this field for extended entries. I was hoping that the MTKeyValuesStripped tag would allow me to strip the key/value pair when I displayed the entry on an archive page.

However on my archive page, the key/value pair still shows up. Did I misunderstand the purpose of the MTKeyValuesStripped tag?

Thanks for your help.

By enclosing my Extended entry data with a MTKeyValues tag, it strips out the key-values pair, but how do I do that for the bodies? does this depend on the archive type, i.e. will it work on indexes?
thanks.