[wp-trac] [WordPress Trac] #17816: WordPress in dev environments should update /wp-content/* again
WordPress Trac
wp-trac at lists.automattic.com
Thu Jun 16 12:35:45 UTC 2011
#17816: WordPress in dev environments should update /wp-content/* again
--------------------------------------+------------------------------
Reporter: ocean90 | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Upgrade/Install | Version: 3.2
Severity: normal | Resolution:
Keywords: dev-feedback 2nd-opinion |
--------------------------------------+------------------------------
Comment (by nacin):
Not entirely sure how this should work. Always update themes, that makes
sense. But what about Twenty Ten? (Is it staying in the download package?
Seems like it.) Or future Hello Dolly changes? We want to encourage people
to update via the Beta Tester plugin, so I'd rather keep it as close as
possible to how it works normally.
That said, the theme should always be updated. How can we check if we're
updating to a development version from here? Are we able to check the
transient for response == 'development'? If so, that seems better than
parsing the existing and incoming wp_versions.
We do a $type check in the update code. Perhaps we can make this only
apply to themes, and only the final theme in the array. (If we end up
introducing two themes at once or something, we can always just change
this code.) Or maybe this simply becomes another thing to bump? We already
bump versions in wp-admin/includes/update-core.php. We could also do
$force_reinstall = array( 'twentyeleven' ) and add/remove as appropriate.
(And only force this for development versions.)
Regardless of what we do, let's make it filterable that way the Beta
Tester plugin can add a checkbox or something, if westi wants.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/17816#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list