Fix: Correct site_url handling for custom post types and taxonomies in acf admin #957
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the WordPress admin panel, when viewing the advanced settings for custom post types and taxonomies, the permalink structure is displayed.
However, in environments like Bedrock or when WordPress is installed in a subdirectory such as
/wp,site_url()may include/wp, even though this path is not part of the actual public URL.Example:
get_site_url(): https://example.com/wpget_home_url(): https://example.comThis caused discrepancies in the displayed URLs.
This PR fixes the issue by ensuring the correct URL is used.