Getting this error when I activate a feature that has a text format associated with it:

Notice: Undefined property: stdClass::$format in filter_format_save() (line 204 of /var/aegir/platforms/nexus-6.1.0.0/modules/filter/filter.module).
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'format' cannot be null: INSERT INTO {filter_format} (format, name, cache, status, weight) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4); Array ( [:db_insert_placeholder_0] => [:db_insert_placeholder_1] => Blog Post [:db_insert_placeholder_2] => 1 [:db_insert_placeholder_3] => 1 [:db_insert_placeholder_4] => 0 ) in filter_format_save() (line 211 of /var/aegir/platforms/nexus-6.1.0.0/modules/filter/filter.module).

Comments

enikola’s picture

enikola commented

sub

knaffles’s picture

knaffles commented

I got the same thing today. I hacked [featurename].features.filter.inc to add a 'format' item to the exported format array and that cleared the error.

ryan.armstrong’s picture

ryan.armstrong commented

mag3000: Sorry this is likely a newbie question, but could you elaborate on that? What exactly did you add to the .inc file?

knaffles’s picture

knaffles commented

ryan.armstrong: Well, I'm also a total newbie, so don't follow my example. But anyway, when you create the feature and then unpack it, you should find a file called [yourfeaturename].features.filter.inc. In there, you'll probably see a snippet that looks something like this:

  // Exported format: WYSIWYG
  $formats['WYSIWYG'] = array(
    'name' => 'WYSIWYG',
    'cache' => '1',
  [etc...]

I added a line defining the "format" array item, which is basically the machine name of your text format:

  // Exported format: WYSIWYG
  $formats['WYSIWYG'] = array(
    'format' => 'wysiwyg',
    'name' => 'WYSIWYG',
    'cache' => '1',
  [etc...]

That took care of the error message. Obviously, this is not a patch to the module itself, just the .inc that it generates.

ryan.armstrong’s picture

ryan.armstrong commented

Ahh gotcha ok. Thank you for the example, I tried that in my feature and it fixed my issue as well. Thanks!

mpotter’s picture

mpotter commented
Status: Active » Closed (won't fix)

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

joachim namyslo’s picture

joachim namyslo
Primary language German
Location Kulmbach 🇩🇪 🇪🇺
commented
Issue summary: View changes

There is no problem to reproduce this

just install drupal 7.36
drush enable -y harmony_core just to get some panopoly forign modules activated
take your install script

PANOPOLY_MODULES="panopoly_admin panopoly_core panopoly_images panopoly_magic panopoly_theme panopoly_users panopoly_widgets panopoly_pages panopoly_search panopoly_wysiwyg"
for module in $PANOPOLY_MODULES; do
drush dl -y $module --destination=sites/all/modules/panopoly
if test -e sites/all/modules/panopoly/$module/$module.make; then
drush make --no-core -y sites/all/modules/panopoly/$module/$module.make;
fi
done
drush en -y $PANOPOLY_MODULES

then go to the module page disable panopoöy_wysiwyg uninstall it and try to reenable

that should produce the error message above.