[buddypress-trac] [BuddyPress] #3992: Get WP's bumpbot for compressing js/css and incrementing version numbers
buddypress-trac at lists.automattic.com
buddypress-trac at lists.automattic.com
Fri Feb 10 14:21:42 UTC 2012
#3992: Get WP's bumpbot for compressing js/css and incrementing version numbers
--------------------------------------+-----------------------------
Reporter: boonebgorges | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: Core | Version:
Severity: normal | Resolution:
Keywords: dev-feedback needs-patch |
--------------------------------------+-----------------------------
Description changed by boonebgorges:
Old description:
> See #WP1952.
>
> WordPress recently introduced the 'bumpbot', a sister script to potbot
> that regularly checks for changes to .dev.css/.dev.js files, bumps
> version numbers if necessary to bust browser caches, and compresses them.
>
> nacin has offered to help set up bumpbot for BP. Before we can move
> forward, we have to regularize our version strings. We're currently using
> date strings like '20120210', at least in bp-default's main css/js files.
> WP's opted to use $wp_version throughout (removing manual version
> specifications when registering scripts, thereby falling back on
> $wp_version; see http://core.trac.wordpress.org/changeset/19621).
>
> nacin reasonably suggests that we do something similar. Switch our js/css
> version number to $bp->version, and have the bumpbot autoincrement it
> here http://buddypress.trac.wordpress.org/browser/trunk/bp-loader.php#L55
>
> No time at the moment to write a patch, but I can look at it later. Any
> objections?
New description:
See #WP1952.
WordPress recently introduced the 'bumpbot', a sister script to potbot
that regularly checks for changes to .dev.css/.dev.js files, bumps version
numbers if necessary to bust browser caches, and compresses them.
nacin has offered to help set up bumpbot for BP. Before we can move
forward, we have to regularize our version strings. We're currently using
date strings like '20120210', at least in bp-default's main css/js files.
WP's opted to use $wp_version throughout (removing manual version
specifications when registering scripts, thereby falling back on
$wp_version; see http://core.trac.wordpress.org/changeset/19621).
nacin reasonably suggests that we do something similar. Switch our js/css
version number to $bp->version, and have the bumpbot autoincrement it here
http://buddypress.trac.wordpress.org/browser/trunk/bp-loader.php#L55.
We'll have to pass our version manually to wp_register_script(), of
course.
No time at the moment to write a patch, but I can look at it later. Any
objections?
--
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/3992#comment:2>
BuddyPress <http://buddypress.org/>
BuddyPress
More information about the buddypress-trac
mailing list