"but a previous module was in 'sites/all/modules/"
| Project: | Site Documentation |
| Version: | 5.x-1.9 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | NancyDru |
| Status: | postponed (maintainer needs more info) |
Jump to:
Nancy,
This is a very helpful model that I am sure I don't know how to best utilize. So, sorry for what may be a dumb question, but:
Every time I run sitedoc, I get the following three errors:
* 'Throttle' for the 'Core - optional' package was found in 'modules/ ' but a previous module was in 'sites/all/modules/ '.
* 'Tracker' for the 'Core - optional' package was found in 'modules/ ' but a previous module was in 'sites/all/modules/ '.
* 'Upload' for the 'Core - optional' package was found in 'modules/ ' but a previous module was in 'sites/all/modules/ '.
I am assuming that the 'sites/all/modules' directory is referring to the place where I put all of my non-core modules, and the three modules being referred to are all core modules, and are definitely not in the sites/all/modules folder.
Can you give me a hint as to what these errors mean and how to begin a fix?
Many thanks,
Maria
#1
The only time I have seen this, and the reason why I added this, was when someone installed Drupal core in a subdirectory of the wrong modules folder. Please double check to make sure there is no chance that any Drupal modules are in sites/all/modules. Drupal core modules should be in "modules" and nowhere else.
Meanwhile, I'll see if I can make the message a little better about tracking down the problem.
#2
Ah, I have seen another case where this would have happened, but didn't think about it the time. There was one module I downloaded (but don't remember which one) that improperly had a
package = Core - optionalline it its .info file. That would also cause this.If you can, go through your contributed modules and check their .info files. If you find one with that line in it, you need to submit a bug report against that module.
The incorrect module should also be included in the "Core - optional" list that is produced. If you seee something in that list that's not really core, that's the one to report. And you can safely delete the "package" line in that module's .info file to fix the problem.
#3
Nancy,
Many thanks. Turns out it was taxonomy_list, which was out of date and not being caught by the update module. I updated and it is not listed correctly, no errors returning. I would NEVER have guessed that as the problem.
BTW, I love your various modules and over the last few years I have found your suggestions and how-to's enormously helpful.
Maria
#4
Good, I'm glad you found and provided feedback. You may very well have saved someone else from the same problem.
Was it TL that I found that problem in? I don't remember. But I own Taxonomy List now. Hee hee, even if you downloaded a new version today, it's out of date too - I'm about to post some nice new improvements.
#5
I am getting a bunch of this on my multisite installation (5.x):
None of those modules or duplicates of them are in sites/all/modules as the warnings above suggest.
I also get a lot of yellow warnings, although I can trace most of them to modules having submodules called the same or being included in more than one package. But for example, there is no emfield submodule or anything similar in cck_address, it only has cck_address.module and cck_address_canada.module within it.
This is a multisite installation, running fine on 5.x which was ported 2 years ago from 4.7. I'm sorry if I can provide more feedback as I am getting ready to migrate to 6.x at this very moment (that's what I am running sitedoc for :p).
#6
By the way, I did not get this warnings until I upgraded the sitedoc module from 5.x-1.1 to 5.x-1.9.
#7
That feature was added somewhere between those releases, so that is not surprising.
It sounds like you have copies of the core modules in "sites/all/modules" which is not where they belong. Core modules should be in the "modules" directory in the Drupal root - and nowhere else. "Sites/all/modules" (or "sites/sitename/modules" should contain only contributed modules.
#8
No, I don't have copies of the core modules outside the [drupal root]/modules directory.
I am running Drupal on 2 load balanced servers behind one load balancer, but in any case they both use a mirror (actually the sites folder in one server is just a link to sites folder in the other).
This should not matter, but, depending on your code, I guess it could have something to do with it.
Regards,
Carlos.
#9
Probably it is related, so posting to here. Each time I visit Site Documentation admin page, I get these "package was found in ... but a previous module was in ..." messages. Do they mean a problem? I am using version 6.x-1.2.
# 'Ad Weight Probability' for the 'Ad' package was found in 'sites/all/modules/ad/weight/ ' but a previous module was in 'sites/all/modules/ad/cache/ '.
# 'Ads (old)' for the 'Adsense' package was found in 'sites/all/modules/adsense/old/ ' but a previous module was in 'sites/all/modules/adsense/contrib/ '.
# 'Search (old)' for the 'Adsense' package was found in 'sites/all/modules/adsense/old/ ' but a previous module was in 'sites/all/modules/adsense/contrib/ '.
# 'Click filter' for the 'Ad' package was found in 'sites/all/modules/ad/statistics/ ' but a previous module was in 'sites/all/modules/ad/cache/ '.
# 'Location CCK' for the 'CCK' package was found in 'sites/all/modules/location/contrib/ ' but a previous module was in 'sites/all/modules/cck/modules/ '.
# 'Performance Logging' for the 'Development' package was found in 'sites/all/modules/devel/ ' but a previous module was in 'sites/all/modules/location/contrib/ '.
# 'Revenue sharing basic (old)' for the 'Adsense' package was found in 'sites/all/modules/adsense/old/ ' but a previous module was in 'sites/all/modules/adsense/contrib/ '.
# 'User to User Points' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Admin Email' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Badges' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Invite' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints No Negative' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Page Views' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Register' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Reset' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Retroactive' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Userpoints Role' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Role exempt' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
# 'Votingpoints' for the 'Userpoints' package was found in 'sites/all/modules/userpoints_contrib/ ' but a previous module was in 'sites/all/modules/kudos/contrib/ '.
#10
I've seen this in 6.13/6.x-1.2 where a module is within another module (sub module if you like) and is down to the comparison of package paths.
As an example if you have the filefield module installed, you'll also have a subdirectory within filefield that contains filedfield_meta. Both are in the 'CCK' package.
Here's the layout:
sites/all/modules/contrib/cck
sites/all/modules/contrib/filefield
sites/all/modules/contrib/filefield/filefield_meta
Sitedoc does the following when examining the filefield and filefield_meta modules:
1. determines that filefield is part of the CCK package which it's already seen and so compares the package paths...
2. package path for filefield [sites/all/modules/contrib/] is a substring of the CCK package path [sites/all/modules/contrib/cck/modules/] so all is well.
3. determines that filefield_meta is part of the CCK package which it's already seen and so compares the package paths...
4. package path for filefield_meta [sites/all/modules/contrib/filefield/] is not a substring of the CCK package path [sites/all/modules/contrib/cck/modules/] or vice-versa and so throws a warning.
Have a snout around about line 1194 in sitedoc.module (6.x-1.2).
I guess it can be coded round by identifying that the project name is the same as the parent.
#11
Just adding mine to what has already been discovered. Version 6.x-1.2
My 'errors' occurred after updates to modules that in each instance had prior contributed modules as sub modules in sub folders, if that makes any sense. See below:
# 'Date' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
# 'Date Locale' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
# 'Date Popup' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
# 'Date Repeat API' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
# 'Date Timezone' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
# 'Date Tools' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
# 'Evoc Reference' for the 'CCK' package was found in 'sites/all/modules/evoc/modules/ ' but a previous module was in 'sites/all/modules/cck/modules/ '.
# 'GMap Geo Integration' for the 'Geo' package was found in 'sites/all/modules/gmap_addons/ ' but a previous module was in 'sites/all/modules/geo/modules/ '.
# 'Location Add Another' for the 'Location' package was found in 'sites/all/modules/location/contrib/ ' but a previous module was in 'sites/all/modules/gmap_addons/ '.
# 'Location CCK' for the 'CCK' package was found in 'sites/all/modules/location/contrib/ ' but a previous module was in 'sites/all/modules/cck/modules/ '.
# 'Location Search' for the 'Location' package was found in 'sites/all/modules/location/contrib/ ' but a previous module was in 'sites/all/modules/gmap_addons/ '.
I have reviewed every folder mentioned above and have found that it is in the correct location and there are no duplicate folders; i.e. old folders & items removed.
I've been going through tables one at a time to see if this path info is 'stored' some where, with no luck so far.
#12
Subscribing. Getting similar warnings concerning adsense, captcha, cck, devel, and views modules.
Have also checked all install directories (multi-site install) for duplicates, and found none.
#13
UPDATE
I created a brand new test instance of Drupal 6.14, downloaded all of the latest versions of all 3rd-party modules used, but especially those with the issues I had reported here previously.
Main Goal - UML Schema of Tables
My initial and main goal for this test instance was to produce a UML Schema diagram of all tables; Drupal Core, Core Optional and 3rd-party. (I am also at the same time testing out/trial running various DB visualization tools in the process.)
Secondary Goals - Gain deeper knowledge of Database; MySQL DB Maintenance & Optimization
At the same time I begin reviewing what actions/conditions with the MySQL database actually occur during the following:
Tertiary Goals - Locate source(s) of Warnings, Errors, DB Poor Performance, etc
Finished my initial UML diagram, will need to go back to secondary goals, later as what I found during a minor update test was this:
Run Update to Geo and Views modules
Process
Disabled above two modules and all dependencies, as well as the ones in my initial report here. (I was just curious to see what would happen if anything.)
Uninstalled Gmap Geo Integration, no uninstall option for all of Geo, (Odd, but seems to be the norm. Also GMap Geo Int. is also part of GMap Addons, not Geo.) did not uninstall Views.
Ran update.php, did not manually select any specific versions, just ran it.
The following warnings occurred (see further below) and what I find interesting is that they occurred for modules that were untouched, other than disabling them. Did not run uninstall, no new path or folder, nothing moved or updated, other than what ever occurs when update.php is run. I really doubt that should be occurring; old path and new path are the same, nothing changed.
I took a look at the 1194 code pointed out above, and would really like to know where that path info is stored, especially since I did not find a table associated with Site Documentation.
I'm going to recreate my test instance again from scratch, and this time only add the modules in question or those throwing these warnings:
Warnings
Date' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
Date Locale' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
Date Popup' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
Date Repeat API' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
Date Timezone' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
Date Tools' for the 'Date/Time' package was found in 'sites/all/modules/date/ ' but a previous module was in 'sites/all/modules/calendar/ '.
Evoc Reference' for the 'CCK' package was found in 'sites/all/modules/evoc/modules/ ' but a previous module was in 'sites/all/modules/cck/modules/ '.
FileField Meta' for the 'CCK' package was found in 'sites/all/modules/filefield/ ' but a previous module was in 'sites/all/modules/cck/modules/ '.
GMap Geo Integration' for the 'Geo' package was found in 'sites/all/modules/gmap_addons/ ' but a previous module was in 'sites/all/modules/geo/modules/ '.
Location Add Another' for the 'Location' package was found in 'sites/all/modules/location/contrib/ ' but a previous module was in 'sites/all/modules/gmap_addons/ '.
Location CCK' for the 'CCK' package was found in 'sites/all/modules/location/contrib/ ' but a previous module was in 'sites/all/modules/cck/modules/ '.
Location Search' for the 'Location' package was found in 'sites/all/modules/location/contrib/ ' but a previous module was in 'sites/all/modules/gmap_addons/ '.
Modules Issuing Warnings (for Drupal 6.14/Site Documentation 6.12)
Date
Date Locale
Date Popup
Date Repeat API
Date Timezone
Date Tools
Evoc
FileField
Gmap Geo Integration
Location Add Another
Location CCK
Location Search
I plan on updating this post with corrections to anything I missed during the first run.
***VERIFIED***
Second Run completed
Created a brand new MySQL database and the above issues remain.
Enabled ONLY Site Documentation and none of the modules showing these issues, yet the issues still appear?!.
Ran update.php and again no change to these issues.
#14
Subscribe: similar issues regarding "date modules" alerts.