Skip to content
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

Initial patch for old files update for WordPress 6.7 #7594

Open
wants to merge 3 commits into
base: trunk
Choose a base branch
from

Conversation

peterwilsoncc
Copy link
Contributor

Trac ticket: https://core.trac.wordpress.org/ticket/62150


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

Copy link

github-actions bot commented Oct 21, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props peterwilsoncc, davidbaumwald, pbiron.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Copy link
Contributor

@dream-encode dream-encode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peterwilsoncc Thanks! Looks good so far! Nice to have an early PR to have other folks review.

We'll rerun the ^D and ^A during the Dry Run to make sure the updates here are still the same.

Copy link

@pbiron pbiron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I compared this list of deleted files/dirs against the list generated by WP_CLI when upgrading from 6.6.2 to 6.7-beta3 and they are consistent.

By consistent I mean that WP_CLI deletes individual files like wp-includes/SimplePie/{dir}/{file} and this patch deletes wp-includes/SimplePie/{dir}.

Copy link

@pbiron pbiron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not necessary, but wouldn't hurt to add a reference to https://core.trac.wordpress.org/changeset/59141 in this comment.

@peterwilsoncc
Copy link
Contributor Author

Proposed commit message:

Upgrade/Install: Update the $_old_files array for 6.7.

Update the array of files to be removed during the upgrade routine for WordPress 6.7. The upgrade of the SimplePie library in [59141] included a significant refactor requiring a number directories be removed.

Props, fixes, etc

@pbiron
Copy link

pbiron commented Oct 21, 2024

Not necessary, but wouldn't hurt to add a reference to https://core.trac.wordpress.org/changeset/59141 in this comment.

I now realize I did something wrong. I meant the above to be "add that reference to comment at the being of the PR that explains about the SimplePie update" ;-)

@peterwilsoncc
Copy link
Contributor Author

I now realize I did something wrong. I meant the above to be "add that reference to comment at the being of the PR that explains about the SimplePie update" ;-)

Yes, that makes way more sense. Pushed. It's early, that's my excuse for misunderstanding ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants