You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the notice is ignored, nothing will break, WP Rocket will continue to work normally.
But if the notice is clicked to regenerate the config files, WP Rocket will only regenerate the config file for the domain you clicked the button from. WP Rocket will only work on that specific domain, and not on the other mapped domains. If you deactivate/re-activate WP Rocket, all the config files will be generated.
Enter the /wp-admin/ from the different domains, until you see the admin notice.
Click on the regenerate files button, and see the issue.
Expected behavior
As per Alfonso: we are initially creating the config files correctly, so we should prevent the transient rocket_domain_changed to be triggered if you log in from a different domain that’s defined inside the WPML config
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Describe the bug
On a multi-domain installation using WPML, where different languages are mapped to different domains, whenever one of the translated domain's WP Admin is accessed, this causes the domain change notice to display: https://docs.wp-rocket.me/article/705-changing-domains-migrating-sites-with-wp-rocket#deactivate-reactivate.
If the notice is ignored, nothing will break, WP Rocket will continue to work normally.
But if the notice is clicked to regenerate the config files, WP Rocket will only regenerate the config file for the domain you clicked the button from. WP Rocket will only work on that specific domain, and not on the other mapped domains. If you deactivate/re-activate WP Rocket, all the config files will be generated.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
As per Alfonso: we are initially creating the config files correctly, so we should prevent the transient rocket_domain_changed to be triggered if you log in from a different domain that’s defined inside the WPML config
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Ticket: https://secure.helpscout.net/conversation/2813670834/533998?viewId=2675957
Slack: https://wp-media.slack.com/archives/C43T1AYMQ/p1736355324192949
Temporal solution:
To hide the admin notice with this snippet:
The text was updated successfully, but these errors were encountered: