The effects of alcohol on
sustanon 250 leucine for – real weight loss & bodybuilding benefits?
Bug Fatal error: Uncaught TypeError
How-to and Troubleshooting
(@miba)
Active Member
Joined: 3 months ago
When runnig the wizard of wpDiscuz, I get a fatal error as soon as I click next. The strange thing is, that when I do the same thing on my staging website, the plugin works.
The Debug log says:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /var/www/html/wordpress/wp-content/plugins/wpdiscuz/options/class.WpdiscuzOptions.php:1355 Stack trace: #0 /var/www/html/wordpress/wp-includes/class-wp-hook.php(324): WpdiscuzOptions->saveAndResetOptionsAndPhrases() #1 /var/www/html/wordpress/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /var/www/html/wordpress/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /var/www/html/wordpress/wp-admin/admin.php(176): do_action() #4 {main} thrown in /var/www/html/wordpress/wp-content/plugins/wpdiscuz/options/class.WpdiscuzOptions.php on line 1355
(@miba)
Active Member
Joined: 3 months ago
Meanwhile I tried to deactivate all other Plugins. But no changes. Still the same error.
I use WordPress Version 6.8.2 ans wpDiscus Version 7.6.33
(@asti)
Joined: 8 years ago
Illustrious Member
Posts: 8190
Aug 30, 2025 9:48 am
@miba
We don't find such an issue on our test websites. Could you please send the admin login details to info[at]gvectors.com email address? I'll ask the developers to check the issue for you.
(@miba)
Joined: 3 months ago
Active Member
Posts: 3
Sep 02, 2025 10:58 am
@asti The installation runs on a local server on the intranet. Therefore, we cannot provide you with any access data. We have now adjusted the incorrect block in “options/class.WpdiscuzOptions.php” and it is working. But we're wondering why no one else has a problem with it.
(@alyxjame)
New Member
Joined: 7 months ago
It looks like the error is coming from WpdiscuzOptions.php when the wizard tries to save or reset options. The Cannot access offset of type string on string usually means the function expects an array but is receiving a string instead.
A couple of things you can try:
- Clear plugin cache / options: Sometimes wpDiscuz stores options in the database that can get corrupted. Try resetting options (from staging if possible) or clearing the plugin’s cache.
- Check PHP version: This error often shows up on PHP 8.x, as it’s stricter with array/string offsets. If your staging site is on PHP 7.4 and production on PHP 8+, that would explain why it only breaks on live.
- Reinstall wpDiscuz: Download the latest version from WordPress.org, delete (don’t just deactivate) the plugin folder on your live site, and reinstall fresh. Your comments should stay intact since they’re stored in the database.
- Check for conflicts: Temporarily disable other plugins and switch to a default theme to rule out conflicts.
If none of the above helps, you may want to share your PHP version, WordPress version, and wpDiscuz version so the devs/community can better reproduce the issue.
