Fatal error: Uncaught TypeError

Resolved Rollaz
(@rollaz)

1 year, 11 months ago

Hello,

Im having backend issues with plugin. On subdomain where I was configuring all content etc. it was working fine, but when I moved all website to actual domain I started to get errors. Can not activate or download this plugin to start from scratch, getting Fatal error: Uncaught TypeError. What could be the issue?

Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/series/domains/xxx/public_html/wp-admin/includes/class-wp-privacy-policy-content.php:232 Stack trace: #0 /home/series/domains/xxx/public_html/wp-content/plugins/complianz-gdpr/documents/admin-class-documents.php(47): WP_Privacy_Policy_Content::get_suggested_policy_text() #1 /home/series/domains/xxx/public_html/wp-content/plugins/complianz-gdpr/class-admin.php(68): cmplz_documents_admin->preload_privacy_info() #2 /home/series/domains/xxx/public_html/wp-includes/class-wp-hook.php(324): cmplz_admin->activation() #3 /home/series/domains/xxx/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #4 /home/series/domains/xxx/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /home/series/domains/xxx/public_html/wp-admin/admin.php(175): do_action() #6 /home/series/domains/xxx/public_html/wp-admin/plugins.php(10): require_once('/home/series/do…') #7 {main} thrown in /home/series/domains/xxx/public_html/wp-admin/includes/class-wp-privacy-policy-content.php on line 232

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

Plugin Support fritsiub
(@fritsiub)

1 year, 11 months ago

Hi Roliaz,

Thank you for your message, I’m sorry to hear of your issues.

In order to help you find a swift resolution, we kindly ask you to enable Debugging on WordPress https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/#example-wp-config-php-for-debugging), by adding: define( ‘WP_DEBUG’, true ); in the wp-config.php file, and re-triggering the error once more.

This will provide us with additional information regarding the exact error message. Kindly share this with us so that we can try and accurately diagnose the root cause of the error.

We are limited in our communication due to the general forum guidelines, but we’ll do our best to help you of course.

We look forward to hearing from you.
Thread Starter Rollaz
(@rollaz)

1 year, 11 months ago
Nothing new, the same error when trying to enable plugin:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /home/series/domains/xxx/public_html/wp-admin/includes/class-wp-privacy-policy-content.php:232 Stack trace: #0 /home/series/domains/xxx/public_html/wp-content/plugins/x-complianz-gdpr/documents/admin-class-documents.php(47): WP_Privacy_Policy_Content::get_suggested_policy_text() #1 /home/series/domains/xxx/public_html/wp-content/plugins/x-complianz-gdpr/class-admin.php(68): cmplz_documents_admin->preload_privacy_info() #2 /home/series/domains/xxx/public_html/wp-includes/class-wp-hook.php(324): cmplz_admin->activation() #3 /home/series/domains/xxx/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #4 /home/series/domains/xxx/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /home/series/domains/xxx/public_html/wp-admin/admin.php(175): do_action() #6 /home/series/domains/xxx/public_html/wp-admin/plugins.php(10): require_once('/home/series/do…') #7 {main} thrown in /home/series/domains/xxx/public_html/wp-admin/includes/class-wp-privacy-policy-content.php on line 232 There has been a critical error on this website. Please check your site admin email inbox for instructions.
- This reply was modified 1 year, 11 months ago by Rollaz.
Plugin Support daniub
(@daniub)

1 year, 11 months ago

Hi,

what it looks like is that another plugin adds a Suggested Privacy Policy text, but does it in a different way than expected, whereby it causes an issue when Complianz tries to use the Suggested Privacy Policy text from that plugin. I would recommend to check if this issue persists with Complianz as the sole activated plugin.

We suspect that the issue won’t occur in this case, so then you can re-enable plugins one by one until the issue happens again; at which point you’ll know exactly which plugin causes the issue to occur.

As a further step please also update Complianz plugin.

Hope this helps

Thread Starter Rollaz
(@rollaz)

1 year, 10 months ago

Disabling all other plugins did not solve this issue.
For now moved to other plugin, will investigate later.
Thank you.

braino
(@braino)

1 year, 6 months ago

i am having the same issue

nirvanagold
(@nirvanagold)

1 year, 6 months ago

Likewise – same issue and stacktrace. The plugin was configured and all looking good, but I discovered this issue after deactivating Complianz then activating it again (that’s when it triggered).

I had deactivated the plugin because I was noticing that after any plugin update or install, WP said it had failed, even though the plugin would actually install. I suspect those warnings were related to this issue, as they are not happening now with Complianz deactivated. (I disabled all plugins and re-enabled, one by one, testing.)

I note this plugin is “not tested with version 6.7 of WordPress”. I’ll deactivate it and wait until there is a fix for the above.

nirvanagold
(@nirvanagold)

1 year, 4 months ago

Just to say this is no longer an issue for me with latest version of the plugin. I’m not sure why, but I’ve been able to re-enable it!

Plugin Support leonardoiub
(@leonardotamion)

1 year, 4 months ago

@nirvanagold thanks for your feedback!