Couldn't see an issue for this problem; if this is a duplicate, sorry!

I'm fairly certain notifications is breaking content import.

I was having issues in importing a content type on a dev box and kept getting an illegal choice. I copied over part of a working export to see if that'd work.

It did; here's the differences

+ 'notifications_node_ui' =>
+ array (
+ 'links' => true,
+ 'form' => false,
+ 'comment' => false,
+ 'block' => false,
+ ),
'old_type' => 'gene',
'orig_type' => '',
'module' => 'node',
@@ -28,27 +35,6 @@
'og_content_type_usage' => 'omitted',
'rdf_schema_class' => '',
'content_profile_use' => 0,
- 'notifications_node_ui' =>
- array (
- 'links' => true,
- 0 => 1,
- 'form' => false,
- 'comment' => false,
- 'teaserlinks' => false,
- 'subform' => false,
- 'block' => false,
- ),
- 'notifications_content_type' =>
- array (
- 'group' => true,
- 'grouptype' => true,
- 'taxonomy' => true,
- 'thread' => true,
- 'nodetype' => true,
- 'author' => true,
- 0 => 1,
- 'typeauthor' => false,
- ),

My guess is it's the 0 => 1 causing the issue since it's there twice (notifications_node_ui and notifications_content_type) and I had two illegal choice warnings.

Comments

jose reyero’s picture

Status: Active » Postponed (maintainer needs more info)

Yes, it looks like it's some notifications_ui value, but I cannot see it in my variables. It may be some left over data there.

Could you edit the content type settings, save, try again and let me know whether that value is gone?

hefox’s picture

Saved and re exporting but still there.

http://drupal.org/node/375200
Looks like it's also happening in other situations, so it may not be related to notifications

jose reyero’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Ok, closing for now, When you find out let us know.

jwjoshuawalker’s picture

Title: Notification breaks content Import » Notification breaks content Import

This is happening again as of the following versions:
Drupal 6.19
CCK 2.8
Notifications 6.x-4.0-beta7

I don't want to be too gung-ho about who to point the finger at, but I know that prior to updating to these versions, we were at:
Drupal 6.17
CCK 2.6
Notifications 4.0-beta6

At that time, the content type import worked. Luckily, I had built a module that was deploying new content types via a dummy form and the 'import code' for CCK was stashed in a file. I say lucky because I was able to see that the '0 => 1' part was present even in the old version seen here:

  'notifications_node_ui' => 
  array (
    0 => 1,
    'form' => false,
    'comment' => false,
    'links' => false,
    'teaserlinks' => false,
    'subform' => false,
    'block' => false,
  ),

I reverted back to older CCK, no good. Did the same w/ notifications and no luck. I'm assuming it was a change in Drupal's form submission process that is causing the import to fail now where it previously allowed that value, however I don't think that '0 => 1' should be there and I'm not quite sure who is adding it. I haven't had the time to track down in the modules where this part is generated but hopefully this post can get some attention as it will be a week or so before I can start looking into it.

By the way... removing 0 => 1, makes the import work fine but I'd like to know who is adding it to the CCK export code.

jwjoshuawalker’s picture

Version: 6.x-2.0 » 6.x-4.0-beta7
Status: Closed (fixed) » Active

Woops, forgot these 2 changes

jose reyero’s picture

Status: Active » Closed (cannot reproduce)

Please, find out which module before reopening the issue. Thanks.

liquidcms’s picture

Status: Closed (cannot reproduce) » Active

re-opening.

yes, Notifications is breaking cck node type import.

cck: 6.x-3.0-alpha1

node type is very simple - only title/body; no fields added.

import causes: illegal choice detected error

watchdog reports 2 errors:

Illegal choice author in Allowed subscription types element.
Illegal choice nodetype in Allowed subscription types element.

Disabling Notifications module and import works fine.