Closed (fixed)
Project:
DBTNG
Version:
6.x-1.0-alpha7
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2010 at 07:41 UTC
Updated:
25 Mar 2011 at 22:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
mikey_p commentedAre you using Autoload 2.0-rc1?
Comment #2
wonder95 commentedHmmm, that is listed under Requirements, isn't it?
Installing Autoload 2.0-rc1 fixed the problem.
Thanks.
Comment #3
joachim commentedThis is broken again with autoload 6.x-2.0.
Comment #4
ludo.rI get the same error with with autoload 6.x-2.0
Comment #5
kaynen commentedTry rebuilding the theme registry. That worked for me. In my case, using the Devel module, I just used "flush all caches" and the error no longer occurred.
Comment #6
willieseabrook commentedI confirm this is still happening on:
migrate-6.x-2.0-rc1
autoload-6.x-2.0
dbtng-6.x-1.0-alpha7
Comment #7
xenophyle commentedSubscribing
I should add that clearing the theme registry doesn't work for me. I get the error as soon as I clear the cache and try to go back to the migrate page.
Comment #8
xenophyle commentedSome progress:
I printed out the value of $lookup_cache at autoload.module line 184 and saw that the path to dbtng was wrong (sites/all/modules/dbtng instead of sites/all/modules/contrib/dbtng). I think this was the result of moving the dbtng module into the contrib folder after enabling the module, but I can't remember for sure if that's what I did.
I wasn't able to fix this by clearing the cache, since I just kept getting this error everytime I tried to clear the cache, but I disabled the migrate, dbtng and autoload modules and then re-enabled them, and that fixed it.
Comment #9
xenophyle commentedNever mind, the error came back after a few minutes.
Comment #10
xenophyle commentedI feel like I'm spamming this issue, but one more thing... I don't know if this is a mistake or just something I don't understand, but I notice the .info file uses "files[] =", which is not supported until D7.
Comment #11
joachim commented> the .info file uses "files[] =", which is not supported until D7.
That is what autoload module (branch 2.x) uses to detect classes.
Comment #12
xenophyle commentedI really need to be able to use the migrate module and I want to help fix it, but I'm clueless what the autoload and dbtng modules are doing. It looks like dbtng is trying to load DatabaseTasks, but I can't tell where it expects to get it from.
Could someone provide a hint that might help me debug?
Thanks
Comment #13
kristen polSubscribe... I see the error as well with:
autoload 6.x-2.0
dbtng 6.x-1.0-alpha7
migrate 6.x-2.0-rc2
Kristen
Comment #14
mikeryanOne thing I think people haven't mentioned here is that they're enabling all the modules at one time at admin/build/modules - try enabling one at a time (i.e., first autoload, then dbtng, then migrate and its relations). I finally ran across this (I usually use drush to enable and disable modules one at a time)... I find that if I enable Autoload and DBTNG at the same time (no Migrate), I get "Fatal error: Call to undefined function autoload_registry_update() in /Users/mikeryan/html/migrate62/sites/all/modules/dbtng/dbtng.install on line 9". Actually, I get that enabling all three at once as well... I did the the "Class 'Database' not found" error once, but can't reproduce it now. Anyway, the place to start is dbtng.install...
Comment #15
mikeryanOK, with this patch I can enable autoload and dbtng, or autoload, dbtng, and the whole bunch of migrate modules, without error. Be sure you have uninstalled (not just disabled) all the relevant modules before trying this.
Comment #16
mikeryanOK, that may work for interactive enabling, but it breaks Migrate simpletests, which die with the "Class 'Database not found" error...
Comment #17
xenophyle commentedI had not been enabling them all at once, since I didn't think it was possible to enable a module without first enabling the one(s) it depends on.
Comment #18
mikey_p commentedCommitted, thanks. This will be in rc2.