Veritaserum

Image description template has definitely gone south, but I love this little plugin. It has a great future in protecting the innocent downloader. It also helps you properly attribute photographers. I added a bunch of functionality to my sites using MMWW, and I write data to my own custom xmp name spaces (created with exiftool). This new xmp namespace stores all of my Flickr Creative Commons license fingerprints and valuable semantic text.

But the template mapping… When I find a solution, I will share asap as a new Github fork of MMWW. Till then, one can only hope that the OllieJones, whom I believe does not get enough praise for his efforts, will make a fix and post the update. BTY, thanks Ollie for all of the hours that went into making this plugin, and we all hope you are well.
Remember, for those who are interested, MMWW has a Github you can fork.

Some useful stuff I do with this plugin:
Firstly, I download from Flickr Commons for most of my posts. I create a file hash of the download, and archive it as a sidecar to the original photo.
Then I retrieve all of the meta via Flickr API (python) and store it in a sqlite. I write the meta to a csv (Python) formatted for exiftool, then let exiftool batch write the meta to the cc images (custom namespace I named FOG). I sometimes populate some IPTC, Dublin, CC, etc.

THEN THE GOOD PART MMWW. I Retrieve the meta on upload to Word-d-Press -using MMWW modded – and with a theme properly configured, I attribute the photo’s author, map tags, map hierarchal categories, put in the photo authors original description, map ALT text, create a custom attachment.php, etc…
Edit the descriptions to your liking and bingo, instant topics, awsome seo content, and a body of “fingerprint” meta additionally containing the original file download hash.
Much of this to keep myself out of small claims court over perfectly legal CC use…
YES, I said COURT! There is a growing branch of organized crime that preys on the innocent CC down-loader by scamming the license FROM: normal CC By- images TO: All Rights Reserved, contesting at unscrupulous agencies… Then these bums crawl the web for the old CC, find innocent users, raise hell with you, troll your site, threaten law suite, and believe me, they WILL ‘try’ extort large settlements.
Always download originals with all EXIF embedded and put them under lock and key (create a file validity hash).

This is the meta I use with MMWW (wth small mod of some retrieval arrays)
MMWW
xmp.php
//start FOG MODS
array(‘xmp:rating’, ‘//xmp:Rating’),
array(‘xmp:label’, ‘//@xmp:Label’),
// XMP Rights
array(‘xmprights:marked’, ‘//xmpRights:Marked’),
array(‘xmprights:webstatement’, ‘//xmpRights:WebStatement’),
array(‘xmprights:usageterms’, ‘//xmpRights:UsageTerms’),

// Dublin
array(‘dc:creator’, ‘//dc:creator’),
array(‘dc:creator’, ‘//dc:creator’),
array(‘dc:subject’, ‘//dc:subject’),
array(‘dc:rights’, ‘//dc:rights’),
array(‘dc:title’, ‘//dc:title’),
array(‘dc:description’, ‘//dc:description’),
array(‘@dc:format’, ‘//@dc:format’),
array(‘dc:format’, ‘//dc:format’),

// XMP
array(‘xmp:createdate’, ‘//xmp:CreateDate’),
array(‘xmp:modifydate’, ‘//xmp:ModifyDate’),

//FOG
array(‘fog:orgfilehash’,’//SHA-256 hash’)
array(‘fog:attribution_url’,’//FOG:attribution_url’),
array(‘fog:description’,’//FOG:description’),
array(‘fog:license’,’//FOG:license’),
array(‘fog:location’,’//FOG:location’),
array(‘fog:photo_id’,’//FOG:photo_id’),
array(‘fog:realname’,’//FOG:realname’),
array(‘fog:tags’,’//dc:subject/rdf:Bag/rdf:li’),
array(‘fog:title’,’//FOG:title’),
array(‘fog:url’,’//FOG:url’),
array(‘fog:username’,’//FOG:username’),
array(‘fog:user_url’,’//FOG:user_url’),
//creativecommons
array(‘cc:attributionname’,’//cc:attributionname’),
array(‘cc:attributionurl’,’//cc:attributionurl’),
array(‘cc:license’,’//cc:license’),
array(‘cc:morepermissions’,’//cc:morepermissions’),
array(‘cc:deprecatedon’,’//cc:deprecatedon’),
array(‘cc:jurisdiction’,’//cc:jurisdiction’),
array(‘cc:legalcode’,’//cc:legalcode’),
array(‘cc:license’,’//cc:license’),
array(‘cc:permits’,’//cc:permits’),
array(‘cc:prohibits’,’//cc:prohibits’),
array(‘cc:requires’,’//cc:requires’),
array(‘cc:useguidelines’,’//cc:useguidelines’)
);
//end FOG

I am using the plugin Amazon Link Engine (see GeoRiot) in combination with Amazon Auto Links PRO (1hellovea-piece-ocode) and it actually Works Awsome!
GeoRiot recommended Amazon Auto Links Pro to me. The two systems are compatible, and a very good solution to localization.

Elan you were a over the top to say the least, and that kind of behavior, although it does gets attention, it is a negative distraction. That being said, I am having the same problem and boy did my search reveal a rats nest, but your post…made me think.
I will rephrase your inflammatory lecture for you, since your methods failed to work for most.

a. You are saying that ‘core’ simple things like TinyMCE not working properly is very bad for WP in general -I agree.

b. You have tested on your 3 systems and used some alternate code from TinyMCE that improved your system -WOW That is a contribution to WP users -Good.

c. You are obviously a ‘smart’ but wordy non-programmer who is seeking solution for a program. We can all see that this is frustrating to you to no end -RIGHT? Then just say so and don’t beat us all up.

I am being a bit like Dr. Phill here I apologize. The other posters need to read around the “hype” and emotionalism of Elan Drydenhall and see the facts imbedded between the lines, and then move on if they cannot cope or contribute to a solution. Please don’t comment on the hyperbola, it just generates more of the same and from far worse than the Elan Drydenhall types. Instead contribute a potential solution. I believe that the Elans of the world are canaries in the mine.

Now for my contribution:
I am using WordPress 3.3.1 Graphene with 7 Widgets.
I believe that the idea of a java script conflict in the load order may be correct. My stock TinyMCE editor is acting strangely as compared to the past, and I am unsure exactly when it changed. It could be do to a plugin, could it?.
In the body I am using WordPress SEO by Yoast, Graphene post-specific options, Keyword Density Checker, Background Manager, In the Right sidebar: Zemantia and Inbound Writer.
I discovered with Firebug, that in the post edit page, TinyMCE is loaded at the bottom of the page. Is that correct? It seems strange. I activated the plugin Ultimate TinyMCE, one of my favorites, and there was no change to the stuttering slowness of the keyboard cursor.
I admit that I don’t know what is going on here, but I believe that the right approach is to get into the php and experiment with the load order. Is this the right approavh? Does anybody know how to do that without breaking an otherwise working post admin page? I cannot afford to loose time by making a mess out of my WP server.
O’ by the way, I also went over to http://www.tinymce.com/tryit/full.php and the TinyMCE editor works perfectly in Firefox 4-9. So I can confirmed that Drydenhall at least had that right. It’s gotta be the implementation of the editor in WP, and it probably has a simple solution.
If anyone can help, please just help and don’t let the inflammatory speech of others stop you from taking a logical approach to a problem that is now affecting the WP community at large, and I must add, pay particular attention to the canaries -OK?