Closed (fixed)
Project:
Registry Rebuild
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 Jan 2012 at 23:19 UTC
Updated:
6 Apr 2013 at 22:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
rfayThis seems to fix it. I think the problem is that your database/codebase is so very old (7.2). But I don't see why we shouldn't add this.
Comment #2
rfayI went ahead and committed (as it seemed no harm), http://drupalcode.org/project/registry_rebuild.git/commitdiff/4e75d07
Comment #3
geek-merlinthis was a fast fix! kudos!
Comment #4
geek-merlinhmm, a first try gives me:
rr does not freak out anymore, but registry seems not fixed
Comment #5
rfayI guess I jumped the gun. I'm not entirely sure this is worth following up though, as updating to 7.10 fixes the problem. I just did a "git checkout 7.10" and "drush updatedb" and all was well.
May very well be worth solving this, but it may be just an old remnant of ancient D7.
What's your opinion? Is it worth going forward to debug this, or should we just assume that people would be using more recent D7?
Comment #6
geek-merlinlooks like the pragmatic solution is to just do the update.
anyone who googled this will now know what to do.
and anyone who notices that an update doesn't do the job should feel free to reopen.
have a nice day randy and cu at the commerce modules party!
Comment #7
geek-merlinwow, this site is a nasty little bastard that might teach us a lesson or not.
in my place:
* checked out current core and drush updb
* drush status now works fine
* login and going to development/testing and got "class view not found"
* "drush upc" gave "Class 'DrupalQueue' not found"
Comment #8
geek-merlinfirst observations:
* table registry_file DOES contain modules/system/system.queue.inc
* table registry DOES NOT contain DrupalQueue
* file system DOES contain said file which looks fine and with same chmod as anyone around
Comment #9
geek-merlinWOW, what did the job:
* empty both registry tables
* drush rr
so it looks registry_rebuild does NOT parse files that are in the table even if class data may be corrupt.
i see 2 issues here:
* for best dx core should offer a full rebuild in case of class-not-found
* for now this drush module should "truncate table registry" - maybe warning user
Comment #10
rfayYeah, I've always wondered if it wouldn't be better to just start with an empty registry. However it works so well for so many things I'm hesitant to make such a significant change.
Comment #11
geek-merlinperhaps a documented drush option.
let's call it "bazooka" :-)
Comment #12
rfayI like it. Patches welcome, too.
Comment #13
rfayComment #14
joachim commentedJust got bitten by this too. Would be very handy to have this!
Comment #15
joachim commentedHmm, and again. I should maybe write this patch! :)
> However it works so well for so many things I'm hesitant to make such a significant change.
Accidentally copying a class name to another file, which then gets the registry stuck thinking the class is in file B rather than the correct, original file A! Currently drush rr won't fix this.
Comment #16
omega8cc commentedSomething like this?
Comment #17
omega8cc commentedCommitted after some testing: http://drupalcode.org/project/registry_rebuild.git/commit/6abd740