Closed (fixed)
Project:
Panelizer (obsolete)
Version:
7.x-3.x-dev
Component:
Other module integration
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Jun 2014 at 21:24 UTC
Updated:
28 May 2020 at 04:07 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dstolComment #2
damienmckennaDid you test it with *just* PanelizerEntityDefault.class.php?
Comment #3
dstolShould have done some due diligence there. Tested with this patch, without fatals.
Comment #5
damienmckennaWeird that it didn't like your patch?
Comment #6
damienmckenna@dstol: Any updates? Thanks.
Comment #7
dstolWe've been running this patch in production for a little over a month. Haven't noticed any regressions and certainly haven't had any fatals since we patched. Seems like it's probably RTBC, but I'll leave it up to you.
Comment #8
damienmckennaSounds good. Committed!
Comment #11
denix commentedDear all,
unfortunately the error is still there. I could reproduce it simply having "file_entity" installed in /all/modules/contrib and "panelizer" in /default/modules/contrib.
Moving "panelizer" in /all/modules/contrib fixed the issue.
Thanks
Comment #12
dasginganinjaI can also echo the results from denix in my installation, albeit this is a multi-site installation.
Comment #13
damienmckennaI highly recommend always having your contrib modules installed in sites/all instead of a per-hostname directory.
Comment #14
denix commentedHi @DamienMcKenna, although the recommendation is a good one, unfortunately it is not always possible i.e. a subsite use a module that you do not want to have installed for other entities of your farm. But yes, you are right.
Comment #15
joseph.olstadI just hit this , can we please get a tagged release that contains this fix?