Closed (fixed)
Project:
Panelizer (obsolete)
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Jun 2012 at 11:16 UTC
Updated:
12 Feb 2013 at 00:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
merlinofchaos commentedI'm sorry, I really don't understand what you're saying. You're going to need to try to be a little more clear.
Comment #2
roynilanjan commentedOk good
Node-Panelizer is a variant in Default node-view panel-page right? if I write a selection rule there for content type (e.g. only for Article) what should be the expected result? Panelizer should be implemented for nodes of Article content type.
But this selection rule doesn't effect in the out-put always panelizer executed in both the content-type nodes
as I have assigned both Basic page & Article to panelizer from configuration of panelizer in admin.
Please let me know if I'm not clear to explain the problem
Comment #3
merlinofchaos commentedI'm sorry, you really need to provide exact steps. I can't see your screens or guess at your implementations, and you're using vague language and leaving out details. Maybe screenshots of your node_view content would help.
Comment #4
roynilanjan commentedPlease review the screen-shots
1. for panel -page configuration node-template(Node-Template.png) where a selection rule is written only for Editorial page content-type
2. Panelizer configuration where both the content-type(Editorial Page & News Article are assigned panelizer conf.png)
3. Now please look into News article content (News Article content type)here still panelizer is coming although I have made a selection( Node-Template.png)
So my selection rule I assume not working when panelizer is a variant in a panel page.
Please let me correct I'm missing something in my implementation
Comment #5
merlinofchaos commentedOkay, yes, I see that this is a bug.
This doesn't strike me as critical:
1) Almost nobody will configure this.
2) The workaround is to not create this conflicting configuration.
3) There's no crash here.
Comment #6
roynilanjan commentedOk I'll not configure in this way,
But one thing please tell me how should I use panelizer variant in a panel page? just give an example
Comment #7
merlinofchaos commentedIt's not something you normally need to use -- Panelizer places it automatically where it needs to.
You might place it for yourself when you want to display a panelized page in a different location. For example, say you've got a 'show' page and a related 'cast' page, you might set node/%node/cast to load an entity from a reference on %node and display that panelized entity. Otherwise, you should leave these alone and let Panelizer deal with them.
Comment #8
renaudcuny commentedHi guys,
Just find your topic by trying to achieve something similar.
Let's imagine a site with a normal version VS a mobile version.
Normal version would use Panelizer to build up complicated pages.
Mobile version uses a light theme and just some light content on every page, the node body, a header and a footer, basta.
Great solution would be to use Domain Access + Domain Ctools, then create a selection criteria on panelizer variant: "use only for domain X (normal version)".
In that case it would really make sense to be able to get the selection criteria working, don't you think so :)?
Comment #9
merlinofchaos commentedThis appears to have been fixed in the 7.x-3.x branch, but not in 7.x-2.x
However, the 2.x branch isn't really supported any more, and simply is there go give people who have code relying on the 2.x behavior a stopping point, so I'm not going to backport the fix.