Need help with mysqli_query()

LuckyGirl9334

Regular Member
Jr. VIP
Joined
Aug 26, 2018
Messages
298
Reaction score
169
I just uploaded a new plugin to my wordpress site and immediately inside the interface I got this warning:

Warning: mysqli_query(): Empty query in /home/lucindabrummitt/public_html/blog/wp-includes/wp-db.php on line 1924

I have no idea how to fix this. For somebody here it may be simple. Any pointers? Suggestions?

Thanks in advance.:D
 

Attachments

  • screenshot-mywebsite- linkmaster plugin.png
    screenshot-mywebsite- linkmaster plugin.png
    51.5 KB · Views: 259
If you have FTP access into your host go in and remove the plugin you just (well how many days ago now) uploaded. All WordPress plugins resided in

/your_main_folder/wp-content/pluings/

Careful with any NULL scripts you might "find" around. Lot of them are bunk.

Docker is your friend.
 
@RSS Spider hey thanks for getting back to me. I already took it out a few days back because it scared the bejeezus outta me. Appreciate you trying to help.
 
I just uploaded a new plugin to my wordpress site and immediately inside the interface I got this warning:

Warning: mysqli_query(): Empty query in /home/lucindabrummitt/public_html/blog/wp-includes/wp-db.php on line 1924

I have no idea how to fix this. For somebody here it may be simple. Any pointers? Suggestions?

Thanks in advance.:D

Was this plugin found in the WordPress Plugins directory? If so, can you check its page in the directory and see what major version it last supported? If it's 5.0+ (or even the high 4.x releases usually), then it's likely a plugin conflict rather than a broken plugin.
 
Was this plugin found in the WordPress Plugins directory? If so, can you check its page in the directory and see what major version it last supported? If it's 5.0+ (or even the high 4.x releases usually), then it's likely a plugin conflict rather than a broken plugin.

Hey thanks for the reply. No it was a paid plugin. I contacted the developer - through his affiliate that I bought it through. He said and I quote'" it's not an issue - it's just a warning."
I told him it broke my site and asked if he could just check the coding. He told me if I didn't like it don't use it. SMH.

Thanks for trying to help though, its much appreciated.
 
Hey thanks for the reply. No it was a paid plugin. I contacted the developer - through his affiliate that I bought it through. He said and I quote'" it's not an issue - it's just a warning."
I told him it broke my site and asked if he could just check the coding. He told me if I didn't like it don't use it. SMH.

Thanks for trying to help though, its much appreciated.

That's a shame. For a paid plugin, I'd expect better support. That said, he is right, it is only a warning. I think there's more going on that caused it to break your site. Typically production environments don't display PHP warnings; perhaps talk to your host about this.
 
That's a shame. For a paid plugin, I'd expect better support. That said, he is right, it is only a warning. I think there's more going on that caused it to break your site. Typically production environments don't display PHP warnings; perhaps talk to your host about this.
It is an E_WARNING I think after looking at the documentation for mysql_query. Apparently it isn't documented. Just curious if that is the case?
 
It is an E_WARNING I think after looking at the documentation for mysql_query. Apparently it isn't documented. Just curious if that is the case?

If you realy like the plugin you can just set your website php engine to suppress all warnings. That will fix it...
 
If you realy like the plugin you can just set your website php engine to suppress all warnings. That will fix it...

"A run-time warning. It is non-fatal and most errors tend to fall into this category. The execution of the script is not stopped." <- seems fine, but could be annoying. I don't see why it isn't documented for mysql_query(). lol.
 
"A run-time warning. It is non-fatal and most errors tend to fall into this category. The execution of the script is not stopped." <- seems fine, but could be annoying. I don't see why it isn't documented for mysql_query(). lol.

The documentation is there. All functions can throw an error if not used exactly right. In my php scripts whenever I hit this, I just suppress it at runtime with "@". You insert it at the beginning of the line of code causing the error.
 
Back
Top