- Updates
COOKIEPATH
andSITECOOKIEPATH
values to/
inapplication.pantheon.php
to resolve cookie-related nonce authentication failures. Previously, the values were set to''
(empty string), which does not allow the cookies to allow authentication within all the paths in a domain. (#164)
- Fixes a bug in the previous update where some WordPress core resources were not available on some single and subdirectory multisite installs. (161)
- Refactors core resource URL filtering and multisite handling. (#157) This resolves an issue where some WordPress core resources were 404ing on single site installs.
- This update primarily fixes consistency issues between the development repository (
pantheon-systems/wordpress-composer-managed
) and the upstream repository (pantheon-upstreams/wordpress-composer-managed
). Most notably, this update removes decoupled packages that were erroneously being added to the non-decoupled upstream (and are not included in this repository). - Fixes issues with subdomain multisite testing (#148)
- Updates automation steps to check PRs for "mixed" commits (#146) and adds handling for merge commits and conflicts (#152)
- Moves cookie settings inside the pantheon environment check (#151)
- Removes code that for handling wp-admin URLs. (#143) This code was not working as intended and testing revealed it to be unnecessary.
- Adds a filter to disable the subdirectory multisite custom wp-content directory warning. (#144) This implements the filter added in the Pantheon MU Plugin in #51.
wp-config-pantheon.php
deprecated in favor ofapplication.pantheon.php
. All previous functionality inwp-config-pantheon.php
moved toapplication.pantheon.php
. (#139)DISABLE_WP_CRON
constant removed fromapplication.php
(andwp-config-pantheon.php
) and moved toapplication.pantheon.php
. (#139) It's possible this change could cause a merge conflict. Accept incoming changes from the upstream or resolve manually.- Cookie domain handling in
application.pantheon.php
to resolve cookie-related login redirect issues on subdomain multisites. (#137) - Updates to
application.php
andcomposer.json
to bring WordPress (Composer Managed) in line withroots/bedrock
v1.24.x. (#134) - Correct WordPress site urls on main sites or single sites to drop the
/wp
in WordPress-generated home links. (#132) This fixes an issue where WordPress-generated links to the primary site always included an unnecessary trailing/wp
. This is handled by a filter inmu-plugins/filters.php
set to priority9
so it can be easily overridden. - Pre-set the WP GraphQL endpoint path to
wp/graphql
if the plugin exists to preserve existing functionality after URL filters above. (#138) - Bump PHP version to 8.2 and DB version to 10.6. (#133) PHP back to 8.1 is still supported but PHP 8.0 support is dropped by the Composer configuration to follow current Bedrock and Sage minimum requirements.
- Update the
update_php
function inhelpers.sh
to update PHP version inpantheon.yml
to 8.1 (or higher) to follow new Bedrock and Sage PHP minimum. (#131) - Silences the check for multisite in the Sage theme install script. (#131) Previously a warning would be shown if the site the script was being run against was not a multisite because the
MULTISITE
constant did not exist. - Adds a check to see if the generated Sage theme exists prior to theme activation. (#131) This change corrects the script's behavior to not attempt to activate the theme if it does not exist.
- Ensure managed WordPress files aren't omitted. (#128) This fixes an issue where some required files were being ignored by version control. Props @araphiel
- Filters core resource URLs for non-main sites in subdirectory multisites. (#130) This fixes an issue where core resource URLs (e.g. to WordPress core JavaScript and CSS assets) were linked incorrectly in subdirectory subsites. This is handled by a filter in
mu-plugins/filters.php
set to priority9
so it can be easily overridden. - Replace
tput
with asave_tput
function inhelpers.sh
. (#129) This fixes an issue where a warning was being displayed in Workflow Logs in the dashboard because thetput
function was not available in the terminal environment. - Adds semver versioning convention to CHANGELOG to track changes easier. (Tags will begin at 1.31.0 rather than retroactively creating new tags.)
- Adds
package.json
file and Playwright tests for functional testing. (#138)
- Filters the configuration file filename on the Setup Network instructions page to use
config/application.php
instead ofwp-config.php
. (#125) - Adds Composer script to update the
platform.php
value to the version of PHP consistent with the version in thepantheon.yml
file. (#127
- Adds a new
PANTHEON_HOSTNAME
constant toapplication.pantheon.php
to be used for configuring multisites. For more information, see our mulstisite configuration documentation. (#119) - Implements
pantheon.multisite.config_contents
filter to correct the multisite configuration instructions (to useConfig::define
instead ofdefine
). - Adds a new
filters.php
mu-plugin for thepantheon.multisite.config_contents
filter and any future filters we might add. - Adds
lint:phpcbf
script to thecomposer.json
.
- Fixed an issue where
WP_HOME
was left undefined and throwing notices into New Relic logs. For more information, see our release note. (#115)
- Updates to the Sage install script to support running the script without prompting for input. Also adds automated test runs of the script on
ubuntu-latest
andmacos-latest
environments. (#113)
- Fixed a bug that failed to prevent a
composer.lock
file from being committed to the repository. (#103) - Removed the
upstream-require
script (#105). This is now available as a standalone Composer plugin:pantheon-systems/upstream-management
- Added a README to the Upstream Configuration path repository with notes about the new
upstream-management
package. (#104)
- Removes the
lh-hsts
plugin requirement from thecomposer.json
file. (#91) - Adds the Pantheon WP Coding Standards to use instead of the default PHPCS/WPCS standards (#94)
- Backports updates from Roots/Bedrock (#90)
- Updates the
post-install-cmd
hook to run a script that checks for the existence of symlinks before attempting to create them. (#98) - Minor improvements to the Sage install process (included in #98)
- Changes the language in comments about appropriate usage of
config/application.php
.application.php
should be used for any site config customizations rather thanwp-config.php
which should not be edited. (#76) - Updates the Sage install script to properly update the PHP version. (#81)
- Updates the Sage install script to force symbolic links rather than attepting to create them on each
composer install
. (#79) - Updates the Sage install script to attempt to fix invalid theme names. (#80)
- Updates the Sage install script to fail hard if
jq
is not found, but provide links to download the executable. (#82) - Fixes an issue that led to failing builds due to an unstaged
index.php
file created by the forced symlinks. (#86)
- Adds Composer Patches plugin (#66)
- Remove Dependabot (#58)
- Resolves issue where updates to commit choosing logic were causing a merge conflict. (#60)
- Adds a Roots Sage install script. See docs/Installing-Sage.md (#61)
- Set minimum-stability to "stable" in
composer.json
(#55) - Add Composer
post-install-cmd
to create symlinks to theweb/wp
directory (for better multisite support) (#56)
- Pull the latest versions of all packages (#36)
- Improved debug log path suggested in
.env.example
(#38) - Get latest WP updates (and other WP-related dependencies) automatically (#40)
- Always pull the latest Pantheon plugins from wpackagist (#45)
- Change from
php_version
tophp-version
in testing matrix (#46) - Additional Lando configuration (#47)
- Fix a typo in
README-internal.md
(#48) - Exclude
.github/
from the deploy script for the upstream repository. (#50) - Also forbid
.github/workflows/ci.yml
from the deploy script. (#51) - Skip commits in deploy process for nonrelease changes (#52 #53)
- Load global .env file even if .env.local is absent (#32)
- Set permalink structure in build-env.install-cms Composer extra property (#30)
- Move Pantheon modifications in application.php (#29)
.gitignore
updates - Reported in the Pantheon Community Slack channel was the fact that the.gitignore
included in this repository did not match the.gitignore
(with commonly-ignored files) in the default WordPress upstream (#24)- Use
.env.local
for local development (#26) - Fixes an issue where Lando was not using.env
files locally. - README updates (#27 and #28) - Adds link to https://github.com/pantheon-upstreams/wordpress-composer-managed for forking, as well as additional guidance about the default branch name for custom upstreams.
- Initial fork from
roots/bedrock
at 1.20.0. See the changelog prior to that atgithub.com/roots/bedrock