Roles and Permissions errors page

Resolved

(@lewisself12)

I’m getting errors on the roles and permissions page and when activating the plugin I got the following error;

Roles (Settings) page

Notice: Function map_meta_cap was called incorrectly. When checking for the delete_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the delete_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the delete_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the edit_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the edit_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the edit_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the read_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the read_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the read_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the delete_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the delete_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the delete_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the edit_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the edit_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the edit_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the read_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the read_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Notice: Function map_meta_cap was called incorrectly. When checking for the read_post capability, you must always check it against a specific post. Please see Debugging in WordPress for more information. (This message was added in version 6.1.0.) in C:\Users\LewisSelf\Local Sites\cell-pack-solutions\C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public\wp-includes\functions.php on line 6114

On Activate

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in C:\**website**\app\public\wp-includes\functions.php on line 6114

Is there anything I need to do on my end? If needed I can paste the site info if it helps.

This topic was modified 1 year, 5 months ago by lewisself12.
This topic was modified 1 year, 5 months ago by lewisself12.
This topic was modified 1 year, 5 months ago by lewisself12.

Viewing 5 replies - 1 through 5 (of 5 total)

Matthew

(@mhdizmni)

1 year, 5 months ago

Hi @lewisself12,

Thank you for starting this thread!

We would greatly appreciate it if you could share your site information with us, as it may help us replicate and investigate the issue more effectively.

Looking forward to your response!

Regards,
Matthew

Thread Starter

lewisself12

(@lewisself12)

1 year, 5 months ago

No problem please see below, we do have some custom plugins and a custom theme which I can disable if needed.

