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

Booking meta reassigned to wrong product after booking edit, if order contains more than one booking/accom product #318

Open
2 tasks
rtpHarry opened this issue Nov 26, 2022 · 0 comments
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.

Comments

@rtpHarry
Copy link

I think this is an issue with the parent Woocommerce Bookings Plugin to be honest, but that repo seems to be private so there doesn't seem to be anywhere for developers to submit issues for it?

The issue is that if I make a booking with more than one booking / accommodation type:

image

Then try to edit one of the bookings (I'll edit the status of booking 16633 for example, to set it back to unpaid):

(Clicked view booking > {set status to unpaid} > save booking, then click the "linked to order" link to go back)

image

See it is now attached to the wrong product, and stays that way (as in it's not just a ui glitch. Generated invoice PDF's, emails, etc all show it).

However if you click into it then it still thinks it's product is the correct one:

image

It still says the booked product is tamworth hut (the accom product) even though its displaying in the main order view as being an item meta of "rewilding your garden".

And its not just defaulting to the top one either. I just edited the "rewilding your garden" meta, and on save, that has now switched over to the "tamworth hut" one, so they are both now inverted:

image


  • Issue assigned to next milestone.
  • Issue assigned a priority (will be assessed by maintainers).
@vikrampm1 vikrampm1 added priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug. labels Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.
Projects
None yet
Development

No branches or pull requests

2 participants