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

Issue with Tour Date Syncing from Wetu #158

Open
1 task
ashleyshaw opened this issue Oct 9, 2024 · 0 comments
Open
1 task

Issue with Tour Date Syncing from Wetu #158

ashleyshaw opened this issue Oct 9, 2024 · 0 comments
Labels
[Status] Needs Dev Ready for, and needs developer efforts [Type] Bug An existing feature does not function as intended

Comments

@ashleyshaw
Copy link
Member

  • Tour Date Syncing Bug from Wetu

    Describe the bug
    Tour dates imported from Wetu do not consistently match the updated schedules available on the Wetu platform.

    To Reproduce
    Steps to reproduce the behavior:

    1. Go to the Tour Operator section in WordPress.
    2. Click on the Wetu Importer tab.
    3. Perform a data sync for the tour dates.
    4. Review the imported tour dates and compare them to Wetu's data.

    Expected behavior
    The imported tour dates should accurately reflect the latest schedule updates from Wetu.

    Screenshots
    If applicable, add screenshots to help explain your problem.

@ZaredRogers add images after testing

Desktop (please complete the following information):

  • OS: [e.g. Windows, macOS]
  • Browser: [e.g. Chrome, Firefox]
  • Version: [e.g. 95.0]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone 12, Samsung Galaxy S21]
  • OS: [e.g. iOS 14, Android 11]
  • Browser: [e.g. Safari, Chrome]
  • Version: [e.g. 14.1]

Additional context
This issue may affect other date-based data imports and requires frequent manual corrections.

@ashleyshaw ashleyshaw added [Type] Bug An existing feature does not function as intended [Status] Needs Dev Ready for, and needs developer efforts labels Oct 9, 2024
@ashleyshaw ashleyshaw modified the milestones: 2.0.0, 2.1.0 Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Needs Dev Ready for, and needs developer efforts [Type] Bug An existing feature does not function as intended
Projects
Status: Needs Triage
Development

No branches or pull requests

1 participant