Download & Extend
Image » Issues

Check existence of image content type on install

Posted by sharrison on May 16, 2009 at 6:29pm
Project:Image
Version:6.x-1.x-dev
Component:image.module
Category:task
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

I just installed the Image module on my Drupal 6.12 installation.

The module installed but it didn't create an image content type.

I then deactivated, uninstalled, and reinstalled the image module.

Again, no content type.

Is there anything I should have done differently to get this module up and running.

Thanks,

Stan

Login or register to post comments

Comments

#1

Posted by joachim on May 19, 2009 at 8:13am
Status:active» postponed (maintainer needs more info)

Have you actually checked the path at node/add/image -- going to it directly rather than via the menu? It could be you have a problem with your menu cache for example.

#2

Posted by sharrison on May 20, 2009 at 5:44pm

Thanks for writing.

I think I've uncovered what went wrong.

I created a "3rd Party image" content-type which is showing up when I go to node/add/image

So, I'm thinking that the image module can't install it's content type because I've already used it.

I'm going to delete my 3rd Party image content type and see what happens.

I'll let you know by tomorrow.

Again, thanks,

Stan

#3

Posted by joachim on May 20, 2009 at 7:48pm

Yup, if you created a node type called 'image' yourself then image module's node type won't get picked up.
Can you confirm that's what the problem was?
You may need to empty your cache before the node type is picked up -- or try disabling and re-enabling image module.

We should maybe add a check for that in the installer.
ETA: actually, I think maybe Drupal core should check when looking at a new node info hook that the content types aren't already there.

#4

Posted by sharrison on May 20, 2009 at 11:47pm

Yup. That was it. I

  • uninstalled the Image module
  • deleted my 3rd Party Image content type
  • reinstalled the Image module
    • Still not there
  • emptied my cache file 2x

And, yes, the Image content type appeared.

Self-created problem resolved.

Thanks,

Stan

#5

Posted by joachim on May 21, 2009 at 9:48am
Title:Image Content Type Not Created» Check existence of image content type on install
Status:postponed (maintainer needs more info)» active

I think we've had a few support requests about this.

How about checking for a pre-existing image node type in hook_requirements on install?

#6

Posted by sun on May 26, 2009 at 9:46am
Version:6.x-1.0-alpha4» 6.x-1.x-dev
Category:bug report» task

hook_requirements() sounds nice. But only display something before the module is installed, not afterwards (wouldn't make sense) - I wonder whether that is doable...

#7

Posted by joachim on May 26, 2009 at 10:09am

I think that's really a job for core: #468976: Module-defined bundle is not installed when a custom with same name already exists
But we can return REQUIREMENT_ERROR and prevent module installation.

nobody click here