Using page scope's in "Edit page" window

Does anyone know how to use $page_scope's on the "Edit page" window?

They work fine on the "Preview page" but nothing appears on the "Edit page".

NOTE: I'm outputting the page scope via the fixed-layout.page.xsl.

I understand the edit page is altered from the usual fixed-layout.page.xsl template to enabled editing.

Find more posts tagged with

Comments

Rick Poulin

I'm assuming you added your own custom page scope variable? If so, there's probably a better way to achieve whatever it is you're doing.. But in the worst case, there's a separate "admin" layout file for the edit mode, that you could perhaps modify for this. It's undocumented and unsupported though, so I'd really recommend finding an alternative approach. (specify your scenario if you want suggestions)

Garth McMillan

Yes, it's a custom page scope.

What I am trying to achieve is to have a single component output content onto multiple parts of the page. Think a 3 column layout, the component is in the middle column, but it can optionally add content to the right column as well.

Previously we handled this by adding another component to the right column and referencing the same DCR as the middle column, but this setup has been causing some confusion with users.

I'll check out the "admin" layout file, but I'm open to any other suggestions as well.

Thanks.

Garth McMillan

I've looked at the admin.edit.fixed-layout-page.xsl and can add dummy text to the area I want, however, I can't output any page scope's.

I've tried my custom page scope, as well as some defaults, including the following:

$PAGE_SCOPE[aside_block]
$PAGE_SCOPE[title]
$PAGE_SCOPE[head_injection]
$PAGE_SCOPE[body_injection_bottom]

NOTE: The $PAGE_SCOPE placeholders do get removed, so it looks as though the actual value of the items are null, rather than page scope's not being processed in "Edit".

It seems that no page scope's are available in edit. Do you have any suggestions/alternatives? Would custom page tokens be a better solution?

binding.png

Rick Poulin

It seems that no page scope's are available in edit. Do you have any suggestions/alternatives? Would custom page tokens be a better solution?

Probably, given your lack of success with page scope vars. I had issues when I first tried something similar, but that was back in 6.7 or 7.1 so I wasn't sure if it was still the case. Custom page token should work, or you can always create a RequestContextWrapper and use $CONTEXT{}. Either way is about the same amount of effort, but the latter might be easier to extend later.