Pricing

[lstrzebinczyk]

I started working on pricing. By occasion I'm implementing config via database, do we might follow pricing with whatever needed that dynamic config. It seems to be pretty straightforward, but I have some questions.

1. Events are paid (or can be) per day. But, at this point, begin and end dates can be changed, and this should be included in payment model. I see 2 possible solutions: a) we recalculate the pricing, and if it's the same or lowe, nothing happens. If it's bigger than the last one, we create a new one with the difference. b) We disable begin date and end date editing. Both are easy to implement, the first one is no more than hour of implementation longer.
2. Config and accepting payments are quite sensitive operations. I suggest we save id of user, who introduces these changes. Just for a safety. Very easy to do.

@hapticastudio please state your position on these topics.

[hapticastudio]

ad 1: how about other solutions: i) if event was started (and it's still living): add options 'close it now' and 'extend' - this first do not use prices, this second wille create new event ii) if event don't started yet, use your proposition a

ad 2: ok

[lstrzebinczyk]

This sound rather complex, I'll see what I can do.