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

Unavailable accommodation days appear as available when the "Display visitor's local time" setting is enabled. #417

Open
ankitguptaindia opened this issue Mar 8, 2024 · 0 comments · May be fixed by #430
Assignees
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug.

Comments

@ankitguptaindia
Copy link
Member

Description: Unavailable days appear as available when the "Display visitor's local time" setting is enabled in Bookimg Timezone setting.

Screenshot 2024-03-08 at 3 24 48 PM

Booking.Accoommodation.mp4
Screenshot

Screenshot 2024-03-08 at 3 24 28 PM

Steps to Reproduce:

  1. Create an accommodation product for day booking.
  2. Set "Number of rooms available" to 1 in availability settings.
  3. Navigate to Booking > Setting > TimeZone and check "Display visitor's local time".
  4. Book a room for a day, for example, the 25th of the month.
  5. After successful booking, return to the calendar and note that the 25th appears as green/available.
  6. Click on the 25th and note the error message "There are a maximum of 0 places remaining on 25/03/2024".
  7. Navigate to Booking > Setting > TimeZone and uncheck "Display visitor's local time", and check "Display your local time from WordPress settings".
  8. Open the calendar again and note that all booked days will appear as unavailable.

Expected Result:

Unavailable days should appear as unavailable regardless of the "Display visitor's local time" setting.

Actual Result:

Unavailable days incorrectly appear as available when the "Display visitor's local time" setting is enabled, leading to potential confusion.

@vikrampm1 vikrampm1 added priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug. labels Mar 11, 2024
@faisal-alvi faisal-alvi self-assigned this May 17, 2024
@faisal-alvi faisal-alvi added this to the 1.2.6 milestone May 17, 2024
@faisal-alvi faisal-alvi linked a pull request May 17, 2024 that will close this issue
4 tasks
@dkotter dkotter modified the milestones: 1.2.6, Future Release May 17, 2024
@ankitguptaindia ankitguptaindia added the status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. label Jun 7, 2024
@ankitguptaindia ankitguptaindia removed the status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants