Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
routing system
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
22 Feb 2015 at 12:18 UTC
Updated:
13 Mar 2015 at 15:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tstoeckler_access_modehas always bothered me when I used it and when I have taught others Drupal 8 but I could never really pin-point why. After reading the issue summary, I now know why! :-) Thanks.I totally agree. So long as we stick to the
allowed()/neutral()/forbidden()trifecta - which is not going to change at this point -_access_modeis just conceptually wrong.Comment #2
dawehnerJust an experiment. I don't say that there aren't usecases for ANY, BUT
Comment #3
fabianx commented+1 to that! I don't know the code good enough to be able to sensible RTBC it, though.
Comment #4
catchYes I've only seen this cause security issues and not actually help anything.
Comment #5
wim leers+1
Comment #6
dawehnerBumping to major, as it is security hardening.
Added a beta evaluation.
Comment #7
tim.plunkettWhy keep the constants? I would have expected this patch to remove them.
Comment #8
dawehnerGood point tim!
Comment #9
klausiYep, this caused the security issue in #2420559: REST permissions are not working as expected., +1 on the removal.
Comment #10
Crell commented*sniff* I'll miss you, _access_mode.
Comment #11
klausinow we have "requirements:" twice here?
Comment #12
dawehnerIt's not the first time when I think that the YAML parser is not strict enough.
Comment #13
wim leersComment #14
alexpottThis issue addresses a major bug and is allowed per https://www.drupal.org/core/beta-changes. Committed 9c2b19c and pushed to 8.0.x. Thanks!
Comment #16
jibranWe have a change notice which needs update or deletion
Comment #17
dawehnerUnpublished https://www.drupal.org/node/2107991 updated https://www.drupal.org/node/1851490