I'm building a site which relies heavily on the use of "Remove At" and "Publish At" built-in functionality of Umbraco. On the "frontpage"-node I have a MNTP which is used to render shared content and modules. If I selected a module which has a "Remove At" date set and that date/time is reached, the module-document will be unpublished, but not removed from the MNTP on the frontpage-node.
I'm wondering if there is a more clean way of removing a selected node when it's being unpublished than hooking in to the Document.AfterUnpublish event? Is there any kind of setting that I have missed somewhere? :-)
If anything, I think it would be a neat feature to make the MNTP selected area sync with the published state of a document.
I'm sorry if this has been addressed before or it's already built-in and I have missed it ;-)
This is a good one Bo - I actually think it would be great if there was an "unpublished" and/or "deleted" state for nodes picked with MNTP. Developers like us can handle this but Editors have no clue why their stuff suddenly dissapeared etc.
Thanks! And yes, the Delete event would make sense aswell.
For now, I'm just going to hook up to the document events with a DocumentEventHelper class which contains a RemoveNodeFromMNTP(Document document) method.
If anyone's got a better solution, please let me know :-)
MNTP and Remove At
Hi all,
I'm building a site which relies heavily on the use of "Remove At" and "Publish At" built-in functionality of Umbraco. On the "frontpage"-node I have a MNTP which is used to render shared content and modules. If I selected a module which has a "Remove At" date set and that date/time is reached, the module-document will be unpublished, but not removed from the MNTP on the frontpage-node.
I'm wondering if there is a more clean way of removing a selected node when it's being unpublished than hooking in to the Document.AfterUnpublish event? Is there any kind of setting that I have missed somewhere? :-)
If anything, I think it would be a neat feature to make the MNTP selected area sync with the published state of a document.
I'm sorry if this has been addressed before or it's already built-in and I have missed it ;-)
Thanks in advance.
All the best,
Bo
This is a good one Bo - I actually think it would be great if there was an "unpublished" and/or "deleted" state for nodes picked with MNTP. Developers like us can handle this but Editors have no clue why their stuff suddenly dissapeared etc.
/Chriztian
Hi Chriztian,
Thanks! And yes, the Delete event would make sense aswell.
For now, I'm just going to hook up to the document events with a DocumentEventHelper class which contains a RemoveNodeFromMNTP(Document document) method.
If anyone's got a better solution, please let me know :-)
- Bo
is working on a reply...