Blogger Module Not Showing Up in Module List
kdfrawg - January 18, 2007 - 06:00
I know it seems silly, but I just downloaded the Blogger module, then uploaded the files to my Drupal site. I have performed this procedure a number of times with other modules, so I am fairly sure that I have done it correctly. To be sure, I erased the fist upload, re-downloded the module, and re-uploaded it to the site. All of the files that I downloaded have uploaded properly. The module says that it is the module for 5.x and I am running 5.0.
However, when I log in, 'Blogger' is not in the list of modules. I therefore cannot activate it. The rest of the modules are there and seem to work (activation, deactivation, configure, etc.)
Does anyone have any ideas that might help me?
Thanks!
Michael
No info file
The info file is missing from the download package
Check >> http://drupal.org/node/107323
Re-upload Blogger.module again
I do reupload the blogger.module again using SmartCVS. I don't know if the entire files uploaded well because we can not see the changes before about 12 hours ( or 8 ? ) hours.
Here, I found what was caused this upload problem:
- I accept default SmartCVS setting "Enable Alternate Path= Blogger", and my local file is "D:\MASTER\Internet\CMS\Drupal\5.x\blogger".
- above setting makes new folder struct like this: D:\MASTER\Internet\CMS\Drupal\5.x\blogger\blogger which contain the PREVIOUS files not the right one in this folder "D:\MASTER\Internet\CMS\Drupal\5.x\blogger" (without additional folder blogger\blogger). My fault, I didn't recheck the automatic folder created by SmartCVS 5.1.
Now, let's we wait for another hours after Drupal project do sinchronize with the CVS storage.
My suggestion to Drupal storage:
- avoid using CVS but provide a web based file storage which will have this advantage:
1. Provide same interface since SmartCVS different to TortoiseCVS, jCVS, LinCVS and so on.
2. No need additonal several hours for users to download the new one after the developer send their module or themes update.
3. Developer can provider their versioning rather than follow 5.x-1.dev.whatever name. But the website will provide a select list for which version the module/theme compatible to Drupal version.
4. No need to browse to Drupal storage to find which module that we want to update.
Well, You're Right...
...there is no info file. That's because there wasn't one in the download. Of course, I didn't know that having an info file was a deal-breaker. There must be some reason why they would not include an info file with the blogger module, but since it seems the module won't work without one, I'm not sure what the reason would be. I suppose I should read some more and find out what I should do next...
Thanks for the answer! I really appreciate it.
Michael
So I wrote a barebones .info file...
...for blogger and was able to activate it because it shows up in the module list now. But I don't think I got it all right because I don't seem to have all of the options that the writer mentioned in the module description. Maybe it's not very automatic and I have write my own blogger list, but then I don't see what the module is for.
Doesn't a module usually come with its own .info file?
Well, I just went and checked the 4.7 version and it doesn't have a .info file either, although the instructions say that you should install it like any other module. But how can you do that if the .info file is not there and a .info file is needed to install it?
Does this mean that after you write your own .info file you should also go in and rewrite the php in the module file itself to do what you want it to do? This is actually fairly confusing.
Nope, I just looked through the code. It would appear that it should present a form inside Drupal Blocks so that the user can set the desired options. Of course, it does not do that.
thanks!
ps - submitted a bug report