I had a problem with ctools page manager reading a page imported via a feature after cache was cleared: ctools failed to read the schema (panels_layout, page_manager_pages) from code AFTER the menu cache was cleared (by Drush, by Devel rebuild menus etc).

At first I explicitly added the schema in ctools/includes/export.inc, which "fixed" the problem by ensuring they were read #1264890: menu_rebuild destabilizes schema for backup_migrate and ctools

Then I rebuilt the feature, removing all dependencies (Panels, Features etc) except the ctools page, and Features auto-detected and added Ctools as a dependency.

Now the schema are read properly, but I have no clue as to why...

Comments

decibel.places’s picture

decibel.places commented
Title: dependencies can break schema in ctools page manager » Feature dependencies can break schema in ctools page manager
decibel.places’s picture

decibel.places commented

I thought I had it stabilized, but with the page and ctools dependencies the page manager page would lose its variant info after clearing menu cache, therefore no path, no content etc.

The variant would be restored by visiting the main admin page.

The solution

I rebuilt the feature with JUST the page manager page. But it did not stabilize until I deleted the page that was overriding the code in the Feature, I think my coworker was editing the page after the feature was enabled. Seems to be staying stable now, even after menu cache is cleared.

How I got knighted:

My coworker ditched the panels page in favor of a node template, the way the team had been creating pages before I joined them. I told him I thought using a Feature is "more Drupal-ly" and portable across DEV STG & PROD. He said if I showed him the Feature stable he would knight me "Randall Goya, Sir Drupal of Drupingtown, protector of all things Drupal-ly" - guess who's buying me Drupal-ly Burger King (without the meat)....

I created a cartoon for "Sir Drupal..." http://netsperience.org/content/blog/%E2%80%98sir-drupal-drupingtown-pro...

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Postponed (maintainer needs more info)

@decibel.places, is everything set now or do you still need assistance?

decibel.places’s picture

decibel.places commented

Danielle,

I got the Feature working as reported in my last post ("The solution"), but Panels are still problematic in the Features project.

In fact, in the process of exporting some complex configurations from local dev to staging, I had to export/import these items outside the Features and/or configure them manually:

CCK content types (complicated ones with filefield_sources and computed_field fields)
Wysiwyg profiles
Enabling filters on input formats (if using Strongarm, once enabled settings are already there)
set Admin theme

Features works very nicely on:

Views 3.x
Menus
Imagecache
Enabling modules, even custom ones
Rootcandy theme settings (but not setting it as admin theme)

finex’s picture

finex commented

About computed fields support, would be better to open a separate feature request against features module or computed fields module?

Thanks

decibel.places’s picture

decibel.places commented

@FiNeX

Are you having a problem with computed fields or features? what kind of "support" do you want? I used computed fields in Views in a Feature without any trouble.

Features does not always export CCK content types well, you may need to export them separately. But that is a larger issue than computed fields support.

If it's an issue with Computed Fields, it goes to that queue; if it's a Features issue, it goes to that queue.

finex’s picture

finex commented

Well, I've generated a feature with some views and a content type with a computed field, but the field was not completely exported (some info, like the computed field value was not considered).

I'll try to export the computed field alone in order to test if it goes ok. I'll let you know. Thanks

decibel.places’s picture

decibel.places commented

@FiNeX

export the content type using "content copy" in D6 or "bundle copy" in D7

there's an issue posted somewhere requesting similar functionality wrapped in Features, if you want to try to help

however, this is off topic for this thread so if you need further help (after searching for an answer) post to another existing or new issue

finex’s picture

finex commented

@decibel.places: I simply wanted to confirm what yo've wrote on comment #4 about a "problematic" generation of features when you have complicated cck field structure, in my case with computed field (like you've reported before). I'm already looking for a more pertinent issue about the compatibility between features and computed fields and/or creating a new one, but I've to do some further tests in order to identify a reproducible pattern.

Anyway thanks :-)

mpotter’s picture

mpotter commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.