| [3102]
|
johnjamesjacoby
|
Missed a spot from r3098. Fixes possible empty reply_content error when editing a reply.
|
| [5361]
|
johnjamesjacoby
|
Missed a spot.
|
| [2767]
|
johnjamesjacoby
|
Missed a spot. See r2765.
|
| [3577]
|
johnjamesjacoby
|
Missed a spot. Swap @public for @var. See r3576
|
| [5562]
|
johnjamesjacoby
|
Missed removing a tabindex usage. See #2714.
|
| [3965]
|
johnjamesjacoby
|
Missed two EOF ?> in index.php files. See r3964; #1850.
|
| [6139]
|
johnjamesjacoby
|
Moderation: /s/exists/missing
See #3032.
|
| [6138]
|
johnjamesjacoby
|
Moderation: Add error message if reply could not be found or no longer exists.
See #3032.
|
| [6050]
|
netweb
|
Moderation: Add new `bbp_moderation_keys` and `bbp_blacklist_keys` filters
This changeset allows external plugins to filter the list of moderation and blacklist keyword terms, IP, URLs, words, etc.
Also cleans up `bbp_check_for_moderation()` to bails early if there are no moderation keys inline with `bbp_check_for_blacklist()`
Props thebrandonallen, satollo.
Fixes #2861.
|
| [6146]
|
netweb
|
Moderation: Add some missing PHPDoc `@since` revisions
See #3032.
|
| [6384]
|
johnjamesjacoby
|
Moderation: Allow per-forum moderators to edit topics & replies inside of forums they have moderation control over.
This feature require the following changes:
* Prefer `read_forum` capability check over `read_private_forums` or `read_hidden_forums`, and include a `$forum_id` parameter to assist `map_meta_cap` filters
* Prefer `edit_others_topics|replies` over `moderate` where appropriate, to ensure capability mappings work as intended
* Introduce `bbp_get_public_topic_statuses()` to replace several duplicate occurrences of the same array usage (also allow these to be filtered)
* Introduce `bbp_is_topic_public()` (not to be confused with `bbp_is_topic_published()`) to provide parity with `bbp_is_forum_public()` and also utilize `bbp_get_public_topic_statuses()` from above
* Add local caching to `bbp_exclude_forum_ids()` as a performance optimization to reduce the depth of `current_user_can()` calls when private & hidden forums are in use
* Add `user_can( 'moderate' )` capability checks to various mappings, to ensure forum moderators can read/edit/delete content inside of the individual forums they are moderators of
* Use `bbp_get_user_id()` where appropriate, rather than casting as `int`
* Various surrounding code clean-ups
See #2593.
|
| [6349]
|
netweb
|
Moderation: Autoprefixer follow up to [6348] and [6344]
See #3073.
|
| [6348]
|
netweb
|
Moderation: CSS coding standards fixes follow up after [6344]
See #3073.
|
| [6342]
|
johnjamesjacoby
|
Moderation: Clean-up from r6341. Props netweb.
|
| [6133]
|
johnjamesjacoby
|
Moderation: First pass at improved reply toggle actions:
* Allow custom toggles, or replacement of existing toggles with new procedures
* Introduce a handful of actions & filters to enable the above
* Separate functionality into smaller, more manageable parts.
See #3032. (Forums & Topics @todo)
|
| [6142]
|
johnjamesjacoby
|
Moderation: First pass at improved topic toggle actions:
* Allow custom toggles, or replacement of existing toggles with new procedures
* Introduce a handful of actions & filters to enable the above
* Separate functionality into smaller, more manageable parts.
See #3032. (Forums @todo)
|
| [5841]
|
johnjamesjacoby
|
Moderation: Fix some copy-pasta and make sure form terms are formatted correctly. See #459.
|
| [6344]
|
johnjamesjacoby
|
Moderation: Implement theme-side edit-lock interface.
* Edits to defaut theme javascript to interact with alert UI
* Add `alert-topic-lock.php` template part
* Add topic functions relating to edit-lock functionality
* Modify single-topic and topic-edit template parts to include the alert part
* Add CSS to Default template pack to stylize edit-lock alert like a modal (could be pretty much anything)
Props pippin for inspiration. See #3074.
|
| [6085]
|
netweb
|
Moderation: Include topic and reply post content with and without HTML in `moderation_keys` and `blacklist_keys` checks.
This changeset ensures users cannot bypass the moderation word checks by wrapping parts of the word or term in HTML, e.g. `bannedword` could previously be bypassed using `<em>banned</em>word`
Fixes #2986.
|
| [7304]
|
johnjamesjacoby
|
Moderation: Make moderated or disallowed key check case-insensitive for non-Latin words.
The `bbp_check_for_moderation()` function expects to be case-insensitive, but that only works for words using Latin script and consisting of ASCII characters.
This commit adds the Unicode flag to the regular expression used for the check in these functions, so that both pattern and subject can be treated as UTF-8 strings.
See: https://www.php.net/manual/en/reference.pcre.pattern.modifiers.php
In branches/2.6, for 2.6.14.
Fixes #3640.
|
| [7303]
|
johnjamesjacoby
|
Moderation: Make moderated or disallowed key check case-insensitive for non-Latin words.
The `bbp_check_for_moderation()` function expects to be case-insensitive, but that only works for words using Latin script and consisting of ASCII characters.
This commit adds the Unicode flag to the regular expression used for the check in these functions, so that both pattern and subject can be treated as UTF-8 strings.
See: https://www.php.net/manual/en/reference.pcre.pattern.modifiers.php
In trunk, for 2.7.
Fixes #3640.
|
| [6312]
|
johnjamesjacoby
|
Moderation: Maybe add `view=all` query-arguments to view links in row actions.
Fixes #2938.
|
| [6136]
|
johnjamesjacoby
|
Moderation: Move `sub_action` query var into a passable argument, so all actions can have reliable sub-action usage.
See #3032.
|
| [6137]
|
johnjamesjacoby
|
Moderation: Pass `$reply_id` into `bbp_get_reply_toggles()` so the exacty reply ID can be referenced directly at the time of the filter.
See #3032.
|
| [6134]
|
johnjamesjacoby
|
Moderation: Rename function to `bbp_get_reply_toggles()` to better match existing naming scheme.
See #3032.
|
| [6087]
|
johnjamesjacoby
|
Moderation: Skip moderator query if per-forum moderation is not enabled.
Props jmdodd. Fixes #2988.
|
| [6341]
|
johnjamesjacoby
|
Moderation: Use the appropriate `_edit_` post meta when editing a forum/topic/reply.
This first pass does not introduce any theme-side edit-locking interface, but it will warn any user within `wp-admin` if another user is editing something theme-side.
See #3073.
|
| [6858]
|
johnjamesjacoby
|
Moderation: add author-specific keymaster & moderation checks.
This fixes a regression where Moderators were allowed to skip strict moderation rules. Moderators are held to the same standard that regular users in the forums are.
See #3215.
|
| [6857]
|
johnjamesjacoby
|
Moderation: allow custom keys to be passed in via the `$strict` parameter.
See #3215.
|
| [6974]
|
johnjamesjacoby
|
Moderation: flip strict condition in `bbp_check_for_blacklist()`.
This commit fixes a bug causing old calls to `bbp_check_for_blacklist()` to use the incorrect discussion setting values.
|
| [6973]
|
johnjamesjacoby
|
Moderation: flip strict condition in `bbp_check_for_blacklist()`.
This commit fixes a bug causing old calls to `bbp_check_for_blacklist()` to use the incorrect discussion setting values.
|
| [6921]
|
johnjamesjacoby
|
Moderation: make sure pending topics (for moderation reasons) are accessible to authors.
This commit updates the logic inside of the topic & reply map-meta-cap implementations, restricting edit-lock checks to actual "Edit" screens, and using the "edit_others_posts" capability in non-"Edit" screens, ensuring that both scenarios are covered.
It also adds an explicit condition for Pending Topics to both the Topic Description and Topic Notices, alerting users as to why they are seeing what they are seeing.
Fixes #3253 (again!) See also #3164 for other related discussion & details.
|
| [6754]
|
johnjamesjacoby
|
Moderation: pass `$content` into `comment_max_links_url` filter.
This changes brings parity to changes made in WordPress 4.7.0.
Fixes #3141.
|
| [7301]
|
johnjamesjacoby
|
Moderation: prefer "disallowed_keys" over "disallow_keys".
This change corrects a regression (from r7270, since 2.6.11) where the incorrect option name was used when deprecating `blacklist_keys` via #3538.
Props robin-w.
In branches/2.6, for 2.6.14.
Fixes #3638.
|
| [7302]
|
johnjamesjacoby
|
Moderation: prefer "disallowed_keys" over "disallow_keys".
This change corrects a regression (from r7270, since 2.6.11) where the incorrect option name was used when deprecating `blacklist_keys` via #3538.
Props robin-w.
In trunk, for 2.7.
Fixes #3639.
|
| [5853]
|
johnjamesjacoby
|
Moderation: reduce moderation restriction from `keep-gate` to `moderate` in `bbp_check_for_moderation()`.
This changeset ensures that moderators are able to bypass the forum moderation, seeing as how they can self-approve topics & replies anyways.
Props netweb. Fixes #2726.
|
| [6855]
|
johnjamesjacoby
|
Moderation: remove references to blacklist/whitelist verbiage.
This change combines 2 functions into 1, merging `_blacklist()` checks into `_moderation()` checks. A new `$strict` parameter is added, when set to `true` will continue to check against the WordPress `blacklist_keys` option name.
* Tests updated
* `bbp_check_for_blacklist()` deprecated
* Error response keys renamed (non breaking - nothing relies on them)
* Some docs updates
Fixes #3215. For 2.6.
|
| [7234]
|
johnjamesjacoby
|
Moderation: use the correct `post_status` when untrashing a topic/reply.
This change fixes a bug/regression (since WordPress 5.6.0) that was causing untrashed topics & replies to use an unintended `post_status` value.
It fixes it by adding a new function ('bbp_fix_untrash_post_status()') and hooking it to the `wp_untrash_post_status` filter in WordPress, and overriding the results as needed.
Props r-a-y.
In branches/2.6 for 2.6.10. Fixes #3433.
|
| [7235]
|
johnjamesjacoby
|
Moderation: use the correct `post_status` when untrashing a topic/reply.
This change fixes a bug/regression (since WordPress 5.6.0) that was causing untrashed topics & replies to use an unintended `post_status` value.
It fixes it by adding a new function ('bbp_fix_untrash_post_status()') and hooking it to the `wp_untrash_post_status` filter in WordPress, and overriding the results as needed.
Props r-a-y.
In trunk for 2.7.0. Fixes #3433.
|
| [7123]
|
johnjamesjacoby
|
Moderation: when approving topics & replies, manually set post_date_gmt.
This commit is necessary to prevent `wp_update_post()` from marking these posts as having been published immediately, instead of their original post_date.
In branches/2.6, for 2.6.6.
Props SergeyBiryukov.
See #3133.
|
| [7122]
|
johnjamesjacoby
|
Moderation: when approving topics & replies, manually set post_date_gmt.
This commit is necessary to prevent `wp_update_post()` from marking these posts as having been published immediately, instead of their original post_date.
In trunk, for 2.7.
Props SergeyBiryukov.
See #3133.
|
| [6519]
|
johnjamesjacoby
|
Moderators: Add an `$object_type` parameter to add/remove/delete functions.
In a future release, this will more easily allow objects like taxonomy-terms to have their own moderators, and is also necessary for future enhancements to the WordPress.org support forums where custom taxonomies are used for prevalently than in bbPress core currently.
See #3068, #459.
|
| [5836]
|
johnjamesjacoby
|
Moderators: Add forum moderators field to `form-forum.php` template part. See #459.
|
| [5862]
|
netweb
|
Moderators: Add missing @since PHPDoc missed in `bbp_map_forum_mod_meta_caps()` via r5834
|
| [6223]
|
johnjamesjacoby
|
Moderators: Allow moderators to see topic/reply author IP addresses.
Fixes #2975.
|
| [6407]
|
johnjamesjacoby
|
Moderators: Another performance optimization in `bbp_is_user_forum_moderator()`.
Use `bbp_is_object_of_user()` directly, and clean-up local variable reassignments.
|
| [5834]
|
johnjamesjacoby
|
Moderators: First pass at per-forum moderators.
This commit introduces a powerful feature commonly found in other popular forum software that has been on our wishlist for nearly 9 years. It includes the following changes:
* Custom `forum-mod` taxonomy for assigning user nicenames to forum IDs
* Associated functions for defining capabilities, labels, etc...
* New capability filters for ensuring forum moderators have the ability to moderate forums even without the `moderator` role assignment
* New option for toggling the entire feature on/off (on by default)
Props jmdodd, netweb. See #459.
|
| [6563]
|
johnjamesjacoby
|
Moderators: Introduce "Super Moderators" setting.
This change introduces the option (and default off value), admin setting and UI for toggling it on and off.
A "Super Moderator" is a moderator with the ability to also edit users, a commonly requested and popular feature in other forum software. The use-case is that user accounts may be spammers and need to be moderated beyond just their topics & replies, but the `edit_users` capability is reserved for Administrators (or Super Admins in multisite.) This setting will act as the global on/off to the deeper implementation of this feature.
|
| [5835]
|
johnjamesjacoby
|
Moderators: Introduce `none` argument for topic-tags & forum-mods list functions.
This change allows for passing text or HTML to output if no taxonomy terms are found, and uses this new functionality in `wp-admin` to show per-forum moderators in the list-table column, also reducing code duplication.
See #459.
|
| [5838]
|
johnjamesjacoby
|
Moderators: Introduce functions for theme-side setting & getting of forum mods for `form-forum.php`. See #459.
|
| [6406]
|
johnjamesjacoby
|
Moderators: Performance optimization in `bbp_is_user_forum_moderator()`.
Rather than query for all forums a user can moderate, query for the users that can moderate the forum. This data is likely already hot in the meta-data cache from forums being loaded previously, and eliminates the need to query for forum IDs that are unrelated to the one being checked.
|
| [6455]
|
johnjamesjacoby
|
Moderators: Prefer `sanitize_title` over `trim`. See #3097.
|
| [6056]
|
johnjamesjacoby
|
Moderators: Refactor per-forum moderators to use meta-data instead of mocked taxonomy terms.
If the future of Forums is a taxonomy (vs. a custom post-type) then a per-forum Moderator taxonomy for a Forum taxonomy won't work very well, for a few reasons:
* Scalability
* Taxonomies for taxonomies is a bit more inception than should be required for this simple feature
* Forum moderators do not require much of what taxonomy objects provide (permalinks, visibility, metadata, etc...)
* User taxonomy terms matching nicenames works okay for something like Automattic's P2 theme, but bbPress requires a user ID based solution to avoid data synchronization issues between nicenames & term slugs
So... the future of per-forum per-user capability mappings is in meta-data using `map_meta_cap`.
This commit:
* Removes the `forum_mod` taxonomy and surrounding code additions introduced in the first pass in r5834
* Renames `forum_mod` functions to `forum_moderator` to be more explicit
* Adds CRUD wrapper functions for per-forum moderator meta data
* Adds administrative interfaces for assigning moderators to forums for `wp-admin` and forum `edit` pages
* Adds helper functions for getting user nicenames & IDs
Note that this feature has now been refactored to no longer be forum specific (I.E. object agnostic) -- it's possible for any user access to be mapped based on the object type using any meta-data key. While this is currently useful for per-forum moderators, it may be user for per-topic blocking, per-topic-tag moderation, etc...
See #459.
|
| [5839]
|
johnjamesjacoby
|
Moderators: Rename `bbp_get_forum_mod_ids()` to `bbp_get_forum_moderator_ids()` to better match unabbreviated forum equivalent. Also update phpdoc & refactor some logic to use cached functions. See #459.
|
| [6454]
|
johnjamesjacoby
|
Moderators: Trim usernames after they're exploded.
Resolves an issue where spaces in the comma separated usernames field would result in skipping that user.
Fixes #3097.
|
| [6221]
|
johnjamesjacoby
|
Moderators: Update `bbp_get_moderator_forum_ids()` to use same approach as favs/subs.
See #459, #2959, #2972.
|
| [6032]
|
johnjamesjacoby
|
Moderators: pass current forum/topic/reply ID into `moderate` capability checks, providing additional context about what's being moderated so more targeted decisions can be made.
See #459.
|
| [5285]
|
johnjamesjacoby
|
More Grunt improvements:
* Fixes CSS & JS admin folder path for `BBP_RTL_CSS`, `BBP_LTR_CSS` & `BBP_JS` in Gruntfile.js
* Removes Mint & Evergreen CSS (including RTL) to use Mint & Evergreen SCSS
* Adds `_admin.scss`, `_mixins.scss`, `_variables.scss` via ([https://core.trac.wordpress.org/browser/trunk/src/wp-admin/css/colors /trunk/src/wp-admin/css/colors]) to build our Mint & Evergreen admin themes
* Adds `/includes/admin/styles/evergreen/colors.scss` & `/includes/admin/styles/mint/colors.scss` via [https://github.com/ryelle/admin-color-schemes/tree/2288dcd5b57c9a9045de62d1cfa72722d5163cfc 2288dcd5b5 MP6 GitHub Repo Changset]
* Adds support in Gruntfile.js to build minified and RTL Mint & Evergreen CSS
* Adds `grunt-sass` `~0.10.0` to `package.json` to build Mint & Evergreen CSS from SCSS source
* Reinstates minified and `SCRIPT_DEBUG` support for minified Mint & Evergreen CSS
* Adds minified and `SCRIPT_DEBUG` support for admin javascript & frontend javascript
Props netweb. See #2542.
|
| [5344]
|
netweb
|
More Grunt updates
* Adds `uglify:dynamic` to `grunt uglify` so that `grunt watch` -> `watch:js` tasks can dynamicly minify Javascript files with the `grunt watch` task.
* Improved inline documentation for grunt jshint task.
* Props netweb. See #2542
|
| [5294]
|
netweb
|
More Grunt updates, fixes `grunt watch` task not RTL'ing or minifying CSS files.
* Use explicit CSS file names, avoids ambiguous LTR CSS (avoids LTR = `*.css` including `bbpress-rtl.css`)
* Remove `cssmin:colors` and include Mint and Evergreen CSS minification in `cssmin:core`
* Remove `cssjanus:colors` and include Mint and Evergreen RTL CSS in `cssjanus:core`
* Use `BUILD_DIR` (not `SOURCE_DIR`) to compile RTL CSS `cssjanus`
* Use `BUILD_DIR` (not `SOURCE_DIR`) to compile and LTR & RTL minified CSS with `cssmin`
* Add Grunt tasks `cssjanus:core`, `cssmin:ltr` and `cssmin:rtl` to `grunt watch` -> `watch:colors` task
* Add Grunt tasks `cssmin:ltr` and `cssmin:rtl` to `grunt watch` -> `watch:rtl` task
* Reorders `grunt build` and `grunt build-release` tasks to firstly copy `bbpress.css`, and `admin.css`, then create Mint and Evergreen CSS using `colors` , then RTL all the CSS with `cssjanus:core`, then minify all the CSS with `cssmin:ltr` and `cssmin:rtl`
* Props netweb. See #2542
|
| [5293]
|
johnjamesjacoby
|
More Grunt updates:
* Add `_n_noop` to `grunt-pot` keyword check
* Remove grunt task `test` as PHPUnit tests are covered by grunt task `phpunit`
* Add grunt task `jstest` to run javascript tasks
* Add `grunt-checktextdomain` to `package.json` to check for missing or incorrect text-domain in gettext functions. See https://www.npmjs.org/package/grunt-checktextdomain
* Adds grunt task `checktextdomain` to `grunt build-release`
* Checks for the following keywords: `__:1,2d`, `_e:1,2d`, `_x:1,2c,3d`, `_n:1,2,4d`, `_ex:1,2c,3d`, `_nx:1,2,4c,5d`, `esc_attr__:1,2d`, `esc_attr_e:1,2d`, `esc_attr_x:1,2c,3d`, `esc_html__:1,2d`, `esc_html_e:1,2d`, `esc_html_x:1,2c,3d`, `_n_noop:1,2,3d`, `_nx_noop:1,2,3c,4d`
* Props netweb. See #2542.
|
| [5295]
|
netweb
|
More Grunt: Switch from `grunt-pot` to `grunt-wp-i18n`
* Remove `grunt-pot` from `package.json`
* Add `grunt-wp-i18n` to `package.json`
* Adds grunt task `grunt makebot` to `grunt build` and `grunt build-release`
* Creates `bbpress.pot` in `/build`
* Requires fresh `npm install` to update dependencies
* Props netweb. See #2542
|
| [3057]
|
johnjamesjacoby
|
More adjustments for theme compatability layer. Rejigs the bbp_load_template function to also have theme compatability. Introduces bbp_user_can_view_forum() function as a method to check the scope of a users ability to view private/hidden forums, topics, and replies.
|
| [3100]
|
johnjamesjacoby
|
More aggressive CSS on topic/reply revision log for theme compat
|
| [3851]
|
johnjamesjacoby
|
More aggressively check private and hidden forums when changing forum status. (2.0 branch)
|
| [3852]
|
johnjamesjacoby
|
More aggressively check private and hidden forums when changing forum status. (plugin branch)
|
| [2509]
|
johnjamesjacoby
|
More bbp_loader.php cleanup. Move activation/deactivation/uninstall sequence functions into loader class.
|
| [2971]
|
johnjamesjacoby
|
More clean-up to bbp_pre_get_posts. Fixes #1450.
|
| [5040]
|
johnjamesjacoby
|
More esc_url() improvements, and practice late-escaping where we were otherwise passing around escaped URL variables. See #2367.
|
| [6387]
|
johnjamesjacoby
|
More graceful handling of the `$post` global in `bbp_get_global_post_field()`.
|
| [5289]
|
johnjamesjacoby
|
More grunt updates:
* Add RTL, minified and `SCRIPT_DEBUG` support for bbPress admin CSS.
* Add RTL, minified and `SCRIPT_DEBUG` support for bbPress default theme-compat CSS.
* RTL bbPress CSS is now compiled with cssjanus. (`bbpress-rtl.css` file removed)
* Props netweb. See #2542.
|
| [5326]
|
netweb
|
More grunt updates:
* Add `grunt-patch-wordpress` to `package.json`
* Adds grunt task `grunt patch` to `grunt build` and `grunt build-release`
* Requires fresh `npm install` to update dependencies
* Full instructions https://github.com/aaronjorbin/grunt-patch-wordpress#patching-from-the-command-line
* Props jorbin. See #2542
|
| [5333]
|
netweb
|
More grunt updates:
* Include bbPress version via `package.json` in the 'banner' of minified CSS & JS files
* Include current date and time (UTC) in the 'banner' of minified CSS & JS files
* Props netweb. See #2542
|
| [5031]
|
johnjamesjacoby
|
More improvements to responsive CSS. Props mercime. Fixes #1933.
|
| [4590]
|
johnjamesjacoby
|
More precise list-item CSS. See #2113.
|
| [2885]
|
johnjamesjacoby
|
More renaming of last_active to last_active_time, this time in bbp-admin.php
|
| [2879]
|
johnjamesjacoby
|
More renaming of last_active to last_active_time, this time in bbp-wdigets. Also use enhanced bbp_reply_author_link function to include user gravatar.
|
| [3180]
|
johnjamesjacoby
|
More security sweep and code clean-up through bbp-topic-functions.php. Also fix incorrect variable usage in bbp_update_topic_reply_count() and bbp_update_topic_last_active_time(). See #1514.
|
| [3136]
|
johnjamesjacoby
|
More security sweep and final code clean-up on bbp-topic-functions.php. See #1514.
|
| [5335]
|
johnjamesjacoby
|
More specific CSS selector on closed topics to only target lists of topics, not single topic views. See r2962.
|
| [4641]
|
johnjamesjacoby
|
More thorough regex for pre and code tags and HTML entities. Props Corey Worrell. See #1967.
|
| [3091]
|
johnjamesjacoby
|
More tweaks to avatar styling. Revert r3089/r3090 in favor of something specific to bbPress templates and widgets that guess at container ID's, since some themes are very specific about their avatar positioning.
|
| [3147]
|
johnjamesjacoby
|
More tweaks to the readme.txt
|
| [5091]
|
johnjamesjacoby
|
More updated "About" text for 2.4.
|
| [3424]
|
johnjamesjacoby
|
More useful phpDoc for bbp_sanitize_val() and bbp_get_sanitize_val()
|
| [3672]
|
johnjamesjacoby
|
More verbose descriptions and whitespace clean-up in bbp-core-hooks.php.
|
| [4988]
|
johnjamesjacoby
|
Move $postarr arrays into their respective calls to wp_update_post().
|
| [3012]
|
johnjamesjacoby
|
Move 'bbp_register_textdomain' to priority 2 on 'bbp_init' action. Fixes #1497. Props !GautamGupta for original patch.
|
| [3689]
|
johnjamesjacoby
|
Move 'bbp_setup_current_user' action off of 'bbp_init' and onto 'set_current_user.' See #1722.
|
| [3427]
|
johnjamesjacoby
|
Move 'bbp_setup_updater' action off of 'bbp_init' and late onto 'bbp_ready' to ensure alterations to the permastruct have settled. Fixes issue where a bbPress update would flush the rewrite rules too early on bbPress update. See #1569.
|
| [3439]
|
johnjamesjacoby
|
Move 'bbp_setup_updater' action to 'bbp_admin_init' so update only runs when accessing wp-admin. See #1569. Props nacin.
|
| [4826]
|
johnjamesjacoby
|
Move 'bbp_template_redirect' action to priority 8, giving bbPress precedence over network activated plugins hooked to 'template_redirect' at priority 10 (like BuddyPress). Fixes #2225.
|
| [3282]
|
johnjamesjacoby
|
Move 'bbp_user' and 'bbp_view' into bbPress global vars, so they can be referenced by external plugins more easily and require less maintenance to change if needed later.
|
| [3559]
|
johnjamesjacoby
|
Move BuddyPress extension loader to bbp-core-hooks.php.
|
| [3217]
|
johnjamesjacoby
|
Move _bbp_include_root option into single slug area, to more accurately mirror the order of the settings page. Include more detailed description of what it does.
|
| [4570]
|
jmdodd
|
Move `bbp_notify_subscribers` to priority 11.
* Fixes #2038.
|
| [5274]
|
johnjamesjacoby
|
Move `includes` and `templates` back into `/src` directory. See #2452.
|
| [3192]
|
johnjamesjacoby
|
Move a few theme compatibility helper functions out of bbp-general-functions.php and into bbp-core-compatibility.php
|
| [5225]
|
johnjamesjacoby
|
Move admin CSS and JS out of `admin_head` and into proper enqueues. New `admin.css` replaces top level icons with Dashicons, introduced in WordPress 3.8. Fixes #2396. See #2463.
|
| [3812]
|
johnjamesjacoby
|
Move admin action setup lower in file. See r3811.
|