Feature request: change internal method access to 'private' or 'protected'
Reported by dleffler | January 2nd, 2016 @ 02:08 PM
We could tighten down security a great deal by making the 'internal' methods 'private' and/or 'protected' instead of 'public' (default for no access/visibility modifier)
Comments and changes to this ticket
-
dleffler January 22nd, 2016 @ 06:31 PM
This also means renaming some controller methods to conform with standard permission names or 'remove_permissions' to block their being called by a non-admin
-
dleffler January 26th, 2016 @ 01:56 AM
- Title changed from “Feature request: change internal method access to 'private'” to “Feature request: change internal method access to 'private' or 'protected'”
This basically/mainly applies to the controllers...within expController, the method/variable MUST be 'protected' since 'private' will prevent the method/variable from being available to the other controllers.
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bug Tracker for Exponent CMS
dleffler
expNinja