Skip to main content
7 events
when toggle format what by license comment
Apr 13, 2017 at 12:49 history edited CommunityBot
replaced http://tridion.stackexchange.com/ with https://tridion.stackexchange.com/
Nov 15, 2013 at 4:47 comment added Alvin Reyes A description about the fields automatically being set during publish can help authors if you choose to leave the fields visible. If this wasn't delivery-side (custom) metadata, AppData would be another good place to store "hidden" information. The fields could even be a feature in case authors ever need to override the values.
Nov 14, 2013 at 14:36 comment added Bart Koopman @PauldeMaesschalck Yes for my approach a save is required and thus you must have the Metadata field. As discussed in my second article, you can opt for hiding those fields from your editors through a UI extension like the Tridion FBI extension (as discussed here). If you want to hook into the Publisher process the 'dirty' way, then follow Eric's answer.
Nov 14, 2013 at 14:23 comment added Paul de Maesschalck Bart, Thank you for the quick reply. If I look at the code on GitHub, there still is a .save() present in the code, which means that I need to have the metadata fields already present in the schema. That means that the content managers will see duplicate fields when they re-open the component (Unless I hide them using a GUI extension). Is there no way to hook into the publishing process, at a time when no schema validation is done anymore ? The dirty solution as you call it?
Nov 14, 2013 at 14:08 history edited Bart Koopman CC BY-SA 3.0
added code examples and a link to Eric's answer, plus a direct answer to the question asked.
Nov 14, 2013 at 14:02 history edited Bart Koopman CC BY-SA 3.0
added code examples and a link to Eric's answer
Nov 14, 2013 at 13:56 history answered Bart Koopman CC BY-SA 3.0