Content type import doesn't work and other installation issues
grendelshitsuren - March 10, 2008 - 14:55
| Project: | Flickr Gallery |
| Version: | 5.x-1.0-beta |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | wonder95 |
| Status: | active |
Description
I tried to import the data in the included cck_photo_field.txt, but that didn't work. There's already a content type called "image" and even if I changed it's name, the import still didn't work as the title is identical... am I missing something here? Should the image module be deinstalled?

#1
I got this to work by changing the names from Image to PhotoImage (You can change it to whatever you want...it says so in the read me).
See below
$content[type] = array (
'name' => 'Image',
'type' => 'image',
'description' => 'Image to be displayed',
'title_label' => 'Title',
'body_label' => 'Description',
'min_word_count' => '0',
'help' => 'Size must be less than 1.5 MB',
'node_options' =>
array (
'status' => true,
'promote' => false,
'sticky' => false,
'revision' => false,
),
'comment' => '2',
'old_type' => 'image',
'orig_type' => '',
'module' => 'node',
'custom' => '1',
'modified' => '1',
'locked' => '0',
);
to
$content[type] = array (
'name' => 'PhotoImage',
'type' => 'photoimage',
'description' => 'Image to be displayed',
'title_label' => 'Title',
'body_label' => 'Description',
'min_word_count' => '0',
'help' => 'Size must be less than 1.5 MB',
'node_options' =>
array (
'status' => true,
'promote' => false,
'sticky' => false,
'revision' => false,
),
'comment' => '2',
'old_type' => 'image',
'orig_type' => '',
'module' => 'node',
'custom' => '1',
'modified' => '1',
'locked' => '0',
);
Further instructions
-- Ade Atobatele
#2
#3
I actually have a patch for the problem with the inital taxonomy gallery not being created here. I just want someone to review it before I commit it.
#4
I just put out a BETA2 release to fix some of the basic issues, such as the taxonomy vocabulary not being created. I was thinking about allowing the user to specify the content type used on the admin page somehow. I'll look at doing that.