Skip to content

Get transient force parameter#7299

Open
JUVOJustin wants to merge 3 commits intoWordPress:trunkfrom
JUVOJustin:get-transient-force-parameter
Open

Get transient force parameter#7299
JUVOJustin wants to merge 3 commits intoWordPress:trunkfrom
JUVOJustin:get-transient-force-parameter

Conversation

@JUVOJustin
Copy link
Copy Markdown

This PR introduces a new optional parameter to get_transient and get_option as well as get_site_transient and get_{site,network}_option. However, it should be fully backwards compatible.

The force parameter is passed through all of these functions. In case of transients, the parameter is also passed to the timeout transient.

Trac ticket:


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.

Justin Vogt added 2 commits September 5, 2024 15:11
This update introduces an optional 'force' parameter to both `get_option` and `get_transient` functions for bypassing the cache when retrieving values. This enhancement ensures that the most up-to-date data is fetched directly from the database when needed.
Updated `get_site_option`, `get_network_option`, and `get_site_transient` functions to include a parameter for forcing uncached option retrieval. This ensures options can be fetched without relying on cache when necessary.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 5, 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 helias10.

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

github-actions bot commented Sep 5, 2024

Hi @JUVOJustin! 👋

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:

Thank you,
The WordPress Project

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 5, 2024

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