Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Nov 2012 at 02:53 UTC
Updated:
25 Sep 2015 at 10:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
effulgentsia commentedThis can be applied on top of #1784312-76: Stop doing so much pre-kernel bootstrapping.
Comment #2
catchAbout to commit the other one, let's get this in quick.
Comment #3
catchComment #4
amateescu commentedLet's try to test it then.
Comment #5
amateescu commentedUgh.
Comment #7
amateescu commentedThat's an unrelated test failure, HEAD is broken atm: #1842726: Transliteration component must not contain drupal_alter().
Comment #8
c4rl commented#4: 1846376.patch queued for re-testing.
Comment #10
c4rl commented#4: 1846376.patch queued for re-testing.
Comment #11
effulgentsia commentedHEAD is working again, and #4 passed the retest, but isn't turning green for some reason, so here it is again.
Comment #12
fabianx commented#11 passed the BOT.
Comment #13
sunThanks, looks good to me.
Comment #14
catchCommitted/pushed to 8.x, thanks!
Comment #16
donquixote commentedDoes someone in here still remember this issue?
I am pretty sure this "fix" no longer works in current Drupal 8.
At least with the Composer ClassLoader, there is no way to "unregister" a namespace. Whatever is still happening there is bogus now...
http://drupalcode.org/project/drupal.git/blob/1f9a488b927e9548365bf4882e...
And here is what ClassLoader::add() actually does..
http://drupalcode.org/project/drupal.git/blob/1f9a488b927e9548365bf4882e...
This can only ever add to the registered namespaces, never remove any.
I am keeping this mechanic in the PSR-4 patch,
#2083547: PSR-4: Putting it all together
but I would prefer to remove it.
We can open a new issue for this, but I would like to get some feedback from the old days' participants first..
(and apologies if reopening is the wrong thing to do)
Comment #17
jhedstromSince modules can only be uninstalled now, are the concerns in #16 still applicable?
Comment #18
jeroenmarinusI have reviewed the comment of donquixote, but cannot find any traces of the code he references.
Just as jhedstrom mentions, it also doesn't seem to be relevant anymore. Closing this issue, if it somehow is not ok maybe it's better to open a new one.