Cameron Barrett

I had the same issue on a multisite install (PHP 7.4). Manually deleting the plugin and re-installing it from the repository fixed the error.

The cbarrett user is an Editor Role.

https://www.dropbox.com/scl/fi/79xdkl28q0ryp380jv6zu/role-is-editor-not-admin.png?rlkey=pmkgl15fjvskriq2gnbpi22ep&dl=0

The cameronbarrett user is a SuperAdmin/Admin Role. This user configured the Site Kit for the subsite, but the Site Kit sharing settings clearly say to allow WordPress Role of “Editor” to see the data.

I will move this post to a new Support Topic, though it clearly appears to be the same issue as @shadician posted about.

Neither the WP Dashboard or the Google Site Kit dashboard are showing the view-only metrics data for an Editor Role who is logged in, despite the View-Only Sharing Settings being set to Editor Role.

Screenshot: Admin Logged In Sharing Settings
https://www.dropbox.com/scl/fi/j52fptjurxhulgi111iz0/admin-view-settings.png?rlkey=j5rjcz6x7brsoqfc4x9edfy76&dl=0

Screenshot: Editor Logged in WP Dashboard View
https://www.dropbox.com/scl/fi/jskrrbn8b7r7flcsboutj/editor-view-WP-dashboard.png?rlkey=rmhxq82hstjgd54lasdxgdzhk&dl=0

Screenshot: Editor Logged in Google Site Kit Dashboard View
https://www.dropbox.com/scl/fi/7hy41f8ybheh1vfjdkhjq/editor-view-GSK-dashboard.png?rlkey=lnuh3pdccc9spy0civ0xyxq0q&dl=0

Note: This is a subsite on a subdirectory multisite install.

• This reply was modified 1 year, 4 months ago by Cameron Barrett.

I’m having this same issue. People in a non-admin role (Editor, etc) cannot see Google Analytics data in their dashboard despite the UI indicating that their Role is granted this access. Only the admin who set up the connection in the first place can see the view-only data.

This is definitely a PHP 8.x issue. The most recent version of the plugin works fine with PHP 7.4 but gives a Fatal Error upon activation when running PHP 8.0.

Excellent. This solved my issues as well.

Unfortunately, my team has been unable to take over the development of this plugin as we had hoped. It needs a complete rewrite from the ground up, especially its Folder Creation and Management process.

I am currently moving over 100 websites I manage to use other solutions. I recommend you do the same, as this plugin will continue to break. It does not work with PHP 8.0.

It truly was a wonderful plugin and I’ve built some fantastic document libraries with it. It’s a difficult plugin to replace, but there are some that come fairly close to providing the same functionality.

This plugin will not work with PHP 8.0 until it gets a rewrite. The developer abandoned the plugin well over a year ago and has indicated he will no longer be maintaining it.

My suggestion is to start looking for an alternate plugin. Sorry. I am dealing with this issue as well and moving at least 100 websites to other document library solutions.

For natively-translated text, we prevent GTranslate from firing using the “notranslate” class. This is for obvious reasons. A user has chosen a language from the WPML links (and not the GTranslate select menu) so we deliver that text via WMPL.

I would advise you not show that message/warning. It’s not helpful and not accurate either. Or please add an option to GTranslate settings to hide the warning.

Thanks, I can’t test this update today but will do a test with 2.3.1 later this evening.

The client is only using this plugin to inject Google Tag Manager code, so I’ve instructed them to move that to Google Site Kit, but I will work with you to try to resolve this error.

• This reply was modified 3 years, 7 months ago by Cameron Barrett.

This is still happening when I upgrade to 2.3.0

Fatal error: Uncaught Error: Call to undefined function wp_get_current_user() in /var/www/southsideisd.org/htdocs/wp-includes/capabilities.php:692 Stack trace: #0 /var/www/southsideisd.org/htdocs/wp-admin/network/settings.php(16): current_user_can() #1 /var/www/southsideisd.org/htdocs/wp-content/plugins/tag-manager-header-body-footer/include/install.php(11): include('/var/www/souths...') #2 /var/www/southsideisd.org/htdocs/wp-content/plugins/tag-manager-header-body-footer/index.php(40): require_once('/var/www/souths...') #3 /var/www/southsideisd.org/htdocs/wp-settings.php(339): include_once('/var/www/souths...') #4 /var/www/southsideisd.org/wp-config.php(125): require_once('/var/www/souths...') #5 /var/www/southsideisd.org/htdocs/wp-load.php(42): require_once('/var/www/souths...') #6 /var/www/southsideisd.org/htdocs/wp-admin/admin.php(34): require_once('/var/www/souths...') #7 /var/www/southsideisd.org/htdocs/wp-admin/network/admin.php(13): require_once('/var/www/souths...') #8 /var/www/southsideisd.org/htdocs/wp-admin/ne in /var/www/southsideisd.org/htdocs/wp-includes/capabilities.php on line 692

Rolling back to previous version fixes this.

This broke for me, too. Upgrading WordPress to 5.5.1 solves it.

Upgrading to 7.0.1 solves this issue. Thanks!

Thanks, that works perfectly!

We were having this issue also, and updating to 3.9.8 fixes it.

We were also experiencing issues when a user uses the “Download” button and then clicks the download from their browser to open in a PDF viewer, they were getting “There was an error opening this document. The file is damaged and could not be opened” errors. However, clicking the download icons from the local browser preview, saving the PDF to their Desktop and then opening would work just fine. A similar thing was happening with Excel spreadsheets and newer versions of Office.

The latest update to 3.9.8 seems to have resolved these issues. I’m still testing.