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

"Edit permissions for this Document Type" gives APIError #17107

Closed
Rockerby opened this issue Sep 21, 2024 · 3 comments
Closed

"Edit permissions for this Document Type" gives APIError #17107

Rockerby opened this issue Sep 21, 2024 · 3 comments

Comments

@Rockerby
Copy link
Contributor

Rockerby commented Sep 21, 2024

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

14.3.0-rc

Bug summary

From a new Umbraco installation, clicking Create from the content menu and following the button that appears for "Edit permissions for this Document Type" takes you to a Doc type creation page with an APIError and then you are unable to create a new Doc Type from this page.

Specifics

The specific URL that throws the error is https://localhost:44331/section/settings/workspace/document-type/edit/undefined/view/structure (this is where the Edit button takes you when clicked).

Here's a short screen grab showing the issue:
chrome_qXda8NAh7V

I've also tested in 14.2.0 and it does the same thing.

Steps to reproduce

  1. Install Umbraco 14.3.0-rc
  2. Head into the back office - https://localhost:44331/umbraco/section/content/dashboard/dashboardTabsContentIntro
  3. Click the three dots next to Content and click create
  4. Follow the edit button in the pop-out
  5. See an error and be unable to add a doc type

Expected result / actual result

Expected is to be able to add a document type following the button.


This item has been added to our backlog AB#44319

Copy link

Hi there @Rockerby!

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 iOvergaard added state/sprint-candidate We're trying to get this in a sprint at HQ in the next few weeks state/reproduced area/frontend affected/v14 labels Sep 23, 2024
@iOvergaard
Copy link
Contributor

Thanks for the report, I see it as well. We will look into it!

@iOvergaard
Copy link
Contributor

We have a fix ready and it will be merged into the final build of 14.3.

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

Successfully merging a pull request may close this issue.

2 participants