I had recently created a custom module for Drupal 4.7.4 which worked perfectly. Then I switched my Drupal over to version 5, which went fine. Then I followed the Module conversion information for 4.7 to 5, but after I finished I couldn't get it to show up in my Drupal 5 modules section. It won't list it, is there something I'm missing? I added the module.info file, but still nothing. I even checked it against Drupal's core Blog module, and I can't seem to find the issue. If anyone has any insight, I'd greatly appreciate it.

Comments

rszrama’s picture

You're gonna have to post some more up here... perhaps the contents of your .info file for starters. And did you actually name it .info where is equal to the name of your .module file?

----------------------
Current Drupal project: http://www.ubercart.org

jonathanchris’s picture

I did use the proper naming convention mymodule.info (yes i used my actual module name and not mymodule). Here's what is inside of it:

name = Get To Know
description = Adds the Get to Know section to your site.

My module is about 260 lines so I didn't think it would be proper to put the whole thing in a post, but I don't know what else to do.

glendac’s picture

Don't you need to include an Id line in the .info file for Drupal 5.x? For example, the line for the aggregator module is - ; $Id: aggregator.info,v 1.2 2006/10/05 15:47:55 dries Exp $.

jonathanchris’s picture

I'm pretty sure that is only used for CVS use. I tried it with and without it so I'm pretty sure that isn't the problem. But thanks for the suggestion :)

And like I said I could be wrong, I've been tinkering with this code for the past two days straight, and might have had something else wrong when I had added the ;$Id: $

coreb’s picture

look at some of the other module's .info files (core and contrib). Most of the contrib modules have a line like

; version added by drupal.org packaging script on 2006-11-20
version = "5.x-1.0-beta"
project = "gettoknow"

Add at least the version, I added project because others were added for some unknown reason.

jonathanchris’s picture

Well apparently you can't have any other folders in your module folder that contain earlier versions of the module. I didn't think it would be a big deal but apparently it was. Thanks for everyone's help!

rszrama’s picture

hehe Yeah, Drupal scans the entire modules directory, including all subdirectories. Previous versions would present a problem, but you can always just add an extension to them, like mymodule.module.old. That'll stop it from picking up on them.

And you're right, to answer the other posts... the first line is added by CVS when you commit the code. It's not necessary, and in the code is basically a comment (meaning it won't affect functionality in your installation).

----------------------
Current Drupal project: http://www.ubercart.org

jonathanchris’s picture

Thanks for the tip, I ended up scraping the old one due to frustration, which ended up working out for the best. I'll have to use that tip next time though.