Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Editors Unable To Select Page Template #17571

Open
nackler opened this issue Nov 18, 2024 · 2 comments
Open

Content Editors Unable To Select Page Template #17571

nackler opened this issue Nov 18, 2024 · 2 comments
Labels

Comments

@nackler
Copy link

nackler commented Nov 18, 2024

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.3.0

Bug summary

Content Editors without access to settings in the backoffice are unable to select one of several preconfigured page templates available for a page.

Specifics

I would like to be able to set up several page templates for a given document type and let my content editors choose one of the templates. I believe this functionality worked before the backoffice rewrite. It is close to working except for a permissions error (403 Forbidden) that the content editors get when trying to select a template.

Steps to reproduce

Set up multiple allowed templates for a "Page" document type.
image

Then log in to the backoffice as a content editor who just has content and media rights. Attempt to choose one of the available templates in the Info tab of the page
image

You will see that the template selector is empty and you will get pink errors in the bottom right hand corner
image

As the result of a request to the managment api
image

Expected result / actual result

Content editors should be able to choose which template a page uses, even though they do not have access to the 'settings' section of the backoffice.


This item has been added to our backlog AB#46198

Copy link

Hi there @nackler!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@iOvergaard
Copy link
Contributor

Thanks for reporting this. I can confirm it's an issue and we are prioritizing getting this fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants