7.0.2: Critical error, Uncaught Error: [] operator not supported for strings...

Sabinooo · 2020-06-06T19:35:44Z

Hello, I had to disable wpdiscuz in an emergency, right after the upgrade to the new 7 branch (I waited till it got its second update, old habits of being careful) I found it turned every post’s page into a white page of death. Error log, kindly emailed by wordpress: WordPress version 5.3.3Current theme: perso (version 2020.1)Current plugin: wpDiscuz (version 7.0.2)PHP version 7.2.31-1+0~20200514.41+debian10~1.gbpe2a56b Error Details=============An error of type E_ERROR was caused in line 1389 of the file /home/blogpaul/public_html/wp-content/plugins/wpdiscuz/class.WpdiscuzCore.php. Error message: Uncaught Error: [] operator not supported for strings in /home/blogpaul/public_html/wp-content/plugins/wpdiscuz/class.WpdiscuzCore.php:1389Stack trace:#0 /home/blogpaul/public_html/wp-includes/class-wp-hook.php(290): WpdiscuzCore->addPluginSettingsLink(‘ * Server: Debian 10, LAMP, MariaDB, php 7.3 fcgi. Tried switching to a default theme, still the same. Presence of wp-supercache and cloudflare, but the tests were repeated after emptying supercache, purging cloudflare, putting cloudflare in development mode, and purging supercache again: same thing. * After this, I allowed wordpress to upate itself to the 5.4 branch, it made no difference, unfortunately. I disabled the plugin by renaming its folder in the wp-content directory, tried reactivating it once, had the same error. * Downloading the former version of wpdizcuz, 5.3.5 from wordpress.org and reuploading it instead fixed the main issue, although most of my styling options are gone, and I had to toggle the option to use the native wordpress Ajax otherwise adding commments wouldn't work, sigh.But, hey, not gonna complain, it’s already an improvement over dead blog post pages. * If you guys want more testing, I’m ready to test with any version you like, I’d like to get that fixed, so I don’t mind trying stuff. LMK, otherwise, you now have my bug report.