Here’s a revised version with corrected grammar:
When a page is translated and published, a new focus area translation should be saved to the database.
Known Issues
The Translate extension creates a subpage for the base language of the focus area, triggering a duplication of the focus area in communityrequests_focus_area. This occurs because we store the focus area based on page_id and language (content language), and the Translate extension creates a subpage with a redirect to the original page for the original language.
Acceptance Criteria
- Translations should have a database representation in communityrequests_wishes_translations and communityrequests_focus_area_translations if the Translate extension is enabled.
Derived Requirement
When the Translate extension is enabled, publishing a translated focus area or wish should result in a corresponding translation record being saved in the appropriate database table: communityrequests_focus_area_translations for focus areas and communityrequests_wishes_translations for wishes. Translations must be stored only once, avoiding duplication caused by the base language subpage created by Translate.
Test Steps
Test Case 1: Ensure wish translation is saved in DB when published
- Navigate to a translatable wish page (e.g., Community Wishlist/Wishes/W123) that supports translation.
- Translate the wish content into a different language and publish it.
- ✅❓❌⬜ AC1: Confirm that a new entry is saved in the communityrequests_wishes_translations table for the published translation.
QA Results - Test Beta
| AC | Status | Details |
|---|---|---|
| 1 | ❌ | T396361#11010585 |