How to handle this replication scenario | Community
Skip to main content
LinearGradient
LinearGradient
Level 6
October 16, 2015
Solved

How to handle this replication scenario

  • October 16, 2015
  • 3 replies
  • 838 views

Hi,

Let's pretend an author deletes a page from a web site but does not want to immediately publish (deactivate) the deleted page from the publisher instance. After some more changes he finally decides to publish his changes.

How can the backend code deactivate the deleted pages, now that their respective nodes are deleted from the repository?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

Nothing out of the box and you can implement at project level by making use of listener.  You have to design & implement an concepts like Trash OR recycle.  

3 replies

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Nothing out of the box and you can implement at project level by making use of listener.  You have to design & implement an concepts like Trash OR recycle.  

LinearGradient
LinearGradientAuthor
Level 6
October 16, 2015

Sham HC wrote...

Nothing out of the box and you can implement at project level by making use of listener.  You have to design & implement an concepts like Trash OR recycle.  

 

How does Touch UI handle this scenario? In the following screen:

[img]Screen Shot 2014-07-25 at 1.47.47 am.png[/img]

What happens when the user deletes the page? Is it also immediately deactivated?

Sham_HC
Sham_HC
Level 10
October 16, 2015

LinearGradient wrote...


What happens when the user deletes the page? Is it also immediately deactivated?

 

yes will deactivate

Terms & ConditionsAccessibility statement

Loading footer...