View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 6063 | Composr | core | public | 2024-11-18 02:16 | 2025-02-27 20:58 |
| Reporter | PDStig | Assigned To | Chris Graham | ||
| Priority | normal | Severity | major | ||
| Status | assigned | Resolution | open | ||
| Summary | 6063: Content translations broken; installer fails on either step 7 or 9 when enabled | ||||
| Description | Content translations causes steps 7 or 9 to fail on the installer. If it fails on step 7, it's because Composr tried to look up a string get_translated_text on g_name when multi_lang_content is enabled (this may have been a server cache issue, though). If it fails on step 9, it's because when installing custom fields for billing address, it tries to query_select_value_if_there on '*.text_original' field names. These do not exist. | ||||
| Additional Information | I spent too much time trying to figure this out; it exceeds cost effectiveness. So I'm assigning to Chris. Until fixed, Composr v11 will have content translations disabled, and v10 sites with it enabled cannot upgrade to v11. | ||||
| Tags | Roadmap: v11 | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
