|
Cristi Constantin
|
June 2, 2014 at 4:47 pm
Currently it is not possible to visually distinguish between the currently selected seat and other unavailable seats. They use the same visual representation and it makes it very hard to understand where you will be seated, by looking at the chart.
|
|
Dean
|
June 3, 2014 at 2:09 am
Hi,
Is this on the front end? Available seats will be grey and unavailable ones in green (perhaps not the best colours, but they are quite different visually).
|
|
Cristi Constantin
|
June 3, 2014 at 2:21 am
Yes, in front end. For me they all display with green and with a check sign on them.
|
|
Dean
|
June 3, 2014 at 2:23 am
Can you provide a link to an example please? Also what version of EE and Seating Charts are you using?
|
|
Cristi Constantin
|
June 3, 2014 at 2:38 am
link: https://planul-meu.ro/evenimente/procesator/?ee=5
EE version: 3.1.36.5.P
seating plugin: v1.2.1-alpha
|
|
Dean
|
June 3, 2014 at 3:43 am
Ahhh right I misunderstood you.
The issue is that the selected seat and the already taken seats look the same, so if a user goes to change seat, they may not be aware of where their currently selected seat is.
That’s a fair point, not sure what can be done about it now as it will likely need JavaScript modifications, but I will certainly add a feature request for it.
|
|
Cristi Constantin
|
June 3, 2014 at 4:06 am
Could you give me a hint on what should be changed? I would like to implement this for myself.
Thank you.
|
|
Dean
|
June 3, 2014 at 4:53 am
Hey,
Right this is very hacky but it seems to work. http://pastebin.com/fMpPW9U1 (it’s a replacement for seating_chart.js) do a search for dean and you will find the 2 code blocks. You will also need to add some CSS in as well (the class is .dean). I added it to the seating chart but you should be ok adding it elsewhere.
All this does is store the seat id and assign a class to it that colours it differently.
As always, back up your files first. This is also just an example so USE AT YOUR OWN RISK as I am not that good a jQuery developer.
screenshot http://take.ms/IRQ1h
|
|
Cristi Constantin
|
June 3, 2014 at 4:09 pm
Works well for a single ticket, but doesn’t provide correct information when choosing multiple tickets (group participant feature). It has to be caused by using attr() and/or prop() which look just for the first instance. Any idea as to take it further? It seems to be a good start – what you proposed.
Thank you.
|
|
Dean
|
June 4, 2014 at 5:58 am
Hi Cristi,
Unfortunately unless it’s merely my lack of experience with jQuery, it looks like it may take some heavy modifications to make it work with multiple bookings, as I think it will somehow need to store the id for each one.
|
