Hello,
Thank you for the additional details.
I understand the situation better now, and I can also see why the issue became confusing after changing the cloned site from **lv.amberglow.lt** to **amberglow.lv** and switching the site's default language from Lithuanian (LT) to Latvian (LV).
From what you described, there are actually two separate issues:
1. Some products not appearing in Elementor widgets when LV is the default language.
2. Incorrect URLs still pointing to old language paths or the previous domain (for example, `/lv/` URLs or references to `lv.amberglow.lt`).
The second issue is not related to WPML translations themselves. It is a consequence of the site cloning/migration process and the domain change. WPML can translate content and manage language URLs, but it cannot automatically update hardcoded URLs that were manually added in Elementor widgets, theme options, custom fields, or other plugin settings.
Regarding the broken site after running the search-and-replace tool, this likely happened because the tool modified values that should not have been changed during the migration. Unfortunately, diagnosing or repairing the effects of a third-party search-and-replace operation falls outside WPML support, and the plugin's support team would be in the best position to advise on recovery options.
For the URL cleanup, I would recommend:
- Restoring a backup taken before running the search-and-replace operation, if available.
- Verifying that the WordPress Address and Site Address are correctly configured.
- Reviewing Elementor templates, widgets, menus, theme options, and custom fields for hardcoded links that still reference the old domain or language structure.
- Resaving the WPML language URL settings and WordPress permalinks after the migration.
As for the Elementor product carousel issue, if that problem still exists after the site is restored and functioning correctly, please let us know which products are missing and whether the issue can be reproduced consistently. We can then investigate that specific WPML-related behavior separately.
I look forward to your update.