-
-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
status:needs-designEarly execution signal (triage queue for design)Early execution signal (triage queue for design)status:needs-devEarly execution signal (triage queue for engineering)Early execution signal (triage queue for engineering)status:needs-more-infoMissing details to proceedMissing details to proceed
Milestone
Description
New API Field - Tour Galleries Support in Wetu Importer #170
Overview
The Wetu Importer needs to be extended to support a new field within the Wetu API for Tour Galleries. This field will allow tours to include media assets, specifically from the "Landing Page Media" section in Wetu, which is provided via the cover_images field in the API.
Task
Extend the current Wetu Importer functionality to process and import the "Landing Page Media" data into a newly created Tour Gallery field within WordPress. This will allow tours to showcase galleries with media assets synced directly from Wetu.
Development Requirements
-
API Integration:
- Update the Wetu API integration to retrieve the
cover_imagesfield associated with a tour’s "Landing Page Media." - Ensure that the API data for the
cover_imagesis correctly mapped to the corresponding gallery field in WordPress.
- Update the Wetu API integration to retrieve the
-
Backend Design:
- @ZaredRogers to provide an updated backend design for how the Tour Gallery field will be structured and displayed within the Tour Operator section of WordPress.
- Ensure that the Tour Gallery field can accommodate multiple images, as provided by the
cover_imagesdata.
-
Data Handling:
- Create or extend a function that processes the
cover_imagesfrom the Wetu API. - The function should save the
cover_imagesdata into the Tour Gallery field within the WordPress database for each tour. - Handle any validation or data integrity checks to ensure only valid images are stored.
- Create or extend a function that processes the
-
Gallery Display:
- Ensure that the imported gallery images are displayed correctly within the WordPress admin interface and on the front end.
- Use the WordPress media gallery or custom gallery implementation to display the images in a user-friendly manner.
Steps to Implement
-
API Update:
- Add a call to the Wetu API to fetch the
cover_imagesfield. - Extend the data mapping logic in the importer to map
cover_imagesto the new Tour Gallery field in WordPress.
- Add a call to the Wetu API to fetch the
-
Backend Design:
- @ZaredRogers will provide the updated backend design for how the gallery field should be structured and how the images should be saved and displayed.
- Implement the design and ensure it's integrated into the Tour Operator section in WordPress.
-
Tour Gallery Field:
- Create a new custom field in WordPress for the Tour Gallery under each tour.
- Ensure that the field is dynamic and can hold multiple images as needed.
-
Sync Functionality:
- Modify the sync functionality to process and import images from the
cover_imagesAPI field into the new gallery field during the sync process.
- Modify the sync functionality to process and import images from the
-
Testing:
- Test the functionality by performing a data sync for tours and verifying that the gallery images from Wetu are imported and displayed correctly in WordPress.
Additional Context
- API Reference: The
cover_imagesfield from the Wetu API provides the images used on the tour's landing page and should be saved in the corresponding Tour Gallery field. - This functionality will allow tours to display rich media galleries directly from Wetu, enhancing the user experience by automating media content imports.
Completion Criteria
- The Wetu Importer can now retrieve and store
cover_imagesfrom the Wetu API into a custom Tour Gallery field. - The imported media is displayed properly in the WordPress admin interface and on the front end.
- Syncs with Wetu are tested to ensure data consistency and proper gallery rendering.
Metadata
Metadata
Assignees
Labels
status:needs-designEarly execution signal (triage queue for design)Early execution signal (triage queue for design)status:needs-devEarly execution signal (triage queue for engineering)Early execution signal (triage queue for engineering)status:needs-more-infoMissing details to proceedMissing details to proceed
Type
Projects
Status
📥 Needs Dev