Disassociate TeamRaiser from parent Blueprint

Mark Kindy · November 2015

So, I have ten TeamRaisers I'm managing, all built on a single Blueprint. There is some independent content on some of the pages, which is pulled by [[S51]] tags referencing PageBuilder pages by fr_id; however, one of the events is turning out to require some changes we didn't anticipate -- easy enough to modify on their own, but the other 9 events are generally being updated with content via the Blueprint and pushes. With some of the content in question being content the 10th TeamRaiser has customized independent of the others, this means pushes are overwriting those changes and I have to go back through and replace those changes.

Obviously, some part of Luminate knows that the 10th TeamRaiser is associated with the Blueprint, and that information can surely be overwritten or deleted -- but is that even accessible anywhere in TeamRaiser management?

Daniel Hartanto · December 2015

Don't think we could disassociate a child Teamraiser from its BP parent -- but would be interested to know myself.

That aside, in terms of preventing a push from overwriting that particular Teamraiser page content. Have you given a thought about potentially using a "Custom Page" (#12. Customize Page and choose "Custom Pages" tab within your Teamraiser > Edit) where you can create one on that 10th Teamraiser, and moved the customized content specific to that 10th teamraiser into it.

You can then "embed" the custom pages using jQuery.Load() into a hidden DIV that you could append to that particular teamraiser from the pagewrapper level by (using S334 targetting the fr_id specific conditional). Every custom pages would have an "sid" (a.k.a. "soid" on the backend alongside "pg=informational").

Add on Note: you can't create a custom page on the BP and hope that would get pushed to the children, especially if this is after the fact a.k.a post initial first push, hence create one on that 10th teamraiser child directly.

Doing so, you could still deliberately let them manage their own content (via the EMC), still have the content rendered at the location/page you want that to be and probably worry less about the push going to overwrite the content of that 10th Teamraiser.

regards,

Daniel

Mark Kindy · December 2015

Daniel Hartanto:

You can then "embed" the custom pages using jQuery.Load() into a hidden DIV that you could append to that particular teamraiser from the pagewrapper level...

Yeah, this was what I wound up doing, although using a combination of PageBuilder content instead of a new custom page. Mostly just wondering if there was a more elegant solution, but this will do for now, and isn't producing any noticeable lag on the affected page. Thanks for the input!

Daniel Hartanto · December 2015

btw Mark -- forgot to mention (scattered brain mode always with me) -- one more important tips on jQuery.load of that custom page. You might want to make sure that you load the page without the pagewrapper associated with it through the use of the following parameter &pgwrap=n

Doing so will significantly improve the load performance / webpage in general as those pagewrapper overheads are excluded by that.

p.s. Anytime and you are always welcome ! Always happy to share and help as I got to learn from it as well by replying / participating in the discussion.

EDIT#2 -- was reading your response about embedding the pagebuilder instead of that custom page -- you can do that also, depending on permission / role; on ours we don't give access to staff in general to edit pagebuilders, thus their only option because of this was to use that Custom Page (since also we are using the EMC component (not all org seems to use it -- this is more like a Participant Center dashboard but more for event managers to edit aspects of their events; i.e. contents)

regards,

Daniel

Disassociate TeamRaiser from parent Blueprint

Comments

Categories