Skip to content

[Feature Request] Included blocks of content fall back #3671

Description

@JoeIzzard

Describe the feature you'd like

I am using the method outlined in #978, protecting pages and including them to give protect blocks of content still within the flow of an existing page, for example for admin info.

It would be great for somethings to be able to specify a fallback for a block of content so that if the included protect content can't be displayed because of permissions, we can leave a Please contact X for assistance message. This would ideally be specified at the inclusion tag level. This could take the form:

{{{@101*@1#blocked}}

In this example we are trying to include page 101, but if that is protected and you are not allowed to see it, display the blocked section from page 1. Exact syntax could be something cleaner but this would allow much more control over these sorts of things.

Describe the benefits this would bring to existing BookStack users

This would give much more exact control over what is displayed when content is protected and would allow us to give fallback information. Currently you can just include both pages but then people with access would see both pages content.

Can the goal of this request already be achieved via other means?

No, not that I am aware of.

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?

6 months to 1 year

Additional context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions