Problem: If you're experiencing an issue where the string 'Type' in the property search form is not translating on the frontend despite being marked as 'Complete' in WPML String Translation, and you have already scanned all theme and plugin files, cleared the cache, and synchronized the string tables, follow these steps for a possible solution. Solution: 1. Confirm that the WPML and PHP memory limits are at least 128M; increase to 256M if necessary. 2. Rescan theme and plugin files, clear all caches, and synchronize string tables again. 3. Delete and re-register the 'Type' string via WPML String Translation. 4. Search exhaustively in Admin Texts Translation under all relevant domains (e.g.,
theme_mods_homelengo
,
homelengo_options
). 5. Examine Elementor Pro widget/template for manual/auto field label input, including translation of its templates. 6. Validate all string translation entries for 'Type' across multiple domains (theme, plugin, acf-field-group, admin_texts). 7. Verify and enable "Auto register untranslated strings"; revisit the frontend in both languages. 8. Review for theme-specific implementation quirks: Confirm how the theme outputs the 'Type' field label, searching for hardcoded, non-translatable output or JS/HTML overrides. 9. Check for localization issues (e.g., improper use of translation functions like
__()
or
_e()
, or outputting raw strings outside translation context). 10. Manually inspect frontend output and theme template files related to property forms, focusing on localization logic for the label. Do not repeat string rescanning, cache clearing, admin texts review, or memory limit increases.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: The client is experiencing a 500 Internal Server Error when accessing translated versions of their website in languages other than the main language (Spanish). This issue occurs specifically with URLs like /nl/, /fr/, /de/, etc. The error does not affect the default Spanish pages. The problem seems to be related to the Homelengo Real Estate theme, which triggers a PHP fatal error when WPML is active or when visiting pages in secondary languages. Additionally, there are issues with internal redirects and REST endpoints used by Contact Form 7.
Solution: We recommend the following steps to troubleshoot and potentially resolve the issue: 1. Contact the hosting provider to check the server error logs for more specific details about the error. 2. Disable the Homelengo Real Estate theme temporarily to see if the issue persists with a default theme. 3. Deactivate and reactivate WPML and Contact Form 7 to check if the issue is specifically related to these plugins. 4. Review and possibly adjust the .htaccess file to normalize /wp-json with language prefixes. 5. Flush permalinks and caches to ensure no stale settings are causing the issue. 6. If the problem continues, provide the debug log to the WPML support team for further analysis. You can find instructions on how to provide this information here: https://wpml.org/faq/provide-debug-information-faster-support/
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket with us for further assistance.
If this solution does not resolve your issue or seems outdated, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
