Reset the pw_id value from the session variable

Options
We have a case where the client wants to assign a variable wrapper to a teamraiser donation page. However, all other pages in that session should maintain their assigned wrappers.

We set the wrapper with a url parameter: /site/TR?pg=entry&fr_id=xxxx&pw_id=AAAA. However, this wrapper id is set in the session and all subsequent pages have this wrapper set. Is there a way to reset the system session variable for the page wrapper, so all subsequent pages use the wrapper assigned to them? We tried [[U0:pw_id=]], but that doesn't seem to work.
Tagged:

Comments

  • Curious to know, if we may backtrack to see whether what they might want to achieve can be accomplished through alternatives not necessarily by using of that pw_id parameter.


    Thus you might want to revisit the following questions:
    • What does "use wrapper assigned for subsequent pages" mean ?  Are you classifying / targeting the different page types (i.e. donation page, registration page) to be wrapped on different wrappers per their specifc page types category? i.e. all the donation pages would use wrapper A while registration page would use wrapper B?  Or is this more of non page-type specific? (i.e. a donation page could use wrapper A, while another donation page could use wrapper B -- but they are all still categorically donation page)
      • Because (especially if this is the former that you are targetting page type) -- you might not need to have them put in different wrappers, but rather tap into the use of S tag conditional checking for page type value through [[S4]] tag and that conditional could be put within the same wrapper. You can use that targeting/conditionalizing for various purposes (governing the look and feel/rendering), or even put different snippets (tracking snippets that need to work only when one is currently on that page of that targetted type)

         
    • What is the main reason that they want to use different wrappers? In most cases, this thing could be achieved by using the S-tag conditional to render things differently yet still use the same wrapper as opposed to having different wrappers for every little thing aside that they high maintenance, those wrappers are driven by their associated security categories -- you either have to set different security categories OR manually set pagewrapper overrides from the backend setting/property of each of this components you want it to render differently and individually.  
      • Of course you could still use the &pw_id=  if they are of the same categories, but that would mean you need to programatically target/append the pw_id for each of the pages that need to be having different wrapper (provided all of those subsequent pages are of the same security categories)  The wrapper will change every time you define that pw_id in the URL (cannot be set through U0 since this is not session variable) on the destination link that gets called by the browser to be the current destination/location to go.  But you are not always going to have that flexibility where you could build href links hence you need to inject that appended parameter sometimes programatically through javascript, or set override manually from the backend administration -- thus the potential high maintenance and laborious efforts.
    Just a thought, let us know.


    regards,

    Daniel


     

    Elizabeth Makayed:

    We have a case where the client wants to assign a variable wrapper to a teamraiser donation page. However, all other pages in that session should maintain their assigned wrappers.

    We set the wrapper with a url parameter: /site/TR?pg=entry&fr_id=xxxx&pw_id=AAAA. However, this wrapper id is set in the session and all subsequent pages have this wrapper set. Is there a way to reset the system session variable for the page wrapper, so all subsequent pages use the wrapper assigned to them? We tried [[U0:pw_id=]], but that doesn't seem to work.

     

  • Daniel,


    Our use-case was that the client has multiple wrappers with completely different design and needed to show both based on where the users came from. :-( If they came from a specific Teamraiser event then we would set a wrapper with a specific ID (pw_id in the URL), however, if they browsed to the from naturally (page without pw_id) we needed to render a completely different design, that is native wrapper. We also needed this as new wrappers were created as part of the redesign. Unfortunately, nothing but the pw_id option was viable.

Categories