Good morning Yves
Thanks for the speedy reply, **I** know that **MY** ticket was THE most important
so I've been sittin gon the edge on my seat waiting for the reply!! I appreciate, after a break away, there's probably a gazillion support requests so I appreciate you quick response! Thanks!!
2. File attached (matukio01.jpg) showing what's happening. You can do it yourself at
www.ckdev.info/party/events/all-events
(click to change months to February). You'll also see the white text on the yellow BG doesn't show. Now I did change that with CSS as I have a, technically, dark sheet BG due to the transparency and I needed it visible. Happy with the way the rest is looking with the changes I made. Wondered if that text has a separate CSS class?
3. As I said, this is SUPER critical to my client and, if you get your head around what she does, then you'll see why (you can see her current site athttp://partybrushesevents.com/calendar)
4. Great!
7. A view from the frontend would be awesome if your wish-list has space on it!!
9. OK - Really need to get these stacked to make it look nice. I don't remember there being an option in Themler (what I used for the template) to force vertical v horizontal.
10. See matukio02.jpg - would be useful (sometimes) to force a user to confirm their email address if we're sending info to them.
11. See matukio03.jpg - after writing this I saw another thread where you or Daniel reported that this isn't currently able to be disabled. It's OK>
12. This, I believe is important to anyone doing ticket sales. I think there needs to be options how it will be handled. For example:
A. More than "x" tickets - so $40 for 1-4 tickets, $35 if booking 5+
B. A user settable %age discount - this I've normally seen as an "Early Bird Discount" so would also need a cut off date
I have a component called j-Business Directory which also does event booking, but it's not a dedicated event component do it didn't give all the functions Matukio does. I have attached a screenshot of their discount setup page - matukio04.jpg. A and B above is how they handle it with theirs, plus they also have a normal coupon too as Matukio does.
As a (maybe) quick workaround for scenario A, it may be easier to add code to the coupon functions which allows for an extra parameter to be added to a coupon that detects # of tickets selected and applies a "hidden" coupon code to reduce the ticket cost. So, allow us to set a per ticket discount after "x" tickets of "x"5 or "$x". Have the component check with an if, else (if $ticket_number <2 $cost-->$tciket_cost-$discount, else... normal price). Yes, horrible code; I'm no coder, but hopefully you get the idea. Hikashop has this function where you can select to have a discount applied automatically. Hope that all helps and makes sense.
13. I did put the terms text in that box. Where/when does it show up? It doesn't show on the 1st page where the user enters their details.
Sorry this was such a big list - glad some was already on the drawing board.