Page Wrapper Home Page

Michael Turner

Hi all,


Just hoping someone could let me know how you tell the page wrapper what page to load on launch. I've been looking around the config settings and nothing is jumping out at me. 


Any help would be greatly appreciated!


If I need to give more detail let me know, I'm still pretty new with Luminate.


Thanks!

Jesse Kelsey

Hi Michael,


I might be misunderstanding your question a bit, but it seems like the answer is to think of the process in the reverse order. A page wrapper can be assigned to a page (a PageBuilder page, a donation form, a survey, etc.). So try creating the page first and then assign the page wrapper to it. One quirky thing about Luminate is that assigning the page wrapper sometimes requires clicking the "Finish" button rather than the "Save" button.



 

Jon Reich

Hi Michael, 


If you're referring to the "site default homepage"... which is what loads when you initially go to your Luminate site, that is somthing that Support will have to change for you. Simply submit a ticket such as:

 

Subject:  site default homepage change   We would like our site default changed from "deploymenthome" to [enter new PageBuilder, TR, or external link]

You can set the site default homepage to be either an internal Luminate page... or even to an external site/link. 


Just let me know if I'm misunderstanding your request. 


Thanks!


- Jon

 --

Jon Reich * Partner * Cathexis Partners * jon@cathexispartners.com * p.605.377.8147

Michael Turner

Hi Jesse,


Thanks for the reply!


Ok so what I've got going on is...I've made my page wrapper and I have 2 pages that I'm testing with right now. Both of those have my page wrapper assigned to them and I can see them displaying properly when I click preview from the page builder screen.


I suppose my question is if the site were to go "live" how does the page wrapper know which of those pages would be the "home page" that gets shown when the site loads? Is there a screen somewhere where i can effectively say "when *blank* page wrapper is used load *blank* page first"


I hope that clarifies my question a little more.


Thanks for responding!

Michael Turner

Hi Jon,


That's what I was looking for! Ok so when the time comes I have to open a ticket and have Support manually assign the home page. Got it!


Thanks a lot!

Brian Mucha

The default home page also turns up when login and logout links don't use a NEXTURL parameter, and a few other places. I think cancel on survey's will direct there as well. So pick one that makes sense in lots of situations, because it may pop up unexpectedly.


Like Jesse said, PageWrappers are sorta like stationary, templates or themes on other platforms. It's just the common graphical/header/footer stuff that wraps your actual content. You navigate to pages, the wrapper is just the paint job.


Chat support can also set this in minutes.

Daniel Hartanto

Isn't that "default" pagewrapper (which wrap those built-in Luminate Online pages i.e. Login, User Profile) would always use your "General" Security Category default pagewrapper ? At least that is what my understanding that each LO instance would have a "General" Security Category already so all we need to do is just create a pagewrapper instance and assigned that as your default security category.


PageWrapper goes hand-in-hand with Security Category. When you create a pagewrapper it will ask what Security Category you want that pagewrapper to belong to, and you could also set that newly created pagewrapper to be the default for that Security Category.


Any pagebuilder that you create that belongs to the same category would automatically know to use the default PageWrapper defined above. Otherwise, you could also override what pagewrapper to use other than default (as long as they are within the same security category) for each pagebuilder to use if you opt to do that.


p.s. you can also override PageWrapper on-the-fly through the use of that URL parameter &pw_id=XXXX (XXXX being your wrapper ID); again so long that they are of same security category -- BUT I won't really recommend this option since initiating / overriding that this way would basically override all of those pagebuilders you happened to visit subsequently within the same browser instance until you close that browser; that otherwise might not be your intend here. This is only good for development purpose when you want to see those otherwise live pages within the new pagewrapper that you are developing to replace the existing one in near future.


regards,

Daniel


EDIT ADD ON:


Here's what I did on "customizing" those "default" pages by creating a new pagewrapper set it as default for our "General" security category. You HAVE to set your custom pagewrapper as default for that "General" security category for those "default" pages to pick up your pagewrapper.


Additionally since those default pages are not necessarily mobile-friendly, I actually put a Javascript redirect within our pagewrapper for those hitting our default login page to go to a custom pagebuilder login page WHEN there is no NEXTURL parameter (for some reason there is a quirk preventing consistent experience trying to pass along the NEXTURL parameter into that custom page or something if I recall correctly)


(here's displaying the default content)

http://main.diabetes.org/site/UserLogin?NEXTURL=http://stepout.diabetes.org


(this default page without NEXTURL will redirect to our custom login page)

http://main.diabetes.org/site/UserLogin