-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPML Compatibility Bug When Languages Use Different Domain Names #750
Comments
@VR51 Can you give me an example of what a "different domain name" would be? For example, if your primary domain is The reason the cache for the other domain isn't getting cleared is that Comet Cache doesn't know about it. It just knows about the domain you have configured in the WordPress settings. |
Hi raamdev, I kinda guessed the cause would be something along those lines. Not certain it needs to perform rewrites for the multi-domain name feature to work. Certainly makes no edits to .htaccess. I'll explain how the server and WPML are configured: We have two domain names, one for each language:
They are not sub-domains. The hyphens are deliberate. The server is configured to use spanish-example.com as the root domain. english-example.com is an addon domain. Both domains point to the same server space. WPML has an option for setting a domain name to use for the alternate language versions of the site. When a request is made to the server, WPML detects which domain is requested. WordPress serves the requested page. WPML detects whether an alternate language version of the page exists and if one does then WPML displays a link to the alternate language version. The WordPress admin pages are served under the primary domain name. Here is the WPML official explanation: https://wpml.org/faq/server-setting-for-languages-in-different-domains/ Thank you for looking into this. |
@VR51 Ah, thank you very much for that explanation and the great link to the WPML docs. We actually have another issue open (see #608) specifically related to aliased domains and this issue with WPML clarifies the problem a bit more, so we should be able to get this fixed sooner rather than later. I've copied relevant information from this GitHub issue over to the other one; see #608 (comment). Note: If you're interested in testing a beta release of Comet Cache before the next version comes out, please sign-up to be a beta tester here or see Comet Cache → Plugin Updater → Beta Testers to automatically receive Release Candidate updates. |
Thank you Raam. Look forward to that update. Will register as a beta tester later today. |
Referencing internal ticket: https://websharks.zendesk.com/agent/tickets/12400 |
Noting that Comet Cache v160706, which was released several months back, fixed the issue with aliased domains. I believe that resolves the issue described above with WPML. @VR51 Can you confirm? |
Yes and no. Mostly positive. This appears to be resolved but I had a customer approach me last week to say the bug had returned. I'm keeping my eye on it. The bug's revival could have been a temporary quirk. Thanks @raamdev |
@VR51 Thanks for the update. I'll go ahead and close this issue for now then. If you confirm the issue is still there, I'll reopen this issue to investigate further. |
Sounds good to me. Will keep you posted. |
WPML allows admins to configure each language to use a URL that is either:
When the clear cache button is clicked in Comet Cache Pro all caches are cleared for URL formats 1 and 2 but format 3 (different domain name) remains unwiped.
I think the cache does clear itself automatically when it expires (not 100% sure) but the Clear Cache button doesn't do the job when different domains are used per language. Manual deletion of the cache directory does work (lol).
I've tried clearing the cache with the button while logged into the affected language version of the site (2 languages only). Doesn't make a difference. The secondary domain's cache doesn't clear.
As this happens with WPML it might also happen with multisites that use domain mapping. That'll need to be tested.
Thanks guys!
The text was updated successfully, but these errors were encountered: