-
Notifications
You must be signed in to change notification settings - Fork 713
Use PANTHEON_HOSTNAME when setting SERVER_NAME #9478
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
base: main
Are you sure you want to change the base?
Conversation
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-9478-documentation.appa.pantheon.site |
Reassigning to @jazzsequence to better understand the issue and it's relation to pantheon_hostname |
Refactored recommendations to use See: |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-9478-documentation.appa.pantheon.site |
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-9478-documentation.appa.pantheon.site |
Fixes #9424
Summary
WordPress Plugins and Themes with Known Issues - Use
PANTHEON_HOSTNAME
when setting SERVER_NAME across all instances