Skip to content

Fix: Update get_delete_post_link() to support post types with multiple _edit_link placeholders#9952

Open
Debarghya-Banerjee wants to merge 2 commits intoWordPress:trunkfrom
Debarghya-Banerjee:fix-61716/update-get_delete_post_link
Open

Fix: Update get_delete_post_link() to support post types with multiple _edit_link placeholders#9952
Debarghya-Banerjee wants to merge 2 commits intoWordPress:trunkfrom
Debarghya-Banerjee:fix-61716/update-get_delete_post_link

Conversation

@Debarghya-Banerjee
Copy link
Copy Markdown

@Debarghya-Banerjee Debarghya-Banerjee commented Sep 18, 2025

Trac Ticket: Core-61716

Problem

  • get_delete_post_link() assumes _edit_link contains only a single placeholder (e.g. post.php?post=%d).
    Gutenberg post types such as wp_template and wp_template_part define _edit_link with multiple placeholders (e.g. site-editor.php?postType=%s&postId=%s&canvas=edit).

  • This mismatch causes sprintf() to throw an ArgumentCountError when generating delete links.

Solution

  • Update get_delete_post_link() to dynamically count placeholders in _edit_link and adjust the arguments passed to vsprintf().

  • This ensures compatibility with both classic and Gutenberg CPTs, prevents fatal errors, and future-proofs the function against additional placeholders.

@github-actions
Copy link
Copy Markdown

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 debarghyabanerjee.

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

@github-actions
Copy link
Copy Markdown

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.

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.

1 participant