Assigning a Publication Package to just one page

ChrisJ

unread,

Jul 17, 2012, 10:29:26 AM7/17/12

to reddot-c...@googlegroups.com

Hi I've already posted this on SolutionExchange, hope it's not annoying for you to put it here too, not sure if people read that to be honest...

Anyway,

Does anyone know of a good way to assign a Publication Package to just one page on a list or is this impossible?

The problem I'm trying to solve is to have one page, a payment form, published as secure but all other pages on the list publishing as normal. So if I have this setup:

[Section contents page]

- [About Section]

- [FAQs on Seciton]

- [Another normal page]

- [Payment Form]

I'd just like [Payment Form] to be published securly and all the other insecurely.

At the moment the only way I can do this is to add an extra layer to give me a new sub-list that I can attach the secure PubPackage and the play with adding redirects and other things, buts it's really ugly.

Cheers!

Jian Huang

unread,

Jul 17, 2012, 1:53:52 PM7/17/12

to reddot-c...@googlegroups.com

Hi Chris,

Having an extra layer is probably the easiest.

Alternatively, you can have those pages connected to a page with list that is within con_body of the main page.

Of course, then those sub pages would not be in navigation manager, and you would need navigation emulation code found below for those pages to display navigation properly.

http://simplyreddot.blogspot.com/2011/12/navigation-emulation.html

ChrisJ

unread,

Jul 18, 2012, 11:11:43 AM7/18/12

to RedDot CMS Users

Thanks Jian, sounds like there isn't a magic bullet here... I'll have
a think about the list-in-container idea, that might work, but would
be a shame to lose this page from nav.

Many thanks again,
Chris!

Message has been deleted

Chris Jamieson

unread,

Jul 20, 2012, 11:14:52 AM7/20/12

to reddot-c...@googlegroups.com

That's a brilliant solution Jian - you're the man!

We've got some mete-refresh content classes in our system for doing stuff like this, but yours is really neat with the lists on that page and the Nav emulation to show the correct menu (could be a little bit of work to replace our current nav-man code, but would be possible with a bit of moving around).

Many thanks for taking the time to share your idea, it's a cracker!

Cheers,

Chris.

On 18 July 2012 19:29, Jian Huang <jhuangs...@gmail.com> wrote:

Hi Chris,

I have a solution that would would for you.

Create a content class that has code like this

<html>
<head>
<title></title>
<meta http-equiv="refresh" content="0;URL='<%lst_navigation%>'">

</head>
<body>
</body>
</html>

Note: you can add in more HTML later to make it SmartEdit friend. Ensure lst_navigation has insert path and file name only enabled. Make sure this content class is a master page.

Now, create and connect a page instance of this content class to wherever lst_navigation you can. Then, under the lst_navigation of the previously created page, create and connect the page you really want, and attach the publication package you want.

Now all your pages are part of navigation manager. However, when you prefer your secured page, you will see a navigation page a level above "sticking out", which is the redirect page. I can tell all the complicated ways to code navigation manager to do conditional level skips and everything but that's not my style. My goal is to provide the easiest and most maintainable solution. So here it is.

In the content class of your secure page (I hope the secure page is the last page in the SmartTree branch, and it has it's own content class)

Use this code for your left navigation

<%!! Navigation:OutputArea(Left Navigation, Bool:False, Context:CurrentMasterPage.MainLink.OwnerPage.Id, Bool:False) !!%>

This will make the left navigation display as if it is called and rendered from the secured page's parent page. Of course, when web users click on the secured page's parent page URL from the left navigation, they will be redirected to the right URL of the secured page.

I hope I made sense. I typed this in a rush.

Best,

-Jian

--
You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/reddot-cms-users/-/rRl3wczrg94J.

To post to this group, send email to reddot-c...@googlegroups.com.
To unsubscribe from this group, send email to reddot-cms-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.

Reply all

Reply to author

Forward