[19.0][ADD] website_event_hidden_by_password#515
Open
odrakirmusic wants to merge 1 commit into
Open
Conversation
Hide a website event behind a per-event access password. A hidden event is fully redacted on the events listing (no name, date, place or image; only a lock, "Private" and an optional public codename), shows an info-free password wall, and is kept out of the website search (name, facet counts and autocomplete), the canonical-URL redirect, the iCal export and sitemap.xml, so its name and details never leak. Managers bypass the wall. Split out from the discussion on PR OCA#445 as a standalone, password-based counterpart to website_event_private.
OCA-git-bot
added
series:19.0
mod:website_event_hidden_by_password
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hide a website event behind a per-event access password. A hidden event is fully redacted on the events listing (no name, date, place or image; only a lock, "Private" and an optional public codename), shows an info-free password wall, and is kept out of the website search (name, facet counts and autocomplete), the canonical-URL redirect, the iCal export and sitemap.xml, so its name and details never leak. Managers bypass the wall.
Split out from the discussion on PR #445 as a standalone, password-based counterpart to website_event_private.