Closed (fixed)
Project:
UUID Features Integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Jul 2014 at 11:35 UTC
Updated:
28 Jul 2014 at 15:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
christianadamski commentedFirst issue:
On clearing cache or visiting features: crash with strange erronous DB-query, missing tables names and stuff.
Tracked down:
uuid_panelizer_features_export_render() in uuid_panelizer.features.inc assumes $data containing valid key/UUIDs and goes from there. However, at least for me $data was also keyed by '0'. This empties some variables and causes said useless DB-query.
Solution:
My short-hand version: check for key not empty. Possible better version: check for valid key / UUID
Patch will follow later, see above
Comment #2
christianadamski commentedSame file and funtion:
Export of xxx.features.uuid_panelizer.inc was most times basically empty, but sometimes not.
Tracked down:
The entities loaded by entity_uuid_load(), in the panelizer view-mode "page_manager" did not contain and displays. There are just not there.
Solution:
Use entity_uuid_load() with the reset=true (that's the 4th argument)
Comment #3
christianadamski commentedOk, here's the patch. With theses changes and after cleaning bogus DB-entries I was able to deploy a featured node with a custom panelizer full-page-override.
What is strange:
I get different results depending, if using the UI or drush?
Comment #5
das-peter commentedHi @ChristianAdamski & thanks for the patch.
Yes, the panelizer support was just added about one week ago. So indeed fairly new.
May I ask you which versions of panelizer / panels / ctools you use?
I've tested the feature with the latest dev versions of those modules and it seemed to work quite well.
However, I've just pushed the patch as those changes make sense anyway :)
Comment #6
christianadamski commentedHey @das-peter,
using latest stable OpenAtrium release but panelizer-dev from Jun-30 and UUID_features-dev from Jul-2.
The situation is very specific, as I export a specific node panelized in full page override.
The view modes for content types (default, teaser) worked already, what did not was the "page manager" view mode.
I don't know exactly what that means, I am no panels expert.
Be warned:
There still is the weired fact, that the Features UI now shows all my features lined up fine, while 'drush fl' still shows them overridden and wants to add panelizer-view-mode stuff, that is not necessary for single nodes. These are only required for whole content-types.
I do not know, why frontend and drush differ in behavior here.
Comment #7
das-peter commentedAh okay, I thought it could have been a problem with uuid's.
I don't have a clue why drush would differ from the UI - honestly I didn't test the stuff using drush so far.
However, this seems to be strange since we implement the features hooks and I don't know why they would differ.
But maybe I miss something. I'll try to figure it out.
Very nice, I guess I missed that scenario and was just testing with non full page overrides.
So thanks again for working on this!!