9 Answer(s)
-
0
Hi @FlexSolution
This is by design and it has been implemented with recurring payments feature. When you create an edition, some users can purchase this edition. Instead of editing the properties of this edition, we suggest to create a new one with new price and other properties.
-
0
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.
-
0
@FlexSolution sure, you are right. We will update the docs.
-
0
https://github.com/aspnetzero/documents/commit/35594bf9951a88c24994d954d6df42c98a64119f
-
0
I'm currently playing around with editions - to be honest: I was a bit confused about this screen as well, when I tried changing some values. Obviously, editing an edition that is in production and already has tenants assigned is not a good thing to do - so I can perfectly understand the way it is implemented.
Still, I think it would be better to just disable the input fields instead of not showing them at all. Maybe adding additional information about creating a new edition and moving tenants instead of editing an existing edition!?
What do you think?
-
0
-
0
@FlexSolution, sounds good to me!
I'm not sure ASPNETZERO guys will read our comments since this question has been closed already - could you create a new issue on GitHub?
-
0
Maybe it's enough if we do it this way.
We click on Reopen :)
-
0
Hi @FlexSolution
If you create an issue on GitHub we can think on this. As you know, we made Stripe integration for recurring payments. If stripe allows us to update those information on their side, we can make those changes.