Activities of "FlexSolution"

Okay, no problem. That's how I did it in the end. You should just change your documentation. There is the following text:

When we click Actions/Edit for an edition, we can see it's poperties:

https://docs.aspnetzero.com/documents/zero/latest/Development-Guide-Angular#edition-management

That's why I thought it was a bug.

I changed the language over the UI but I reset it and it's still the same error. I also took a completely new project, didn't change anything and it's still the same bug. It's no problem for me to change the message I just wanted to let you know.

That is a very important request.

I know this possibility from other products. However, it is often regulated differently. Mostly there is the possibility to define addons. You then book the addons to the actual edition.

This addon can be private or public and also overlay or extend properties of the edition. Additionally an addon can be assigned several times. Each addon is assigned a price which is then added to the edition price.

For example an addon can be 10 Gb more memory. Now you can assign the tenant 2 times the addon then he has 20 Gb or even a new addon with 20 Gb.

I think that with the addons would make more sense here. You could select all the features you assign to an edition as an addon and the editions would still be nicely separated. You would also have a better overview of what you have additionally assigned to whom.

Sorry, I forgot to write that down. Version 6.7.0 Core & Angular

Here a picture from your languages tabele with the error.

I've been thinking about it, too. You could block the prices and the change of free and paid. Which is ok. But you should be able to change the rest of the information? They have no influence on the price. Only on what happens later.

Maybe it's enough if we do it this way.

We click on Reopen :)

I found the answer in this post https://support.aspnetzero.com/QA/Questions/6680

Thank you. That was the mistake. Sorry

I don't think it's a good solution to hide something in the view. We have a concept here that works through an API so anything that is locked should not work through the API. If I only disable it in the template it is still possible to change it through the API.

We use angular.