| [8123]
|
johnjamesjacoby
|
BuddyPress: Respect community visibility in direct forum reads.
Apply the group visibility decision to direct forum read checks, including descendants of attached group forums. This keeps REST, embed, redirect, and shortcode reads consistent with BuddyPress while preserving ordinary public forums and access for community members.
In branches/2.6, for 2.6.21.
|
| [8122]
|
johnjamesjacoby
|
BuddyPress: Respect community visibility in direct forum reads.
Apply the group visibility decision to direct forum read checks, including descendants of attached group forums. This keeps REST, embed, redirect, and shortcode reads consistent with BuddyPress while preserving ordinary public forums and access for community members.
In trunk, for 2.7.
|
| [7678]
|
johnjamesjacoby
|
BuddyPress: Respect group forum visibility in queries.
Backport descendant exclusions for unreadable BuddyPress group forums while preserving access to descendants that group members or per-forum moderators can read.
In branches/2.6, for 2.6.19.
|
| [7677]
|
johnjamesjacoby
|
BuddyPress: Respect group forum visibility in queries.
Exclude unreadable descendants of private and hidden group forums from forum and topic queries. Preserve access to descendants that group members or per-forum moderators can read.
In trunk, for 2.7.
|
| [8113]
|
johnjamesjacoby
|
BuddyPress: Respect post visibility in activity.
Prevent activity creation for topics and replies protected by their own or an inherited password, regardless of the current visitor's password cookie. Remove activity when an individual topic or reply becomes protected or unpublished, including posts converted to anonymous authorship.
Restore eligible activity when an individual post becomes publicly visible again, including closed topics. Preserve the revision setting for ordinary edits and exclude anonymous posts from activity creation. This change does not bulk-clean historical activity or synchronize descendants when a forum or site changes visibility.
In branches/2.6, for 2.6.21.
Props ton-ha.
|
| [8114]
|
johnjamesjacoby
|
BuddyPress: Respect post visibility in activity.
Prevent activity creation for topics and replies protected by their own or an inherited password, regardless of the current visitor's password cookie. Remove activity when an individual topic or reply becomes protected or unpublished, including posts converted to anonymous authorship.
Restore eligible activity when an individual post becomes publicly visible again, including closed topics. Preserve the revision setting for ordinary edits and exclude anonymous posts from activity creation. This change does not bulk-clean historical activity or synchronize descendants when a forum or site changes visibility.
In trunk, for 2.7.
Props ton-ha.
|
| [7934]
|
johnjamesjacoby
|
BuddyPress: Restore member engagement actions.
Read BuddyPress member-page engagement actions from the request before passing them to the existing favorites and subscriptions handlers. BuddyPress fires `bp_actions` without arguments, so direct callback registration left the action empty and member-profile links reloaded without changing state.
In branches/2.6, for 2.6.20.
Props bradleyt, robin-w, mike80222.
Fixes #3454.
|
| [7933]
|
johnjamesjacoby
|
BuddyPress: Restore member engagement actions.
Read BuddyPress member-page engagement actions from the request before passing them to the existing favorites and subscriptions handlers. BuddyPress fires `bp_actions` without arguments, so direct callback registration left the action empty and member-profile links reloaded without changing state.
In trunk, for 2.7.
Props bradleyt, robin-w, mike80222.
See #3454.
|
| [6485]
|
johnjamesjacoby
|
BuddyPress: Root group forum updates
* Include ability to create a new group root forum if none exists
* Update group-forum setting verbiage to accommodate above
* When a forum is deleted, check if it's the group root, and delete the setting accordingly
* Introduce `bbp_maybe_delete_group_forum_root()` and `bbp_maybe_create_group_forum_root()` functions to carry out the above functionalities
|
| [8308]
|
johnjamesjacoby
|
BuddyPress: Scope group forum moderation capabilities.
Require an explicit forum, topic, or reply before group staff receive moderation capabilities. Keep view=all queries, links, redirects, and pagination scoped to the relevant forum or topic while preserving site-wide moderator behavior. Add BuddyPress regression coverage for local and unrelated content.
In 2.6, for 2.6.22.
|
| [8307]
|
johnjamesjacoby
|
BuddyPress: Scope group forum moderation capabilities.
Require an explicit forum, topic, or reply before group staff receive moderation capabilities. Keep view=all queries, links, redirects, and pagination scoped to the relevant forum or topic while preserving site-wide moderator behavior. Add BuddyPress regression coverage for local and unrelated content.
In trunk, for 2.7.
|
| [8027]
|
johnjamesjacoby
|
BuddyPress: Scope group topic routes to requested topics.
Use non-singular post-name query arguments when resolving BuddyPress group topic routes and titles so an absent or invalid slug remains part of each lookup. This prevents missing, cross-forum, and non-public topic routes from reusing the first visible topic in the group forum.
Add coverage for empty and missing slugs while preserving the existing group-topic visibility coverage.
In branches/2.6, for 2.6.20.
Fixes #3743.
|
| [8026]
|
johnjamesjacoby
|
BuddyPress: Scope group topic routes to requested topics.
Use non-singular post-name query arguments when resolving BuddyPress group topic routes and titles so an absent or invalid slug remains part of each lookup. This prevents missing, cross-forum, and non-public topic routes from reusing the first visible topic in the group forum.
Add coverage for empty and missing slugs while preserving the existing group-topic visibility coverage.
In trunk, for 2.7.
Fixes #3743.
|
| [8409]
|
johnjamesjacoby
|
BuddyPress: Support group forum subforums.
Route child forums, topics, and replies through the attached ancestor's BuddyPress group, including edit and paged URLs. Inherit group access for private and hidden descendants, assign their activity to the group, and prime forum caches before descendant checks.
In trunk, for 2.7.
Props moebis, mlwilkerson.
Fixes #2191.
|
| [6391]
|
johnjamesjacoby
|
BuddyPress: Switch activity action back to `$this->component` and skip groups tests.
Proprs thebrandonallen. Fixes #3089.
|
| [6262]
|
johnjamesjacoby
|
BuddyPress: Update `bbp_format_buddypress_notifications()` with new parameters.
* Prefer `$component_action_name` over less reliable `$content`
* Parameters match BuddyPress 2.6.0 and higher signature
* Mild function clean-up
Fixes #3036.
|
| [7981]
|
johnjamesjacoby
|
BuddyPress: Update activity after topic and reply edits.
Remove transient post type revision-support checks from BuddyPress activity updates. Front-end edits temporarily disable that support to avoid duplicate WordPress revisions, so the callbacks returned before updating existing activity. Preserve the global bbPress revision setting and add regression coverage for topics and replies.
In trunk, for 2.7.
Props michael8888, r-a-y.
Fixes #3328.
|
| [7983]
|
johnjamesjacoby
|
BuddyPress: Update activity after topic and reply edits.
Remove transient post type revision-support checks from BuddyPress activity updates. Front-end edits temporarily disable that support to avoid duplicate WordPress revisions, so the callbacks returned before updating existing activity. Preserve the global bbPress revision setting and add regression coverage for topics and replies.
Merges [7981] to the 2.6 branch.
In branches/2.6, for 2.6.20.
Props michael8888, r-a-y.
Fixes #3328.
|
| [6368]
|
johnjamesjacoby
|
BuddyPress: Update inline doc for group-forum filter. See #2974.
|
| [5822]
|
johnjamesjacoby
|
BuddyPress: Use `bbp_get_paged_slug()` instead of `$wp_rewrite->pagination_base` directly.
|
| [5653]
|
netweb
|
BuddyPress: Use `bbp_is_favorites_active()` and `bbp_is_subscriptions_active()` respectively to check if bbPress' favorites and/or subscriptions are enabled before displaying menu items in BuddyPress member profiles.
Props tharsheblows. Fixes #2594
|
| [6285]
|
johnjamesjacoby
|
BuddyPress: Use correct hook type for `bp_modify_page_title` filter.
Props thebrandonallen. Fixes #3057.
|
| [7902]
|
johnjamesjacoby
|
BuddyPress: Use locale-aware notification plurals.
Use `_n()` for grouped reply notifications so translations can select the correct plural form for the notification count. Preserve the existing escaped notification string and add regression coverage for English and locale-selected plural forms.
In branches/2.6, for 2.6.20.
Props tobifjellner, dilip2615.
Fixes #3435.
|
| [7901]
|
johnjamesjacoby
|
BuddyPress: Use locale-aware notification plurals.
Use `_n()` for grouped reply notifications so translations can select the correct plural form for the notification count. Preserve the existing escaped notification string and add regression coverage for English and locale-selected plural forms.
In trunk, for 2.7.
Props tobifjellner, dilip2615.
See #3435.
|
| [8271]
|
johnjamesjacoby
|
BuddyPress: Use the configured reply edit slug.
Build group reply edit URLs with `bbp_get_edit_slug()` instead of the internal rewrite ID. This keeps generated links aligned with the configured route while preserving the default `edit` slug, with regression coverage for custom values.
In branches/2.6, for 2.6.22.
Props konnektiv.
See #3780.
|
| [8270]
|
johnjamesjacoby
|
BuddyPress: Use the configured reply edit slug.
Build group reply edit URLs with `bbp_get_edit_slug()` instead of the internal rewrite ID. This keeps generated links aligned with the configured route while preserving the default `edit` slug, with regression coverage for custom values.
In trunk, for 2.7.
Props konnektiv.
Fixes #3780.
|
| [8023]
|
johnjamesjacoby
|
BuddyPress: Use the current activity SQL filter.
Register the SQL-clauses filter on BuddyPress 15 and newer, adapting its WHERE conditions through the existing forum visibility logic. Continue using the legacy where-conditions filter on earlier BuddyPress releases.
Add regression coverage for version-appropriate filter registration while preserving restricted and password-protected activity handling.
In branches/2.6, for 2.6.20.
Fixes #3741.
|
| [8022]
|
johnjamesjacoby
|
BuddyPress: Use the current activity SQL filter.
Register the SQL-clauses filter on BuddyPress 15 and newer, adapting its WHERE conditions through the existing forum visibility logic. Continue using the legacy where-conditions filter on earlier BuddyPress releases.
Add regression coverage for version-appropriate filter registration while preserving restricted and password-protected activity handling.
In trunk, for 2.7.
Fixes #3741.
|
| [6808]
|
johnjamesjacoby
|
BuddyPress: add more `fully_loaded()` methods to component classes.
This will allow an entry point for plugins to alter these classes how they see fit.
Fixes #3192.
|
| [7184]
|
johnjamesjacoby
|
BuddyPress: add topic ID to `bbp_new_reply` notification type.
This commit adds more context to otherwise vague topic reply notifications, and also more accurately marks notifications as read when clicking on the adminbar menu to view them.
In branches/2.6 for 2.6.7. Fixes #3341.
Props konnektiv.
|
| [7183]
|
johnjamesjacoby
|
BuddyPress: add topic ID to `bbp_new_reply` notification type.
This commit adds more context to otherwise vague topic reply notifications, and also more accurately marks notifications as read when clicking on the adminbar menu to view them.
In trunk for 2.7.0. See #3341.
Props konnektiv.
|
| [6805]
|
johnjamesjacoby
|
BuddyPress: clean up new `get_profile_url()` method.
See r6804.
|
| [7058]
|
johnjamesjacoby
|
BuddyPress: explicitly query for Group forum IDs, for topic parent dropdown.
This commit fixes an ambiguity regarding which forum IDs should/may appear when editing a Forum Topic inside a Group Forum. By being explicit here, a possible bug can be avoided where incorrect forum IDs could be listed.
Props imath. For 2.6.14, branches/2.6
|
| [7057]
|
johnjamesjacoby
|
BuddyPress: explicitly query for Group forum IDs, for topic parent dropdown.
This commit fixes an ambiguity regarding which forum IDs should/may appear when editing a Forum Topic inside a Group Forum. By being explicit here, a possible bug can be avoided where incorrect forum IDs could be listed.
Props imath. For 2.7, trunk.
|
| [7059]
|
johnjamesjacoby
|
BuddyPress: explicitly validate IDs when editing Group forum topics & replies.
This commit adds methods to validate that the forum IDs and reply-to IDs for topics & replies are within the accepted ranges for the specific Group Forum they are being edited inside of.
In addition, the `moderate_forum` mapped meta capability is removed, and the broader `moderate` capability will continue to cover its use case. This capability was not intended to be used directly, and doing so incorrectly would trigger unintended and infinite recursion.
For 2.6.14, branches/2.6
|
| [7060]
|
johnjamesjacoby
|
BuddyPress: explicitly validate IDs when editing Group forum topics & replies.
This commit adds methods to validate that the forum IDs and reply-to IDs for topics & replies are within the accepted ranges for the specific Group Forum they are being edited inside of.
In addition, the `moderate_forum` mapped meta capability is removed, and the broader `moderate` capability will continue to cover its use case. This capability was not intended to be used directly, and doing so incorrectly would trigger unintended and infinite recursion.
For 2.7, trunk
|
| [6710]
|
johnjamesjacoby
|
BuddyPress: improve targeting of single forum/topic filters.
This change simplifies the logic used when attaching-to and checking-for the current BuddyPress Group Forum & Topic pages, by conditionally filtering behind a singular `bp_is_group()` check.
Fixes #3165. Props thebrandonallen.
|
| [6807]
|
johnjamesjacoby
|
BuddyPress: more efficient includes method.
Props r-a-y. Fixes #3193.
|
| [6810]
|
johnjamesjacoby
|
BuddyPress: prefer `empty()` check on `disable_blogforum_replies` setting.
This fixes a bug causing some activity to not appear in relative activity streams.
Fixes #3180.
|
| [7188]
|
johnjamesjacoby
|
BuddyPress: prevent possible duplicate "Topics" & "Replies" activity filters.
This commit removes legacy shims (for filters like `bp_activity_filter_options`) and instead trusts that `bp_activity_set_action()` will be obeyed when outputting filter select HTML elements. These shims were necessary in older versions of BuddyPress and no longer are.
In branches/2.6 for 2.6.7. Fixes #3367.
|
| [7187]
|
johnjamesjacoby
|
BuddyPress: prevent possible duplicate "Topics" & "Replies" activity filters.
This commit removes legacy shims (for filters like `bp_activity_filter_options`) and instead trusts that `bp_activity_set_action()` will be obeyed when outputting filter select HTML elements. These shims were necessary in older versions of BuddyPress and no longer are.
In trunk for 2.7.0. See #3367.
|
| [6982]
|
johnjamesjacoby
|
BuddyPress: return the original content on non-reply actions.
This commit fixes a regression causing BuddyPress notifications to be broken in #3036.
Props tw2113. Fixes #3287. For 2.6.2, branches/2.6.
|
| [6981]
|
johnjamesjacoby
|
BuddyPress: return the original content on non-reply actions.
This commit fixes a regression causing BuddyPress notifications to be broken in #3036.
Props tw2113. Fixes #3287. For 2.7, trunk.
|
| [6815]
|
johnjamesjacoby
|
BuddyPress: tweak notifications item IDs to provide a bit more context.
This change also fixes a bug with hierarchical reply notifications.
Props jpolakovic. Fixes #2834.
|
| [6804]
|
johnjamesjacoby
|
BuddyPress: updates to member profile URL filters:
* Introduce methods for known user profile pages
* Update public filter methods to use a private method
This change uses new intercept hooks to make sure bbPress profile URLs are turned into BuddyPress ones instead.
See #3814.
|
| [6845]
|
johnjamesjacoby
|
BuddyPress: use `$reply_id` instead of `$topic_id` so `bbp_get_reply_url()` works correctly.
This change ensures that notification links go directly to the reply, not the topic, and not a 404.
Fixes #3213. See #3214.
|
| [5995]
|
netweb
|
Build Tools: Add @stylelint for linting CSS to adhere to WordPress CSS Coding Standards
This changeset adds a new Grunt task `grunt postcss:lint` that runs stylelint on CSS & SCSS files to ensure bbPress' CSS adheres to WordPress CSS Coding Standards.
8 months in the making and is maintained by yours truly @netweb, with stylelint I'm learning JavaScript deeply.
See also:
* http://stylelint.io/
* https://github.com/stylelint/stylelint
* https://github.com/ntwb/stylelint-config-wordpress
* https://make.wordpress.org/core/handbook/best-practices/coding-standards/css/
Hat-tip: David Clark and Richard Hallows for the ongoing help and support.
Props netweb.
Fixes #2924.
|
| [5994]
|
netweb
|
Build Tools: Add Autoprefixer for adding CSS vendor prefixes
This changeset adds a new Grunt task `grunt postcss:core` that runs Autoprefixer on CSS & SCSS files to add or remove any vendor prefixes required by browsers.
Browsers supported are the same as WordPress currently supports which are:
* Android >= 2.1
* Chrome >= 21
* Edge >= 12
* Explorer >= 7
* Firefox >= 17
* Opera >= 12.1
* Safari >= 6.0.
Vendor prefixes are are also added for `templates/default/css/bbpress.css` as this is the only file that requires them at this time.
Fixes #2923.
|
| [6655]
|
netweb
|
Build Tools: Add Composer packages to Travis CI cache
|
| [5996]
|
netweb
|
Build Tools: Add NPM package `postcss-scss` for styelelint SCSS compatibility
This changeset fixes an idiosyncratic NPM v3.x issue with "flat" folders and sharing dependencies that is not an issue when using NPM v2
See #2924
|
| [6073]
|
netweb
|
Build Tools: Add PHP 7.1 to Travis CI and "allow to fail"
This changeset adds explict PHP 7.1 for testing bbPress, see also #WP37625
See #2980.
|
| [6132]
|
netweb
|
Build Tools: Add PHP 7.1 to the Travis CI job matrix and remove from `allow_failures` list
|
| [6637]
|
netweb
|
Build Tools: Add PHP 7.2 to Travis CI.
Fixes #3136.
|
| [7006]
|
netweb
|
Build Tools: Add PHPCS with custom bbPress ruleset
- This changeset adds an initial bbPress PHPCS ruleset
- Future iteration of the rules in the ruleset can follow later
- To run the PHPCS check run `grunt phpcs
Fixes #3294.
|
| [6203]
|
netweb
|
Build Tools: Add Travis CI cache for installed apt packages.
See #2980.
|
| [5961]
|
netweb
|
Build Tools: Add WordPress 4.4 to the Travis CI build matrix
|
| [6003]
|
netweb
|
Build Tools: Add WordPress 4.5 to Travis CI build matrix
|
| [6081]
|
netweb
|
Build Tools: Add WordPress 4.6 to Travis CI build matrix
|
| [6131]
|
netweb
|
Build Tools: Add WordPress 4.7 to Travis CI build matrix
|
| [6840]
|
netweb
|
Build Tools: Add a `.npmrc` file, and move `node-sass` to `devDependencies`
The `.npmrc` file configures NPM to save exact versions
|
| [6651]
|
netweb
|
Build Tools: Add debug echo for `TRAVIS_PHP_VERSION`
|
| [5984]
|
netweb
|
Build Tools: Add minimum NodeJS 4.2.x LTS version
This changeset sets the minimum required NodeJS version supported. This is required as various NPM modules now require a minimum version greater than the default v0.10.x currently in use.
See #2920.
|
| [6494]
|
netweb
|
Build Tools: Add npm `package-lock.json` for npm v5.x
This changeset adds support for npm 5 which include significant performance improvements, these are primarily due updated caching, offline caching and the addition of a `package-lock.json` to leverage the new caching.
To install and use npm 5 with your existing install of Node.js 6 or 7 run `npm i npm@5 -g`. Node.js 8 support will be added in a follow up ticket.
Installing npm modules for bbPress is now ~6x faster with npm 5 🏎
Fixes #3113.
|
| [7039]
|
netweb
|
Build Tools: Add project root `composer.json` file.
This commit adds the following Composer package developer dependencies:
• `phpcompatibility/phpcompatibility-wp`
• `wp-coding-standards/wpcs`
• `dealerdirect/phpcodesniffer-composer-installer`
This also adds two composer scripts:
• `composer lint` to "lint" the PHP files using PHPCS
• `composer format` to "format" the PHP files using PHPCBF
Props jrf.
See #3294.
|
| [6462]
|
netweb
|
Build Tools: Build Tools: Update `grunt-contrib-clean` from 1.0.0 to 1.1.0
* https://github.com/gruntjs/grunt-contrib-clean/compare/v1.0.0...v1.1.0
This changeset reverts the incorrect change in [6461] to `grunt-contrib-copy` instead of `grunt-contrib-clean`
Antiprops netweb.
|
| [6548]
|
netweb
|
Build Tools: Bump slow tests threshold for multisite to 250 for now, and we can continue to bring this value down as test performance is improved.
|
| [6962]
|
netweb
|
Build Tools: Cache `node_modules` folder in Travis CI
Fixes #2885.
|
| [6652]
|
netweb
|
Build Tools: Check for existence `xdebug.ini` using `phpenv` for Travis CI
|
| [5985]
|
netweb
|
Build Tools: Define TRAVIS_NODE_VERSION as a global variable for Travis CI
See #2920
|
| [6946]
|
netweb
|
Build Tools: Disable PHPUnit Speed Tester
|
| [6656]
|
netweb
|
Build Tools: Exclude Travis CI PHP 7.2 builds for WP 4.7 & 4.8, PHP 7.2 compat will WP 4.9.
|
| [6076]
|
netweb
|
Build Tools: Fix `BBP_UnitTestCase::go_to()` for `WP_Network`.
This changeset is via buddypress:changeset:10125
Props boonebgorges.
Fixes #2981
|
| [6654]
|
netweb
|
Build Tools: Fix copy pasta added in [6652]
|
| [6404]
|
netweb
|
Build Tools: Fix copy pasta of `;` instead of `,` added in [6403].
WordPress Coding Standards requires one variable declaration.
See #2924.
|
| [7050]
|
netweb
|
Build Tools: Improve PHPCS setup.
Props jrf.
See #3294.
For trunk.
|
| [5619]
|
netweb
|
Build Tools: Include PHP-7 "nightly" builds with failures allowed in Travis-CI
|
| [5986]
|
netweb
|
Build Tools: Install NodeJS 4.x.x using NVM in Travis CI
See #2920
|
| [6075]
|
netweb
|
Build Tools: More targeted cleanup for multisite unit tests.
This changeset is a subset of buddypress:changeset:9980 and removes a previous heavy-handed workaround for deleting the first multisite user. This also resolves a fatal error `Object does not implement ArrayAccess` when running the tests on HHVM.
See #2962, #2981
|
| [6625]
|
netweb
|
Build Tools: Move PHP 5.2 and 5.3 Travis CI jobs from the `php` section to the `matrix` section.
This changeset is a follow up to [6624] where the "build matrix" was broken, my bad.
See #3127.
|
| [6267]
|
netweb
|
Build Tools: NPM modules in `package.json` should only use semantic versioning `~` ''minor'' versions, rather than `^` ''major'' versions.
This changeset will help avoid the pitfalls of upstream NPM modules breaking our build due to a release of a new major version for which bbPress has not yet tested against.
|
| [6405]
|
netweb
|
Build Tools: Remove HHVM from the test infrastructure on Travis.
Fixes #3104.
|
| [6201]
|
netweb
|
Build Tools: Remove unsupported WordPress versions from Travis CI build job matrix.
This changeset removes all WordPress versions previous to 4.7 as this is now bbPress' minimum required version.
|
| [5983]
|
netweb
|
Build Tools: Renamed `grunt-rtlcss` option `options.config` to RTLCSS v2.x `options.opts` option
See #2918
|
| [6799]
|
netweb
|
Build Tools: Replace Browserslist configuration in `Gruntfile.js` with `@wordpress/browserslist-config`
This change simplifies bbPress' Browserslist configuration maintainence by depending on WordPress' shared Browserslist configuration package:
* https://github.com/WordPress/packages/tree/master/packages/browserslist-config
* https://github.com/WordPress/packages/
|
| [5987]
|
netweb
|
Build Tools: Revert Travis CI TRAVIS_NODE_VERSION environment variable changes from r5984/r5985, installing NodeJS 4.x.x via NVM is sufficient per r5986.
Fixes #2920.
|
| [6000]
|
netweb
|
Build Tools: Revert [5999] `grunt-legacy-util` update, from 0.2.0 to 1.0.0
This changeset reverts the above change as I missed the `1.0.0` recommended [https://github.com/gruntjs/grunt-legacy-util/blob/master/README.md change] to use `require('child_process').spawn` over `grunt.util.spawn`. Per NodeJS docs [https://nodejs.org/api/child_process.html#child_process_child_process_spawn_command_args_options here] and [https://nodejs.org/dist/latest-v4.x/docs/api/child_process.html#child_process_child_process_spawn_command_args_options here] for NodeJS versions 5.x and 4.x respectively this needs some more testing and changes to the Grunt phpunit task and multi task.
Another option per [https://github.com/gruntjs/grunt-legacy-util/issues/10 grunt-legacy-util #10] is to switch to [https://www.npmjs.com/package/cross-spawn-async cross-spawn-async]
Both above options will require *nix and Windows testing.
''6000 is the natural number following 5999 and preceding 6001.''
See #2918
|
| [6653]
|
netweb
|
Build Tools: Run Travis-CI unit tests against WordPress 4.8.
|
| [6748]
|
netweb
|
Build Tools: Run Travis-CI unit tests on WordPress 4.9.
|
| [6025]
|
netweb
|
Build Tools: Set a whitelist for PHPUnit code coverage
This chageset adds a PHPUnit whitelist of files for use with code coverage tests analsyis tools.
Hat tip jorbin.
Fixes #2953.
|
| [6100]
|
netweb
|
Build Tools: Switch stylelint Grunt task from `grunt postcss:lint` to `grunt stylelint`
This changeset switches the stylelint task from using the `grunt-postcss` to `grunt-stylelint` NPM module. This new Grunt module supports stylelint's native formatters and allows for improved task error reporting. This change also splits the CSS and SCSS lint tasks in preparation for a future `stylelint-config-wordpress` SCSS update.
See also: https://github.com/wikimedia/grunt-stylelint
Props netweb.
See #2924.
|
| [6624]
|
netweb
|
Build Tools: Switch to Ubuntu Trusty as the the default linux distro for Travis CI.
* This changeset also explicitly adds `dist: precise` to the PHP 5.2 and 5.3 build jobs.
* Travis CI will discontinue support of PHP 5.2 & 5.3 in September 2017 and a further follow up will be required.
Fixes #3127.
|
| [6145]
|
netweb
|
Build Tools: Travis CI: Only test PHP 7.1 against WordPress 4.7 or greater
This changeset updates the Travis CI test matrix to match WordPress' PHP 7.1 compatability, which was only added in version 4.7.
|
| [6577]
|
netweb
|
Build Tools: Update Autoprefixer supported browser matrix.
Following WordPress' implementation this new version hard codes IE 11 as a minimum, otherwise specifies either last 2 or last 1 based on https://make.wordpress.org/design/handbook/design-guide/browser-support/
|
| [6222]
|
netweb
|
Build Tools: Update Grunt and companion packages to the latest version.
This changeset updates `grunt`, `grunt-exec`, and `grunt-legacy-utils` to the latest version.
Run `npm install` in your terminal to install the updates above.
|
| [7107]
|
netweb
|
Build Tools: Update Node.js and npm required versions
|
| [7106]
|
netweb
|
Build Tools: Update PHPCS
|
| [6236]
|
netweb
|
Build Tools: Update PostCSS Autoprefixer from v6.5.1 to v6.6.1
* See https://github.com/postcss/autoprefixer/compare/6.5.1...6.6.1
|
| [6268]
|
netweb
|
Build Tools: Update PostCSS Autoprefixer from v6.6.1 to v6.7.0
|
| [6237]
|
netweb
|
Build Tools: Update PostCSS SCSS from v0.3.0 to v0.4.0
* See https://github.com/postcss/postcss-scss/compare/0.3.0...0.4.0
|
| [6945]
|
netweb
|
Build Tools: Update SASS Node.js modules
|