CiviCRM Community Forums (archive)

Setting maximum counts on price set items for events has definitely come up as something some folks need. I'm not aware of anyone working on code for this at the moment. If you're interested in developing something that could be integrated into the core codebase at some point - a good starting point is to write a blog post describing the requirements and describing your planned approach (both data model changes and proposed user interface for admin side and for registrants).

If you want to move ahead on this - let me know and I'll make sure you have permissions to post a blog on civicrm.org

(You might want to check out Chris Iven's blogs on his work integrating the "price set" concept into Memberships: http://civicrm.org/blog/4679)

Spoken to my team of people. You've helped them before. Reekingofrandomness (Rob) and andrewbelcher are in my team of developers. Me (Jamie) and Rob are just students who used to work together on a church community based website, recently we've been employed for a Thai Boxing Gym which is very exciting. Anyways, from an academic point of view I just love Open-source stuff so I'm hoping anything they pay us to make that isn't already out there, we're hoping we can turn those things into patches and modules. I might post a list of the proposed changes we're making to CiviCRM in the near future so people can tell us if its worth getting it usable to others.

So before we post anything on any blogs. We'll use this thread to discuss our design brief. We want to make two seperate modifications (Please note I'm not a web developer so I'm sure andrew and Rob will correct me on things as we go along!)

1) Seating Plan upload
Add a field that allows easy upload of a seating plan (an image file). And add something in the template that makes it each to change how the seating plan is displayed. (Seatings plans can be whatever you like, but we'll put numbers on them to show the different areas, its likely that this will be displayed in the purchasing tickets screen, not in the event info screen)

2) In the Price Sets. In the Page Edit a price set. Next to Price will be another column called "Number" (people can suggest something better) where the number of tickets can be set. I thought this should not be in "Edit price numbers" so that different groups could still pay different amount but would deduct from the remaining tickets.

-(Maybe here it would be good to have another column called "Tickets Remaining")
- All the current features that apply to "Maxiumum number of participants" should apply to tickets. Don't know exactly what that is. But obviously that means a ticket should count as "Sold out" and not be selectable for a user. If there are waiting list features this should apply to individual tickets, not whole events. Refunds and cancellations should apply to individual tickets not events. And anything else we can find.
- I don't know if this should completely replace "Maximum number of Participants" or work alongside it.

-We will then find a way of reporting ticket sales using Interamind's reporting tools for VirtueMart (Although obviously that is specific to us)


Rob and Andrew - Want to talk about how this will be done technically?

2) In the Price Sets. In the Page Edit a price set. Next to Price will be another column called "Number" (people can suggest something better) where the number of tickets can be set. I thought this should not be in "Edit price numbers" so that different groups could still pay different amount but would deduct from the remaining tickets.

-(Maybe here it would be good to have another column called "Tickets Remaining")

At the moment, we have it so that you can set a maximum number of tickets available on the Price Field edit form. It's probably not appropriate to have a 'Tickets Remaining' column on the price set page because Price Sets should probably be specific to venues rather than to specific events

The next job is to get the front end of events relying on the price set information rather than anything else.


And yeah Dave, I agree with you about deriving the number of tickets remaining. It's just about how and where we display it.

Hi Jamie - responses inline:

We've got a demo of it working in our back-end, working on the styling now. Do you think we could have access to a blog and post our involvement in that blog as you suggested?

Cool! I've updated your civicrm.org login so you can now post blogs :-) Details of the implementation (and screenshots too) would be great.

I don't know if you can do this but would it be possible for us to have access to a branch of the SVN so we could upload our changes directly? Or would you prefer some other method of collaborating on this as we are obviously quite new to the community?

I think the best approach for now is to share the details of your implementation with us / the community and then to submit a patch with your modifications as an issue on the issue tracker.

Finally, we found bits of the developer documentation hard to follow (with regards to hooks and stuff), would you like I to contribute to that? To be honest I think we'll just post suggested documentation into the forum (especially because we're only looking at civicrm with joomla at the moment) so it might be better for you guys to look at our code before we suggest any documentation.

I would just get an account on the doc wiki and make changes / improvements as needed. If there's an area where you're not sure "how it works" or want clarifications prior to documenting - then it makes sense to use the forum.

As far as I know, each Drupal user has their own blog. So either they can post from your login ("bad behavior" - but ok I guess if you trust them) - or let me know and I can give them each permission to post their own blogs.

Here's a screen of the back end:

(http://i642.photobucket.com/albums/uu150/rlmumford/screenshot_priceSet_availability_mo.jpg)

Would this module be able to display who has bought the tickets at each table so that during the registration process a person may see who they will be sitting with? I imagine that this would need to be an option when registering so if they don't want their name displayed then it won't show up. This way people can choose to sit with their friends unless their friends don't want them to.