Errors on new version 0.9.8

What version of WordPress do you have? mysqli support is only in 3.9 and later.

I have WP 4.0

I have noticed that in my wp-config.php the word “FALSE” is written all lower caps so I tried to change it to “false” but it did not solve.

Your WordPress install is still using the mysql extension, not mysqli.

Two more things you could check. One, check the output of phpinfo and make sure you have mysqli installed.

(if you don’t know what that is, just put

<?php phpinfo();

in a file called something.php and load it through your browser)

Second, I suppose it’s possible that the constant WP_USE_EXT_MYSQL is already being set to true somewhere. You could try moving this line to the top of your wp-config.php file.

If you’re still stuck I could look at your wp-config.php.

Hi, I made the file, you can find it here.
The wp-config.php does not contain any reference to Sqli

Thanks, you can delete that file now.

It confirms what I originally thought from the stack trace, that your PHP has mysqli enabled but for some reason WordPress is choosing to use mysql extension instead of mysqli.

If you like you can post your wp-config.php (maybe just copy and rename it to .txt on your web server) and I’ll look at it — be sure to x out your database username/password/server in it so I can’t see them though.

The line you’re supposed to add to wp-config.php:

define('WP_USE_EXT_MYSQL', FALSE);

defines the constant WP_USE_EXT_MYSQL as false, that should be all you have to do. You can’t “redefine” a constant so it’s possible this is already set to true, that’s why I suggested moving it to the top of your wp-config.php. It could also be defined in index.php or elsewhere. I would not expect any of these, but you never know.

The previous version 0.9.1 of the plugin will work fine, the only changes in 0.9.8 were to change to mysqli, you can always use the old version.

I did post the wp-config here.

Seems now after place the line of code at the beginning the error are gone but, I don’t know if this is an error or what, I still see:

2014-10-19T13:49:13+0200 Could not SHOW INDEX on database table cwp_comments.
2014-10-20T13:04:42+0200 Could not SHOW INDEX on database table cwp_comments.

Is this correct?

Those look like those are lines in the User Spam Remover log file … the timestamps are about a day apart.

You can see the location of that file if you scroll down the settings page. You might try deleting that file and then reloading the settings page to see if those errors reoccur.

I don’t think they should … I think that everything is working now.

That error is when User Spam Remover tries to run the SQL query: show index from wp_comments; (or replace wp_comments with whatever your comments table is named). If these errors *do* show up again then it is unusual that the message say “cwp_comments” instead of “wp_comments” unless your comments table is actually “cwp_comments” (this WP prefix is configurable … it looks like you have $table_prefix set to something so that may be OK)

Hi,

So this is a more common problem than I thought. I had a similar thing, also on WP 4.0:

Warning: mysqli_query() expects parameter 1 to be mysqli, resource given in /home/sitename/public_html/wp-content/plugins/user-spam-remover/user-spam-remover.php on line 795

So do I just go ahead and add this line to the wp-config.php file:

define(‘WP_USE_EXT_MYSQL’, FALSE);

Would this affect existing databases in case they are using mysql?

No, no effect on your database at all. This is just WordPress’ configuration setting for which PHP API to use, no effect on underlying data.

You’re right that this is a flag that most users of this extension will probably need to set. For now WordPress (still) isn’t selecting the mysqli interface by default, even though PHP has deprecated the old mysql one and will actually throw a warning level error in PHP 5 and later.

The problem is solved after delete the log file and move the code to the top of the wp-config.php
Thank you!

OK, glad to hear it!

I will do some testing on the placement of the config line in wp-config.php and clarify the instructions for future. Sorry for the troubles with mysqli, hopefully WordPress core will change to just default to mysqli in all PHP 5 versions (I can maybe lobby for this in 4.1) and then this complication will go away.

FWIW I did update the readme to suggest adding the WP_USE_EXT_MYSQL line near the top of wp-config.php with all the other DB settings.

In fact it can be included anywhere except at the very bottom of the file. After wp-settings.php is required in (the very last line) it will have no effect.