#36923 closed enhancement (invalid)
Create filter for $details_url in wp_theme_update_row()
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Upgrade/Install | Keywords: | has-patch |
Focuses: | administration | Cc: |
Description
Currently, this function populates data for the details overlay for theme updates. Usually what is populated is the .org page for the theme. If a theme is not hosted on .org the overlay displays as a large white space blocking the screen with no information.
My use case is for updater code that populates themes_api() and so will have relevant information but no ability to display it. By allowing a filter here a developer may change the parameters of $details_url and have the ability to provide useful information to their users.
Thanks.
Attachments (5)
Change History (14)
#3
@
9 years ago
I'm not sure this filter is needed (unless I'm missing something obvious), as if you're filtering the update response to add non-w.org-hosted plugins, then you'll be able to set the url
field (which this filter is filtering) to whatever you want.
#4
@
9 years ago
In multisite, the current behavior loads a page from the theme directory that doesn't appear to have a close box and fills a majority of the screen. Perhaps, this is another issue?
For a non .org hosted theme it looks like this.
Filtering $details_url also allows me to filter the size of the popup and actually display some information.
The only difference between the 2nd and 3rd images is having the filter in place.
I also get this error.
Refused to display 'https://bitbucket.org/afragen/test-bitbucket-child?' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.
and an empty iFrame results. Changing the url
field fixes this.
#5
follow-up:
↓ 6
@
9 years ago
I'm not sure this filter is needed (unless I'm missing something obvious), as if you're filtering the update response to add non-w.org-hosted plugins, then you'll be able to set the url field (which this filter is filtering) to whatever you want.
That's it exactly.
#6
in reply to:
↑ 5
@
9 years ago
Replying to afragen:
I'm not sure this filter is needed (unless I'm missing something obvious), as if you're filtering the update response to add non-w.org-hosted plugins, then you'll be able to set the url field (which this filter is filtering) to whatever you want.
That's it exactly.
I think you're missing the fact that $current->response[ $theme_key ]['url']
can be set by your updater code.
The only thing this filter achieves is filtering the width/height of the thickbox.
Just some extra stuff removed from the diff.