[Resolved] Homepage header and images missing after enabling “Use directory for default language (/de/)” ...

Regarding the image translations — this behavior is not always automatic. WPML’s Media Translation feature only translates image meta information (like titles, captions, and alt text) when those images are used in translatable contexts on the frontend. You can read more about this here:
https://wpml.org/documentation/getting-started-guide/media-translation/#how-to-translate-media-meta-information

If an image does not appear on the frontend or isn’t required in a translated context, WPML will not translate it or consume translation credits unnecessarily.

For the development site — could you please replace URLs such as:
`hidden link`
with
`hidden link...`

Currently, many images still point to the live production site, which makes debugging difficult. You can update these using a plugin like https://wordpress.org/plugins/better-search-replace/.

Also, please note that the URLs in the database should not include the `/de/` path (e.g. `hidden link...`) — they should instead be:
`hidden link...`
Otherwise, this causes greyed-out images in the backend and 404 errors on the frontend.

Lastly, for troubleshooting purposes, would it be okay if I temporarily disable all plugins except WPML (on the staging site)? This will help isolate the issue and confirm whether it’s related to WPML or another plugin conflict.

To troubleshoot this problem (possibly a server issue or a setting), I'll install the Duplicator plugin and generate packages for further debugging purposes. I'll ensure to exclude all media files to maintain a minimal package size.

You can find more information about the process here:
https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#get-help-from-support

Please confirm if this approach is acceptable to you!

I understand your concern — just to clarify, I didn’t mean to blame the server. I only mentioned that the issue might be related to a server configuration or another external factor, and that having a Duplicator package would help us debug it more effectively.

This is part of the recommended WPML troubleshooting process (as outlined here: https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#get-help-from-support
).

Could you please confirm if this approach is acceptable to you so I can proceed?

Just to clarify — theme authors can state that their product is “compatible with WPML”, but unless it’s listed in our official compatibility directory, that means it hasn’t been formally tested or approved by our team. The Nexis theme isn’t currently listed there, so I can’t confirm official compatibility.

At this stage, I’m not focusing on the theme itself, but rather trying to identify where the issue originates. Creating a Duplicator package is the standard step we use in such cases, as it allows us to reproduce the problem in a controlled environment and confirm whether it’s related to the theme, a plugin, or something else.

Could you please confirm if I can proceed with generating the Duplicator package?

That’s perfectly fine — please let me know if the theme’s support team shares any updates.

In the meantime, if they need us to verify anything on our side, we’ll still need a Duplicator package to reproduce and debug the issue properly. Without it, we won’t be able to proceed with any technical investigation.