` wp-core

version: 6.7.1
site_language: en_GB
user_language: en_GB
timezone: Europe/London
permalink: /%postname%/
https_status: false
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: open
environment_type: local
user_count: 1
dotorg_communication: true wp-paths-sizes

wordpress_path: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public
wordpress_size: 64.06 MB (67171931 bytes)
uploads_path: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public/wp-content/uploads
uploads_size: 58.24 MB (61072145 bytes)
themes_path: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public/wp-content/themes
themes_size: 15.02 MB (15745345 bytes)
plugins_path: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public/wp-content/plugins
plugins_size: 91.92 MB (96380267 bytes)
fonts_path: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public/wp-content/uploads/fonts
fonts_size: directory not found
database_size: 9.19 MB (9633792 bytes)
total_size: 238.42 MB (250003480 bytes) wp-active-theme

name: Cell Pack Solutions (cell-pack-solutions-1)
version: 5.3.1
author: @jonathanww, @lewisself64 & @AaronAdlington
author_website: https://github.com/cell-pack-solutions/
parent_theme: none
theme_features: core-block-patterns, widgets-block-editor, post-thumbnails, wc-product-gallery-lightbox, widgets, editor-color-palette, html5, align-wide, automatic-feed-links, title-tag, woocommerce, menus
theme_path: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public/wp-content/themes/cell-pack-solutions-1
auto_update: Disabled wp-themes-inactive (1)

Twenty Twenty-Five: version: 1.0, author: the WordPress team, Auto-updates disabled wp-plugins-active (16)

Antispam Bee: version: 2.11.7, author: pluginkollektiv, Auto-updates disabled
Brevo - WooCommerce Email Marketing: version: 4.0.32, author: Brevo, Auto-updates disabled
Cell Pack Solutions Blocks: version: 1.0.0, author: lewisself64, Auto-updates disabled
Fake Pay For WooCommerce: version: 1.1.0, author: Anthony Graddy, Auto-updates disabled
Relevanssi: version: 4.24.2, author: Mikko Saari (latest version: 4.24.3), Auto-updates disabled
Safe SVG: version: 2.3.1, author: 10up, Auto-updates disabled
Sequential Order Numbers for WooCommerce: version: 1.6.7, author: WebToffee, Auto-updates disabled
ShortPixel Image Optimizer: version: 6.0.4, author: ShortPixel - Convert WebP/AVIF & Optimize Images, Auto-updates disabled
TawkTo Manager: version: 2.2.2, author: Daniel Mulder, Auto-updates disabled
Timeline Block: version: 1.0.7, author: bPlugins, Auto-updates disabled
WooCommerce: version: 9.4.3, author: Automattic (latest version: 9.5.1), Auto-updates disabled
WooCommerce Checkout Customer Source: version: 1.1.1, author: lewisself64, Auto-updates disabled
WooCommerce Email Test: version: 1.2.2, author: RaiserWeb, Auto-updates disabled
WooCommerce Product Stock Notification Email: version: 1.5.3, author: Lewis Self, Auto-updates disabled
WP Statistics: version: 14.11.4, author: VeronaLabs (latest version: 14.12), Auto-updates disabled
Yoast SEO: version: 24.0, author: Team Yoast (latest version: 24.1), Auto-updates disabled wp-media

image_editor: WP_Image_Editor_GD
imagick_module_version: Not available
imagemagick_version: Not available
imagick_version: Not available
file_uploads: 1
post_max_size: 1000M
upload_max_filesize: 300M
max_effective_size: 300 MB
max_file_uploads: 20
gd_version: bundled (2.1.0 compatible)
gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM
ghostscript_version: not available wp-server

server_architecture: Windows NT 10.0 AMD64
httpd_software: nginx/1.16.0
php_version: 8.1.9 64bit
php_sapi: cgi-fcgi
max_input_variables: 4000
time_limit: 1200
memory_limit: 256M
max_input_time: 600
upload_max_filesize: 300M
php_post_max_size: 1000M
curl_version: 7.77.0 OpenSSL/1.1.1q
suhosin: false
imagick_availability: false
pretty_permalinks: true
htaccess_extra_rules: false
current: 2025-01-06T09:00:40+00:00
utc-time: Monday, 06-Jan-25 09:00:40 UTC
server-time: 2025-01-06T09:00:39+00:00 wp-database

extension: mysqli
server_version: 8.0.16
client_version: mysqlnd 8.1.9
max_allowed_packet: 16777216
max_connections: 151 wp-constants

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public/wp-content
WP_PLUGIN_DIR: C:\Users\LewisSelf\Local Sites\cell-pack-solutions\app\public/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: true
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: true
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: local
WP_DEVELOPMENT_MODE: undefined
DB_CHARSET: utf8
DB_COLLATE: undefined wp-filesystem

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
fonts: writable wp_statistics

version: 14.11.4
detectActiveCachePlugin: Disabled
activePostTypes: post, page, product
dailySaltDate: undefined
geoIpDatabaseExists: Yes
geoIpDatabaseLastUpdated: 2025-01-03 10:03:47
geoIpDatabaseSize: 55 MB
geoIpDatabaseType: GeoLite2-City
geoIpDatabaseValidation: Yes
monitorOnlineVisitors: Enabled
trackLoggedInUserActivity: Disabled
storeEntireUserAgentString: Disabled
attributionModel: first-touch
trackingMethod: Client Side Tracking
bypassAdBlockers: Disabled
anonymizeIpAddresses: Enabled
hashIpAddresses: Enabled
wpConsentLevelIntegration: Disabled
anonymousTracking: Disabled
doNotTrack: Disabled
viewStatsInEditor: Enable
viewsColumnInContentList: Enable
viewsColumnInUserList: Disabled
showStatsInAdminMenuBar: Enabled
wpStatisticsChartsPrevPeriod: Enabled
wpStatisticsWidgets: Enable
disableInactiveFeatureNotices: Disabled
viewsInSingleContents: Disabled
reportFrequency: Disabled
userRoleExclusions: Administrator
ipExclusions: Not Set
excludedLoginPage: Enabled
excludedRssFeeds: Enabled
excluded404Page: Disabled
excludedURLs: Not Set
matomoReferrerSpamBlacklist: Enabled
logRecordExclusions: Disabled
minRoleToViewStats: manage_options
minRoleToManageSettings: manage_options
ipDetectionMethod: sequential
geoIpDatabaseUpdateSource: js-deliver
automaticCleanup: Enabled
purgeDataOlderThan: 180
phpGmpExtension: Not Installed
phpBcmathExtension: Installed
phpGzopenFunction: Installed
phpPharDataClass: Installed

Matthew

(@mhdizmni)

1 year, 5 months ago

Dear @lewisself12,

After reviewing the settings for WP Statistics, it appears that only the manage_options capability is checked. You can find the settings by navigating to Statistics > Settings > Roles & Permissions.

Based on this, the issue is likely being caused by another plugin. To pinpoint the source, could you please deactivate all plugins and then reactivate them one by one? This will help determine which plugin is triggering the notices.

Thank you for your cooperation!

Regards,
Matthew

Thread Starter

lewisself12

(@lewisself12)

1 year, 5 months ago

Thanks for this, I’ve done the above and WooCommerce was the plugin which seems to be causing the issue. To make sure I also disabled every other plugin and just had WooCommerce and the error was still persisting.

Matthew

(@mhdizmni)

1 year, 5 months ago

Thank you for the update!

It seems that these notices are caused by WooCommerce, as we have recently encountered them ourselves.

I’ll go ahead and mark this topic as “Resolved”.

Regards,
Matthew

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Roles and Permissions errors page’ is closed to new replies.