Opened 11 months ago
Last modified 2 months ago
#60318 new defect (bug)
Update URI: false - sometimes not working
Reported by: | apedog | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | |
Component: | Plugins | Keywords: | |
Focuses: | Cc: |
Description
I've recently copied and modified a small plugin from wp-org for my own need.
I've set the Update URI: false
header. However on the Plugins page, the View Details link still leads to the original plugin and the Enable/Disable auto-updates button link is present.
I've changed the main plugin file name to something else, but not the directory name, however the View Details link is still present.
I've removed the readme.txt
file and that seems to do the trick.
To test this, I've then tried restoring the readme.txt
file, removed the Update URI: false
header and renamed the plugin file to its original wp-org name. The View Details link was NOT restored.
However, changing the plugin file name to something new again DID restore the View Details link. The experience has been very inconsistent throughout.
I'm running a LocalWP installation on Windows 10.
WordPress 6.4.2
PHP 8.2
VSCode editor.
This is not a long-term problem for me as I intend to rename the plugin file AND directory name, but thought I'd report this bug for the record.
Change History (3)
#1
in reply to:
↑ description
;
follow-up:
↓ 2
@
7 months ago
#2
in reply to:
↑ 1
@
7 months ago
Replying to siliconforks:
WordPress stores update information in the transient cache. So if you change/add/remove the
Update URI
header, that may not take effect immediately.
I did not know this. That seems a reasonable explanation for the shenanigans.
So it's not a bug? It feels bug-ish. Not a great experience.
Also, thanks for the CLI solution.
Replying to apedog:
Are you sure this isn't a caching issue? It sounds a lot like a caching issue.
Note that WordPress does not check/recheck for updates every time the Plugins page is loaded - it stores update information in the transient cache. So if you change/add/remove the
Update URI
header, that may not take effect immediately - you will have to wait for the transient to expire. If you want it to take effect immediately, I think this WP-CLI command will work: