Replace trigger_error with wp_trigger_error

[prasadkarmalkar]

In this PR I have replaced trigger_error with wp_trigger_error and for the function name first parameter in wp_trigger_error I have used METHOD and FUNCTION based on either this is in function or class

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

---

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.

[github-actions]

Hi @prasadkarmalkar! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

• PHP Coding Standards
• CSS Coding Standards
• HTML Coding Standards
• JavaScript Coding Standards
• Accessibility Coding Standards
• Inline Documentation Standards

Thank you,
The WordPress Project

[github-actions]

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 hellofromtonya, prasadkarmalkar, rajinsharwar, thelovekesh.

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

[github-actions]

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.

[Rajinsharwar]

Can you please strip all tags before displaying the error?

[thelovekesh]

Hi @Rajinsharwar!

Is there a specific reason to strip HTML tags from triggered error messages? I believe the HTML tags are expected, allowing the front end to render the error messages makeup(e.g. links) appropriately for the user.

Regarding the failed tests, wp_trigger_error() includes the method or function name in the error message, which is causing the tests to fail.

wordpress-develop/src/wp-includes/functions.php

Line 6065 in f1c0e58

$message = sprintf( '%s(): %s', $function_name, $message );

Please note, how function/method name is being appended in the front of error message.

I believe the test cases need to be updated to account for the __FUNCTION__ name prefix if it is being passed to wp_trigger_error().

[hellofromtonya]

Hello and thanks for working on this effort 👋 Some of the changes are in external packages / libraries that are maintained outside of Core, e.g. Requests, PHPMailer, SimplePie, etc.

For this first round of replacements (especially this late in the beta cycle), I'm thinking to only replace within Core's maintained codebase. For these external libraries, discussion can happen whether in their repo (such as with Requests) or within 6.7+ trac ticket.

I'll push a change to this PR shortly that reverts the changes to external libraries. And then review the remaining changes for 6.6 commit consideration.

[hellofromtonya]

I did a force push because it easiest and most clean way for me to restore the changes in external libraries from the original first commit c99f027. Also rebased it on top of the current WP trunk just in case.

[hellofromtonya]

Ready for commit 👍

[hellofromtonya]

Thank you everyone for your contributions 🌟

Committed via https://core.trac.wordpress.org/changeset/58409 to ship in 6.6.