This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 8:00 – 15:00 | 8:00 – 15:00 | 8:00 – 15:00 | 8:00 – 15:00 | 8:00 – 15:00 | - |
- | 16:00 – 17:00 | 16:00 – 17:00 | 16:00 – 17:00 | 16:00 – 17:00 | 16:00 – 17:00 | - |
Supporter timezone: Europe/Rome (GMT+02:00)
This topic contains 13 replies, has 2 voices.
Last updated by Alejandro 1 year, 8 months ago.
Assisted by: Alejandro.
Author | Posts |
---|---|
September 25, 2023 at 3:16 pm | |
svenD-9 |
Hi there, |
September 25, 2023 at 4:44 pm | |
September 26, 2023 at 10:33 am #14465807 | |
svenD-9 |
Hello again, for everyone out there: The problem: WPML doesn't set the cookies in the dashboard. We've figured out that the issue appears when home URL and site URL are different. In our case it looked like: Since the path for the cookies differ and they'll be set in the frontend using /de/ instead of /, they won't work in the backend and lead to the described issue. Additional problem: The wp-translation_dashboard_filter cookie doesn't work as well, so we currently cannot filter in the translation management for example to easily create translation jobs. |
September 27, 2023 at 8:06 am #14471169 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Hello! You mention that the site and home URL are different and your example includes the language which should not happen. can you please let us know if that's intentional? I'm saying this because that is not normal and should never be added at all that way. i'm trying to recreate the problem with a different setup, similar to your but with a correct and valid scenario since this one will definitely not work (And could even create redirection issues or other possible errors). Can you let me know about this so i can understand better why are you using it this way? ( WPML doesn't really do this to your site). |
October 2, 2023 at 11:01 am #14497387 | |
svenD-9 |
Hi! Yes, that actually is intentional. We've shipped the website with a "/de" site URL so we can serve German in the future with /de as language path when WPML is running. I'm sorry for the confusion, you can simply exchange "de" with "something" and get the same results. |
October 2, 2023 at 12:49 pm #14498135 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
That setup could five you issues and could be related to this cookie issue as well. in this case, the path should be the normal root, without the "/de" part and then you can do the following: https://wpml.org/documentation/getting-started-guide/language-setup/directory-default-language/ This would create unexpected issues (you could run into redirection issues as well because of this setting). Could you try that out and let me know if then the problem goes away? |
October 10, 2023 at 2:41 pm #14551591 | |
svenD-9 |
I'm sorry for the confusion. We actually did figure this out already as mentioned here https://wpml.org/forums/topic/wpml-cookies-doesnt-created-on-the-site-dashboard/#post-14465807 We can live with the problems, because we will eventually change the configuration. Unfortunately it gives us a hard time and we still think this is a valid configuration option, especially for our use case. Since WordPress, the underlaying foundation, provides this configuration option, WPML should either explicitly tell users that problems will occur since the cookies won't be set correctly (for now we've only discovered two places, where this breaks things) or try to fix this behavior. A simple warning in the backend when this configuration is detected would've helped and saved a lot of effort debugging this issue. Please get back to me, if a developer is looking into it and creates a quick fix, so we can smoothly transition to ultimately deliver our website in multiple languages. |
October 10, 2023 at 2:45 pm #14551689 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
I'll consult this case with a developer to see what we can do. i'm sure that we won't be able to handle a scenario where the root has a language code that is also enabled in WordPress but i want to make sure it's this specific scenario that creates the cookie situation because if say, you were using site.com/somethingelse as the root and the cookie wasn't set, then i believe that should NOT be happening and it could be seen as a bug. I'll consult it better with a developer and run a few tests and i'll come back to you afterwards, ok? |
October 10, 2023 at 2:50 pm #14551739 | |
svenD-9 |
That'd be great, but I thought this was already the consensus with the previous supporter I had the initial chat with. Thank you! |
October 10, 2023 at 3:42 pm #14552205 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Back then the case got stopped because of the directory set to a language code which is something not compatible with us. it may be that more was discussed and this is what i'm finding out, so don't worry i'll let you know as soon as i have more infomation about this 🙂 |
October 11, 2023 at 7:54 am #14556131 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Would it be possible for you to create a clone of your staging site but using another subdirectory as your website address value? something different than the code? Our developers would like to test a few things on your site when the website address is different (as i explained we don't nor won't support this current setup). I have enabled the credential fields so you can allow us access to this new staging site and we'll try to see what we can do to help you out. Regards. |
October 12, 2023 at 9:31 am #14564207 | |
svenD-9 |
It's as simple as setting up a fresh WordPress with WPML and this kind of setting set up. You'll see that the Cookies will only be set on the frontend with the /something path. I've tested exactly this with literally "/something" as additional path. |
October 12, 2023 at 11:10 am #14565491 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
Hey quick question, can you send me a copy of your wp-config.php file but remove the sensitive data like salts and DB data? Please leave the rest as it is and if you want you can check for define('COOKIEPATH', '/'); or at least for the "COOKIEPATH" value. i suspect the problem lies here. Please let me know what your value is. |
October 12, 2023 at 12:11 pm #14565931 | |
svenD-9 |
It's a default wp-config.php, as mentioned before I've tested this with a clean WordPress installation and only installed WPML. But, thank you very much for the hint. In my test environment the following define('COOKIEPATH', ''); define('SITECOOKIEPATH', ''); solves the issue, but I don't know if it breaks other things. |
October 12, 2023 at 1:52 pm #14566709 | |
Alejandro WPML Supporter since 02/2018
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00) |
well, that code basically will cause the cookies to be applied for the entire domain name rather than just for the subdirectory which i believe is something that you want to have in this particular scenario. it will definitely not break anything since it's actually a trick people use, mainly in multisites. |
The topic ‘[Closed] WPML cookies doesn't created on the site dashboard’ is closed to new replies.