• Resolved meganmasterson

    (@meganmasterson)


    Hello,

    I’ve been working with our marketing partner to determine why a certain user role has no access to individual events. When this specific role attempts to view an event, they receive this error: https://ibb.co/Cp9mmrnq

    We’ve gone through and deactivated all plugins on our staging site and determined the PublishPress Permissions plugin was the one causing the issue. We’ve updated the role to include Read permissions (even though on the User Role level they should have access) and it’s still throwing that error. Any pieces of advice to help troubleshoot this?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Steve Burge

    (@stevejburge)

    @meganmasterson Thanks for using PublishPress. The first step is find the error message.

    WordPress will email the error message to the site administrator. You can also find it in your hosting company’s error logs or by installing a plugin like this: https://wordpress.org/plugins/debug-log-manager/

    Thread Starter meganmasterson

    (@meganmasterson)

    @stevejburge

    Here’s some info that we pulled recently:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the learndash-notifications 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 /nas/content/live/clientport1stg/wp-includes/functions.php on line 6121

    Deprecated: Creation of dynamic property PublishPress\Permissions::$default_advanced_options is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/publishpress/publishpress-permissions/classes/PublishPress/Permissions.php on line 186

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the presspermit-pro 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 /nas/content/live/clientport1stg/wp-includes/functions.php on line 6121

    Deprecated: Creation of dynamic property LearnDash_Notifications_Status_Page::$show_settings_page_function is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/learndash-learndash-notifications-40c18854865d/includes/admin/class-status-page.php on line 17

    Deprecated: Creation of dynamic property LearnDash_Notifications_Logs_Page::$show_settings_page_function is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/learndash-learndash-notifications-40c18854865d/includes/admin/class-logs-page.php on line 12

    Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 133

    Deprecated: Return type of Pimple\Container::offsetGet($id) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 98

    Deprecated: Return type of Pimple\Container::offsetSet($id, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 79

    Deprecated: Return type of Pimple\Container::offsetUnset($id) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/vendor/pimple/pimple/src/Pimple/Container.php on line 143

    Deprecated: Creation of dynamic property PublishPress\EDD_SL_Plugin_Updater::$beta is deprecated in /nas/content/live/clientport1stg/wp-content/plugins/presspermit-pro/includes-pro/library/edd-sl-plugin-updater/EDD_SL_Plugin_Updater.php on line 50

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks @meganmasterson. It looks like yu’re using the Pro version of our plugin.

    Can I ask you to open a support ticket on our site, please?

    We’re not allowed to support our commercial products here on the WordPress forums: https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products

    Thread Starter meganmasterson

    (@meganmasterson)

    @stevejburge So… unfortunately I can’t because the user who owned the credentials for the site no longer works with us and I have no way of accessing those credentials. Do you have another route I could take to get assistance?

    Plugin Author Steve Burge

    (@stevejburge)

    You’re welcome to contact us via help @ publishpress.com and share the details you have. We can get you access to the account.

    Thread Starter meganmasterson

    (@meganmasterson)

    @stevejburge Thank you so much!! Have a great weekend 🙂

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks. We got your email and replied.

    Plugin Author Kevin Behrens

    (@kevinb)

    @meganmasterson The first “Deprecated” entry in the error log you shared is from a portion of the Permissions Free code, so I will comment on it here. That error was fixed over 2 years ago, so it seems you are either running an old version of the plugin or copying old error log entries. Please be sure to update to the current plugin release before reporting errors. If you have trouble updating the pro plugin, we can help with that through help @ publishpress.com

    Thread Starter meganmasterson

    (@meganmasterson)

    @kevinb Thanks so much for the insight, I believe it is due to being on an outdated version. I’m working with our marketing/site support to get it updated because it’s not wanting to update for me so I may be in contact if we can’t get it sorted. Thanks again!

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

The topic ‘Critical Error for Some Users’ is closed to new replies.