Details
-
Bug
-
Resolution: Obsolete
-
Medium
-
4.4.0, 4.5.0beta1
-
None
Description
The original idea behind <requires> was that an extension would not load at all and throw warning / error if what it requires is not present.
Currently however this type is mapped to an internal "after" case, which is wrong, and causes issues like this: