Skip Navigation

[Resolved] Error when Access plugin activated

This support ticket is created 5 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 7 replies, has 2 voices.

Last updated by leilaG 5 years, 7 months ago.

Assisted by: Christian Cox.

Author
Posts
#1226300

Hello, when we activate the Access plugin we get this error message in the admin panel

Notice: Undefined offset: 0 in /nas/content/live/biocityhq/wp-includes/capabilities.php on line 136

#1226889

Hi, have you tried the standard troubleshooting steps? Let's try to rule out a plugin or theme conflict:
- Temporarily deactivate all plugins except Types, Views and Access. Activate a default theme like Twenty Nineteen, then test again.
- If the problem is resolved, reactivate your theme and other plugins one by one until the problem returns. Try to isolate one source of conflict.
- If the problem is not resolved, try updating WordPress to the latest version. Turn on error logs and see if any more information about the error is available.

Let me know if you're able to determine anything from those tests, and we can go from there.

#1227049

Thanks for the instructions, after trouble shooting, it seems when the plugin Awesome support is active along with Toolset Access this error occurs.

Any suggestions on what to do next to resolve this?

#1227866

Let me ask my 2nd tier support team to take a look. It might be possible to find a workaround...I'll let you know what I find out.

#1246012

Hey! just checking if there are any updates on this?

#1246126

Hi, nothing new to share. I can see this ticket has been escalated to our compatibility team but no permanent solution yet. I'll keep you posted here.

#1248145

Our team was in contact with a 3rd tier support team member at Awesome Support to report the issue in their code, and received the following information:

Thank you for contacting Awesome Support and thank you for bringing this issue to our attention. I have passed on this information to my team for further review.

Here is a description of the issue:
They use current_user_can function in their code for whatever.
Codex mentions that current_user_can accepts the cabability and the user id as parameters.
The user id us optional but if it's not being passed, the warning mentioned here in this ticket will be raised.

Check the Parameters section in : https://codex.wordpress.org/Function_Reference/current_user_can

Example place where they misused the function: \plugins\awesome-support\includes\functions-admin-bar.php

	if ( ! current_user_can( 'edit_ticket' ) ) {
		return;
	}
#1252801

Thanks for trouble shooting this, I'll get in touch with Awesome support.