Hi all,
When enabling a Feature which contains exported Stylizer styles, the install fails with above mentioned error. Perhaps this is a Features issue but I thought it might be wise to check here first.
Looking forward to any suggestions or thoughts!
Comments
Comment #1
merlinofchaos commentedHmm. The stylizer class is in stylizer.inc; anything invoking it *should* be adding that file. Can you paste the full error message? Need to know where this error is happening.
Comment #2
alfthecat commentedHi Merlin,
Thanks and hereby some added info. The feature is part of an installation profile I deploy through Aegir, so the first part is an output from Aegir as it failed to verify the platform. The second part is info from a WSOD that happens when I install the feature manually on a pre-existing site.
AEGIR INSTALL ERROR
ON MANUAL INSTALL OF FEATURE (WSOD)
Where line 18 of the features.inc contains:
}
elseif ($module == "stylizer" && $api == "") {
return array("version" => );
}
}
Looking very much forward to your thoughts! Thanks.
Comment #3
alfthecat commented*nudging* this a bit, curious to know if anyone has suggestions...
Comment #4
merlinofchaos commentedOk, I seem to recall that features and stylizer were broken together because stylizer did not define an 'api' as part of its export. Which CTools thinks is ok, and features does not. The latest version of CTools -dev does define an 'api' for stylizer, so that feature probably needs to be rebuilt from the source, using the latest CTools -dev.
That may fix the class problem too, but I'm not sure.
/var/aegir/.drush/provision/platform/drupal/packages.inc, line 96What's on that line?
Comment #5
alfthecat commentedThanks Merlin,
On line 96 is
// Handle PHP constants
if (defined($value)) {
$value = constant($value);
}
But I think it's not related, just an output from drush/aegir due to the stylizer error. I'm gonna use the dev version of ctools and my guess is that the line 96 error will go away when the stylizer export is accepted by features.
Again, many thanks!
Comment #6
Letharion commentedDue to the lack of activity I take it this has indeed been fixed.
Comment #7
alfthecat commentedHI Letharion,
The issue is not fixed yet, I've rebuilt the feature with the dev release of Ctools but I'm still out of luck :)
Comment #8
Letharion commented@merlinofchaos: Are there any more technical details you could provide regarding the api you mention in #4. After you've commented, I'll move this over to Features, for a comment from them.
Comment #9
alfthecat commentedI've been gathering my thoughts and inspected all my features to see if some variable got smuggled in that perhaps messes things up a bit. I couldn't find anything, but I was wondering if another issue with Panels is related.
Mainly:
#372745: Invalid display id. on Panel-pages content page. is marked fixed but I still have the issue, it's posted here: #991358: Invalid pane id when title is not overridden
Also, but this may be by design, I am often running into trouble with panels_everywhere site templates. I export them into features and they conflict amongst each other due to the fact that the same ID's are used. I have to remember to enable all features that have site templates when I develop new stuff. Again, this probably is by design but all my problems seem to boil down to ID's. Hence I thought it might be helpful information to add here. It's maybe a silly suggestion but I was thinking along the lines of uuid_features integration of some kind, so pane ID's and panels / site template variants can be assigned unique identifiers.
Don't know if this helps, but hope so :)
Comment #10
merlinofchaos commentedWith variants, it is unfortunately the case that the automaticaly generated variant IDs will conflict if you export them without changing them.
The workaround for this situation: Export the one you want and then change the ID manually in the export to something descriptive. Now import that, and remove the original. Make sure it is ordered correctly. Now when you featurize that variant, it will be fine.
Comment #11
alfthecat commented@merlinofchaos thanks for that tip! That will help big time.
Comment #12
japerryClosing this issue as outdated as Drupal 6 ctools is not supported. If this issue is relevant for Drupal 7, feel free to re-open and mark for Drupal 7 (or 8)