#6063 - Content translations broken; installer fails on either step 7 or 9 when enabled
-
By PDStig
- Added
- 9 views
| Identifier | #6063 |
|---|---|
| Issue type | Trivial issue (does not break functionality) |
| Title | Content translations broken; installer fails on either step 7 or 9 when enabled |
| Status | Completed |
| Tags |
Roadmap: v11 (custom) |
| Handling member | PDStig |
| Version | 11 beta8 |
| Addon | core |
| 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. |
| Steps to reproduce | |
| 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. |
| Funded? | No |
| Commits |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
The issue was how $HAS_MULTI_LANG_CONTENT was being set, especially in multi_lang_content().
This hotfix addresses the issue. While not widely tested yet, a full install of v11 with content translations on seems to be working.