i've used Panels Everywhere to deal with "panelizing" paths that come with modules (PrivateMsg, OG, etc). Can you explain the difference/benefit in using your module over Panels Everywhere? Thanks.

Comments

swentel’s picture

swentel commented
Status: Active » Fixed

The key difference is that with Panels Everywhere you override the page template, as where this module takes over the page doing a menu alter. With PE, you override a path by using the selection rules and adding a rule on 'path' and take over the complete page template, whereas this module takes over the page callback and takes control over the $content, not the entire page layout (although, with a good theme you can more or less achieve the same thing because page elements are available on that level as well. It's a different technique. Which one has more benefit, I can't really tell, it depends on the use case I think.

capellic’s picture

capellic
he/him/his
Location Austin, Texas
commented

Thanks for the clarification. Sounds like Page Manger Existing Pages fires off later in the stack? Sounds like Panels Everywhere fires off earlier because of it's ability to control the header and footer of the page as well-- the whole thing. Page Manger Existing Pages doesn't try to control anything outside of $content-- got it. Which is interesting, because we don't use Panels Everywhere to control the header and footer.

Do you know if one method or the other is more efficient in terms of performance? And does that benefit result in any loss of flexibility?

swentel’s picture

swentel commented

I can't really answer on the performance thing as I haven't used PE yet in live projects, however, I think they are both equal on that part - bad or good, I leave that in the middle ;)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.