Digma

That is indeed weird. As it occured right after the upgrade of Disable Comments and no other upgrades or patches were available at that point, nor was I working on anything.

*cough* came of my lazy but and had a look at the error log.

Seems that the upgrade re-wrote the .htaccess in the root of the wordpress folder, but did not completely take along the full code.

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /test/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /test/index.php [L]
</IfModule>

# END WordPress
rite.c>
RewriteEngine On
RewriteBase /test/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /test/index.php [L]
</IfModule>

# END WordPress

You might want to check the installation process of the upgrade.

I have got it fixed now by removing the second bit and continue using disable comments. ??

Thanks for getting back at me.

Edit: for future reference, this was what was in the error log:
.htaccess: </IfModule> without matching <IfModule> section

As a follow up on the above.

I have noticed that as soon as Worpress produces zero results (not shown as error), the Widgets made by widget builder do not work anymore. At least not its contents.

I’ll wait for the release of 2.8.2.

We haven’t released the new design using WP (we changed CMS) yet, so a couple of days more or less won’t matter that much.

Thanks for getting back on this.

Many thanks for supplying this solution. It solved both problems together.

Before the wrong idea is being raised here. The patch did not solve the initial problem of the dropdown array not saving.

For the fatal error there is a patch:
https://rocketgeek.com/blog/wp-members-2-8-1-str_getcsv-patch-for-php-5-3/