Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with multiple Event Types referencing multiple Bat Types #24

Open
qcutter opened this issue Jan 28, 2016 · 6 comments
Open

Issues with multiple Event Types referencing multiple Bat Types #24

qcutter opened this issue Jan 28, 2016 · 6 comments
Labels

Comments

@qcutter
Copy link

qcutter commented Jan 28, 2016

Im working with the most recent github bat_api and bat_drupal. If you I have more than 1 event type the event_unit_reference doesnt maintain the selection for that event. Always is the last reference update to either event. So, I think maybe its using the same table entry for both events (and no way to create a unique entity reference i dont think) This means if I have two events they can both will only point to one event_unit_reference at a time

@istos istos closed this as completed Jan 28, 2016
@qcutter
Copy link
Author

qcutter commented Jan 28, 2016

Will do, its just that I was using the github version and the issue que is not the same format afforded by d.o. nothing was meant by the title sent in this issue. Im just trying to be helpful in the best way I know how. Im not used to troubleshooting or reporting issues, Im more than appreciative of the work going into this project and want to helpful where ever I can.

since I used the the most recent git clones of bat_api and _bat_drupal from 30 min ago, bat_api is labled
7.x-2.x and bat_drupal is 7.x.1.x

In the future I will refrain from !! as i can see how it may come across as offensive :)

Thank you for the hard work and opportunity to contribute what little I can.

Steps to recreate:

  1. Create Two full bookable collections (types, units, events) as specified in documentation.
  2. Go to Event Type -> Manage fields -> event_unit_reference. Go to Edit -> field settings. Take note of configured reference.
  3. Go to Second Event Type -> Manage fields -> event_unit_reference. Go to Edit -> field settings. Change the reference configured to be different from previous event type.
    1. Go back to First Event Type, event_unit_reference and see that it is now configured to what was configured in the second Event Type

@istos istos reopened this Jan 28, 2016
@acrollet acrollet reopened this Feb 12, 2016
@acrollet acrollet changed the title !! Event Unit reference selection broken .. I think :) Issues with multiple Event Types referencing multiple Bat Types Feb 12, 2016
@acrollet
Copy link
Member

@qcutter just to be sure, you've reproduced this issue with beta2 of the BAT library and beta4 of bat_drupal and bat_api?

@qcutter
Copy link
Author

qcutter commented Feb 12, 2016

its pretty straight forward as I explained in detail before, but my use case is i'm trying to use BAT to provide Event Registration and Room Rentals. I have two unit types that will allow me to provide tickets associated with Event Units and Bookings associated with Booking Units. With This in Mind, I created two Type Bundles: Event, Booking. I created Three Event Types: Booking Availability(fixed), Ticket Availability(fixed), and Price(not fixed). I created two additional Units: Booking Unit, Ticket Unit. I went to Event Type: Booking Availability-> Unit:Entity Reference field. Selected Booking Unit for Booking Availability. When i go to Event Type:Ticket Availability-> Unit:Entity Reference field. Booking Unit is already selected. IF I change the Unit here to Ticket Unit, It also changes Event Type: Booking Availability-> Unit:Entity Reference field to Ticket Unit.

@qcutter
Copy link
Author

qcutter commented Feb 12, 2016

I'm running the latest bat and bat_api from github. however I have also ran the latest BAT from D.O when I originally logged the issue. please see my original comments as I spent alot of time detailing the same thing. Ill post a screenshot in a sec.

@acrollet
Copy link
Member

@qcutter thanks much for the explanations. We'll certainly give this a look when we can manage it.

@qcutter
Copy link
Author

qcutter commented Feb 12, 2016

screen shot 2016-02-13 at 8 50 17 am

screen shot 2016-02-13 at 8 49 49 am

screen shot 2016-02-13 at 8 48 35 am

@acrollet acrollet added the bug label Feb 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants