Bug: internal alias pages still appear in menu if page is not public
Reported by dleffler | January 6th, 2016 @ 07:46 PM | in 2.3.8 (closed)
If you create an internal alias page which points to a content page, it will still appear even though the content page is set to NOT public (which the user couldn't get to even if they click on the link)
We need to perform a check on the target of the internal alias page so it follows the public/private status of the page it points to.
Comments and changes to this ticket
-
expNinja January 6th, 2016 @ 09:24 PM
- State changed from “new” to “resolved”
(from [a7a818122a3bdb58e626cbd2debfc4ef8b7df16f]) Now section model only adds an internal alias type page to the menu structure if the page it refers to is also visible (previously, if you made the target page private, the internal alias page would still appear in the menu, but be pointing to a page the user couldn't get to due to their permissions) [#1340 state:resolved] https://github.com/exponentcms/exponent-cms/commit/a7a818122a3bdb58...
-
expNinja January 7th, 2016 @ 09:12 PM
(from [ed5cdc60fec5b12115889e9eeb19a427afe9ff1b]) Now section model only adds an internal alias type page to the menu structure if the page it refers to is also visible (previously, if you made the target page private, the internal alias page would still appear in the menu, but be pointing to a page the user couldn't get to due to their permissions) #1340 state:resolved https://github.com/exponentcms/exponent-cms/commit/ed5cdc60fec5b121...
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
expNinja