Zum Inhalt springen Zur Seitenleiste springen

Dies ist das technische Support-Forum für WPML – das mehrsprachige WordPress-Plugin.

Mitlesen können alle, doch nur WPML-Kunden können hier Fragen veröffentlichen. Das WPML-Team antwortet im Forum an 6 Tagen pro Woche, 22 Stunden am Tag.

Dieses Thema enthält 1 Antwort, hat 2 voices.

Zuletzt aktualisiert von Bruno Kos Vor 1 Jahr, 8 Monaten.

Assistiert von: Bruno Kos.

Autor Beiträge
Februar 7, 2024 um 8:08 a.m. #15274859

danielK-155

Dear WPML Support Team,

I am writing to report a persistent issue on my website, versteckter Link, which I believe is related to the WPML plugin's language switching functionality. Our website is set up with German as the default language, and we also offer content in English and Spanish. However, we've encountered a problem that significantly affects the user experience across different language versions of the site.

Issue Description:
Whenever a user navigates to the Spanish or German version of the website and clicks on the main logo with the intention of returning to the homepage, the website automatically redirects them to the English version of the homepage instead of staying within the same language context. This behavior is inconsistent with our goal of providing a seamless multilingual experience, as it forces users to manually select their preferred language again after being unexpectedly switched to English.

Expected Behavior:
Clicking on the main logo from any language version of the site should redirect the user to the homepage of that same language. For instance, if a user is browsing in Spanish and clicks on the logo, they should be directed to the Spanish homepage, not the English one.

Troubleshooting Steps Already Taken:

Checked WPML language switcher settings to ensure that they are configured correctly for language switching behavior.
Verified that the website's default language is properly set to German in WPML settings.
Reviewed custom URL structures for language versions to confirm they are set up correctly.
Cleared the website's cache and tested in multiple browsers to rule out caching issues.
Despite these efforts, the issue persists, suggesting that it might be related to how WPML handles language switching when the main logo is clicked.

Request for Assistance:
I kindly request your assistance in identifying and resolving this issue. Could you please provide guidance on how to ensure that clicking on the main logo leads users back to the homepage of the current language rather than defaulting to English? If there are specific settings or customizations within WPML that need to be adjusted, detailed instructions would be greatly appreciated.

Thank you for your attention to this matter. I look forward to your prompt response and am hopeful for a solution that restores the intended multilingual navigation functionality on our website.

Best regards, Daniel Kamp

Februar 7, 2024 um 9:09 a.m. #15275316

Bruno Kos
WPML-Unterstützer seit 12/2018

Sprachen: Englisch (English ) Deutsch (Deutsch ) Französisch (Français )

Zeitzone: Europe/Zagreb (GMT+02:00)

Hi,

Thank you for contacting WPML support!

If I open e.g. Spanish, the logo URL has a trailing slash, thereby redirecting it like this:

>>> <em><u>versteckter Link</u></em>

> --------------------------------------------
> 301 Moved Permanently
> --------------------------------------------

Status:	301 Moved Permanently
Code:	301
Date:	Wed, 07 Feb 2024 08:58:08 GMT
Server:	Apache
X-Pingback:	<em><u>versteckter Link</u></em>
X-Redirect-By:	WordPress
Set-Cookie:	mwai_session_id=65c346215894c
Location:	<em><u>versteckter Link</u></em>
Connection:	close
Content-Type:	text/html; charset=UTF-8

Can you do this:
- Update WPML and its addons to the latest versions https://wpml.org/faq/install-wpml/#automated-updates
- check the theme code or the translation of this logo url (if the logo url is translated), perhaps you set trailing slash within the translation

You could also try setting the redirection (or removing it altogether, so that versteckter Link does not redirect), in case you did this somewhere in the backend.

Regards,
Bruno Kos