Bug #13540

Privacy policy static page default installation slug does not match page name, causing issues when regenerating slugs

Added by Dan Gillean 11 months ago. Updated 7 months ago.

Status:NewStart date:07/02/2021
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Menu / navigation
Target version:Release 2.7.0
Google Code Legacy ID: Tested version:2.7
Sponsored:No Requires documentation:No

Description

In #12180, we added a new default static page with a privacy policy, and a configurable privacy policy notification banner as part of our efforts to add features that would support GDPR requirements.

The default new static page is named Privacy Policy. The protected slug it was given at the time was "privacy". This means that if slugs are deleted and regenerated, then the Privacy policy page becomes inaccessible - the menu link now points to a page that doesn't exist (and so it will not display the privacy policy link in the quicklinks menu); the default notification banner link no longer works, etc.

To reproduce

  • In a new installation, open the Quick links menu
  • Select the Privacy policy static page
  • Now run the slug generation task with the --delete option
  • Repeat steps 1-2

Error encountered

  • The slug generated is privacy-policy, taken from the static page title
  • Because the slug no longer matches the menu settings, the "Privacy Policy" link either does not display in the quicklinks menu, or leads to a "Page not found" message

Expected outcome

  • Slug and page title are consistent
  • Regenerating slugs does not break the Quick links menu and default notification banner content

Other background and context:

Previously, privacy was a protected slug - however, before #13297, this meant that the privacy policy page could not be deleted. In the course of addressing this, it seems that the privacy slug is no longer protected. However, because the page title is actually "Privacy policy", this means that running the slug generation task with the --delete option means that the default privacy banner (and, if it was showing up at all, likely the link in the quicklinks menu as well) no longer work, as the replacement slug is "privacy-policy" instead of just "privacy".


Related issues

Related to Access to Memory (AtoM) - Bug #13297: Privacy policy static page cannot be deleted from the menus Verified 04/28/2020

History

#1 Updated by Dan Gillean 11 months ago

  • Related to Bug #13297: Privacy policy static page cannot be deleted from the menus added

#2 Updated by Dan Gillean 11 months ago

  • Priority changed from Medium to High

#3 Updated by Mike Cantelon 11 months ago

I think the quick links issue might be PHP version specific given that a commit where the quick links work fine on a Ubuntu 18.04-based VM won't work on the Ubuntu 20.04-based VM.

#4 Updated by Dan Gillean 7 months ago

  • Subject changed from Regression: Quick links menu and privacy policy static page issues to Privacy policy static page default installation slug does not match page name, causing issues when regenerating slugs
  • Description updated (diff)
  • Priority changed from High to Low

The other issues originally described in this ticket seem to have stemmed from CSRF token issues that have now been resolved. I have reworded this issue to capture the lower priority problem of the privacy policy page, marked the Priority as Low, and removed the 2.7 milestone for now.

Also available in: Atom PDF