Bugzilla – Bug 14847
add parametrized CMS keys output for test server
Last modified: 2009-12-03 15:56:55 UTC
It would be very helpful for Marketing to have a way to quickly see what keys a content block is using. My suggestion is these could be output in some special DOM element, like: <span class="CMSKeys" style="display: none;"> <span class="Position">My Music</span> <span class="Title">MY-MUSIC_OVERVIEW</span> </span> when param 'output_cms_keys' is set to true. This would allow the CMS functional testing can actually crawl MySB.com and verify content is appearing where it's intended to. Secondly, to view within the web UI, marketing could enable the 'visible' flag to produce: <span class="CMSKeys"> <span class="Position">My Music</span> <span class="Title">MY-MUSIC_OVERVIEW</span> </span> which would allow marketing to see the tags in the actual content block. There's really no limit on how this could be implemented, so this is merely my suggestion on how it *could* work. Definitely having the keys someplace in the DOM would make my functional testing MUCH more robust and sophisticated. Having marketing able to spot-check content on the web UI is also a great process improvement over having to bug Michael or Andy to verify. Thoughts?
I just direct to CMS link would be even more helpful. Something like: <span class="CMSKeys"> <span class="Position">My Music</span> <span class="Title">MY-MUSIC_OVERVIEW</span> <span class="CMSLinks"> <a href="http://www.logitechsqueezebox.com/admin/index.php?action=edit&id=24" >Edit Source Content</a> | <a href="http://cms.mysqueezebox.com/index.php/l10ns/view/24/" >View Localizations</a> </span> </span> those links are just examples. I can put together real ones once we get some bandwidth to build out a feature like this -- would be very useful!
This is probably a won'tfix. If anything the CMS will get integrated into the greater GMO CMS.