Closed (fixed)
Project:
Panelizer (obsolete)
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Sep 2012 at 23:52 UTC
Updated:
27 Feb 2013 at 20:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
socialnicheguru commentedchanged title
Comment #2
merlinofchaos commentedAre you sure that 'default' was actually different than 'full' at that time?
Comment #3
rancas commentedThe same for me using 7.x-3.0-rc1+6-dev on panoply distribution.
Comment #4
merlinofchaos commentedIndeed, the old panelizer object was still being found and used. I committed and pushed a fix.
Comment #5
astutonetI have this issue too, using 7.x-3.0+0-dev (2013-jan-30) version.
In my case, I create a teaser panelizer. When I try to disable or remove it, no chance.
The teaser panelized is showed with the same layout, as if nothing had happened.
Even with the settings disabled in the teaser display, the teasers that were worked by Panelizer are displayed with the settings that are disabled.
I can say this with certainty because I have other teasers that were not affected by Panelizer, which are displayed side by side on the homepage.
We needs to have an option to remove changes that are no longer desired made by Panelizer. This also can be understood as a feature request.
Edit:
The first code block below is responsible for displaying teasers which were not treated by Panelizer.
The second block of code is responsible for displaying teasers that were treated by Panelizer but are disabled.
Comment #6
merlinofchaos commentedAhh, that same check needs to also go in the entity view alter. I should've checked that one too. :(
This patch should fix it. Can you verify it for me?
Comment #7
astutonetVerified. The patch returns an error, as in the image.
Tks.
Comment #8
astutonetHi @merlinofchaos,
I forgot to change the status. Can you help me?
Comment #9
merlinofchaos commentedAhh, just a missing parens. I'd hoped whoever tested this would have enough PHP knowledge to fix small things like that, but that's okay, Here's an update.
Also, when a patch fails testing, 'needs work' is an appropriate status.
Comment #10
merlinofchaos commentedLast patch also doesn't work. Try this one.
Comment #11
astutonetHi Merlin.
The patch in #10 worked perfectly.
About the lack of parenthesis, I apologize, it was a lack of attention on my part.
Sorry & Thank you.
Comment #12
merlinofchaos commentedCommitted and pushed!