We're migrating from Panopoly 1.17 to 1.21 and panopoly_pages_update_7101 is giving us a minor headache. Even though the Features revert of node_info is in place in the update hook the node types aren't being recognized.

I was not able to produce this when upgrading the database to the new code base outside of Aegir.

The platform migration is failing and we're getting something like this:

Executing panopoly_pages_update_7101
Undefined index: create panopoly_landing_page content user.module:3152
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'module' cannot be null
Performed update: panopoly_pages_update_7101

I pinged dsnopek in IRC and the issue got fixed up by including node_types_rebuild(). So it's some kind of cache gooberness. Patch incoming to include it to the upgrade hook, for any others who might have this issue.

CommentFileSizeAuthor
#1 sql_integrity-2500351-1.patch523 bytesmglaman
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mglaman’s picture

Assigned: mglaman » Unassigned
Status: Active » Needs review
FileSize
523 bytes

Here is a patch to fix up that issue!

dsnopek’s picture

Status: Needs review » Fixed

Committed, thanks! :-)

  • dsnopek committed 9d337ad on
    Update Panopoly Pages for Issue #2500351 by mglaman: SQL Integrity...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

tomotomo’s picture

Still getting this with a version with that patch applied:

SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'module' cannot be null                                                                         [error]
Performed update: panopoly_pages_update_7101                                                                                                                 [ok]