Vishnu,
I think he was suggesting using the roles to allow for preview, but I'm not sure that will provide the in context approach that I think you are after. I have an alternative suggestion that would work with all out of the box stuff, but might not be the most awesome solution.
Instead of using the web content display, use an Asset Publisher, where you specify the item you want to render (don't do the dynamic option, use the other one .. the name of which escapes me). Then, in your ADT, you can use the JournalArticleLocalService to see if there is a newer (unapporved) version and if there is, and the user has the right role to view it, then render the unapproved version in place of the approved one.
The ADT wouldn't contain any of the "template view" in it, just the logic for the decision of which version to render. Actually, come to think of it, you don't need the Asset Publisher/ADT -- you could introduce the logic into you WCM template in the same fashion
I nice solution might be to try this --
1. In your WCM, detect if the user has the rights to see unapproved content.
2. If they do, give them a toggle to "preview unpublished"
3. By default you render the approved but if they hit that toggle, you re-render with the unapproved one
.. anyway, you can do it by introducing some logic into your template. Not the best practice mind you as templates shouldn't really be "smart", but if you have no other choise, I think that would work.
I think he was suggesting using the roles to allow for preview, but I'm not sure that will provide the in context approach that I think you are after. I have an alternative suggestion that would work with all out of the box stuff, but might not be the most awesome solution.
Instead of using the web content display, use an Asset Publisher, where you specify the item you want to render (don't do the dynamic option, use the other one .. the name of which escapes me). Then, in your ADT, you can use the JournalArticleLocalService to see if there is a newer (unapporved) version and if there is, and the user has the right role to view it, then render the unapproved version in place of the approved one.
The ADT wouldn't contain any of the "template view" in it, just the logic for the decision of which version to render. Actually, come to think of it, you don't need the Asset Publisher/ADT -- you could introduce the logic into you WCM template in the same fashion
I nice solution might be to try this --
1. In your WCM, detect if the user has the rights to see unapproved content.
2. If they do, give them a toggle to "preview unpublished"
3. By default you render the approved but if they hit that toggle, you re-render with the unapproved one
.. anyway, you can do it by introducing some logic into your template. Not the best practice mind you as templates shouldn't really be "smart", but if you have no other choise, I think that would work.
Andrew JardineVishnu,
I think he was suggesting using the roles to allow for preview, but I'm not sure that will provide the in context approach that I think you are after. I have an alternative suggestion that would work with all out of the box stuff, but might not be the most awesome solution.
Instead of using the web content display, use an Asset Publisher, where you specify the item you want to render (don't do the dynamic option, use the other one .. the name of which escapes me). Then, in your ADT, you can use the JournalArticleLocalService to see if there is a newer (unapporved) version and if there is, and the user has the right role to view it, then render the unapproved version in place of the approved one.
The ADT wouldn't contain any of the "template view" in it, just the logic for the decision of which version to render. Actually, come to think of it, you don't need the Asset Publisher/ADT -- you could introduce the logic into you WCM template in the same fashion
I nice solution might be to try this --
1. In your WCM, detect if the user has the rights to see unapproved content.
2. If they do, give them a toggle to "preview unpublished"
3. By default you render the approved but if they hit that toggle, you re-render with the unapproved one
.. anyway, you can do it by introducing some logic into your template. Not the best practice mind you as templates shouldn't really be "smart", but if you have no other choise, I think that would work.
Thank you Andrew. This seems to be an excellent solution. We'll bring it up to the business to get their feedback.
Regards!
Community
Company
Feedback