Releases: publishpress/PublishPress-Permissions
Releases · publishpress/PublishPress-Permissions
v4.0.20
v4.0.19
v4.0.18
Change Log
- Perf : Eliminated scan of users table on plugin activation (impacting sites with large number of users)
- Perf : Eliminated recursive query of subpages (impacting sites with complex page hierarchies)
- Perf : Improved caching of post capability checks
- Perf : On category / term queries, don't filter term counts if empty terms are not being hidden and counts are not being shown
- Code : Improved PHP Code Sniffer scan results
- Compat : Elementor - Could not use Elementor front end editor to save a draft of a published post
- Compat : Nested Pages - Apply pp_force_quick_edit capability to Nested Pages' Quick Edit and Contextual Add / Insert buttons
- Fixed : Filters for Post category, Tags, Terms, Parent or Status could be applied to wrong post under certain conditions
- Fixed : Permissions > Settings > Core > Front End > "Performance: Don't filter category / tag counts" was not applied for Administrator
- Fixed : Some strings on Permissions > Settings were not translated
- Fixed : Gutenberg editor usage was not properly detected when triggered by another plugin, possibly leading to issues with category / term assignment filtering
- Fixed : Category pages: Subcategory posts were inappropriately hidden on some sites
- Fixed : Legacy Nav Menu Management - Limited Nav Menu editors saw uneditable menus in dropdown on Menus management screen
- Fixed : Legacy Nav Menu Management filters interfered with front end filtering under some conditions
- Fixed : Sanity check to prevent excessive version history logging if installed plugin's version tags or version tag storage is incorrect
- Fixed : Terms were inappropriately auto-assigned under some conditions\
- Change : Permissions > Settings > Editing option to disable auto-assignment of terms (when default term is not selectable). Note: Auto-assignment is required for some term-restricted editing configurations.
- Change : Auto-assign a term only if no default terms are selectable and the user's editing access is modified by term-specific Permissions
- Change : Never auto-assign a term to front page or posts page
- Change : Constant definitions related to term auto-assignment to assist any potential troubleshooting or restore previous behavior
- Change : User search for Specific Permission assignment - use LIKE matching for user meta field searches
- Change : Suppress "Enable Permissions" metaboxes in Post editor, Edit Term screens
- Change : Support constant PRESSPERMIT_MEDIA_UPLOAD_GRANT_PAGE_EDIT_CAPS for front end uploading solutions that require page editing capabilities for the async upload request
- Lib : Update wordpress-reviews library to v1.1.20
- Lib : Update wordpress-version-notices library to v2.1.3
- Lang : Update ES, FR, IT translations
v3.11.6
Change Log
- Feature : Option to require Taxonomy edit capability to assign post tags that do not already exist
- Fixed : On Post edit, Tags were not filtered based on Specific Permissions
- Fixed : On Permissions > Settings, All Taxonomies remained checked even after updating with some disabled
- Compat : Work around unidentified compatibility issue affecting term filtering and access to certain static methods
v4.0.0
Change Log
- Perf : Eliminated scan of users table on plugin activation (impacting sites with large number of users)
- Perf : Eliminated recursive query of subpages (impacting sites with complex page hierarchies)
- Perf : Improved caching of post capability checks
- Code : Improved phpcs scan results
- Feature : Option to require Taxonomy edit capability to assign post tags that do not already exist
- Fixed : On Post edit, Tags were not filtered based on Specific Permissions
- Fixed : On Permissions > Settings, All Taxonomies remained checked even after updating with some disabled
- Compat : Work around unidentified compatibility issue affecting term filtering and access to certain static methods
v3.11.5
Change Log
- Compat : Beaver Builder - Queries within BB shortcodes were improperly filtered
- Fixed : Supplemental Role captions (for current assignments) were blank (since 3.11.4)
- Fixed : PHP Warning "Attempt to read property 'count' on string"
- Fixed : PHP Warning "Undefined variable $admin_post_new_url"
v3.11.4
v3.11.3
Change Log
- Fixed : Some Permissions filtering was not applied on sites with a custom wp-admin URL
- Fixed : Type-specific Supplemental Roles also granted most generic capabliities in Pattern Role. Introduce new Permissions > Advanced > Role Integration setting to restore previous behavior if needed.
- Fixed : On page edit, if the Page Parent is not editable by the logged in user, it is hidden from the Page Parent selector. This occurred only with WP >= 6.3 and with a non-standard advanced Permissions configuration.
- Fixed : PHP Warning in term filtering (Attempt to read property "term_taxonomy_id" on string) under some configurations
- Fixed : Filtering of default category / term by other plugin was overridden
- Fixed : Edit User Permissions - PHP Warning "compact(): Argument must be string..."
- Fixed : Fatal error "Call to a member function init() on null" under some configurations
- Compat : Polylang + WP 6.3 - Language filter was no longer applied to Page Parent dropdown
v3.11.1
Change Log
- Fixed : Rest API access error on some sites (potentially preventing login)
- Fixed : Gallery block in Gutenberg editor: error loading Image Size dropdown options
- Fixed : Caption for Navigation Menus (for Navigation block) did not distinguish them from legacy Nav Menus
- Fixed : PHP 8.1 - Warning for dynamic property creation in post editor
- Compat : Peepso - Non-administrators couldn't submit front end posts on PHP >= 8.1
v3.10.0
Change Log
- Compat : WooCommerce - Private Products were not listed in Shop, even if Read Permissions are assigned
- Compat : ACF Extended - Extra Update button on Edit Term screen
- Fixed : Fatal error for undefined PUBLISHPRESS_PERMISSIONS_PRO_VENDOR_PATH on some installations
- Fixed : If a "Limit to: (none)" Permission is assigned to default-restrict a post type, creating a new post causes a post-specific allowance to be assigned
- Fixed : Category filtering error caused Nav Menu corruption if empty category is used as a top level menu
- Change : Update vendor libraries using new internal-vendor structure