WP DB Location for “Next Post to Create” Index Value
WP DB Location for “Next Post to Create” Index Value
wpdb
Problem on wpdb queries, wp_insert_post, wp_insert_user etc. The query runs twice
I resolved my similar issue (see below code block) by modifying the path to wp-load.php. Actually I used Frankie Jaret’s uri parse script which really only works on the default install but, meh, that’s what I use. I’m sure you can find a function that will parse it out where ever it may reside. Code … Read more
What is the best practice to initialise $wpdb by loading wp-load.php?
What is the best practice to initialise $wpdb by loading wp-load.php?
using same mysql user with many databases
Well it’s really not good practise, but this depends on how you’re accessing the other databases. For example, I have a server that hosts 10+ different WordPress sites. I have two options for connecting to the databases: Use the root login in all my wp-config.php files as it’s easier Create a user and logins associated … Read more
pre_get_posts or $where, which one to use?
In general this would make sense at pre_get_posts since you could just express conditions as meta query and let WP figure out SQL. In your specific case this won’t work, since that format is horrible for programmatic comparison. Unless you can change format to something more friendly, you will probably have to write some pretty … Read more
Write mysql credentials in plugin
As long as you aren’t passing out the plugin and other people don’t have access to it, you should be fine. You might add something like the following to the top of the file just in case though: defined(‘ABSPATH’) or die(‘Access denied’); That will simply make sure that the file is loaded via wordpress (e.g. … Read more
Retrieve a list of users based on some conditions
Be careful with the ‘%subscriber%’ part, inside the wpdb::prepare() method. Use ‘%%subscriber%%’ instead. Otherwise $limit will match the %s part and the %d part will be unmatched.
why nl2br() is adding an extra ?
why nl2br() is adding an extra ?
Protect custom form from SQL injection
Yes, $wpdb->update is sufficient protection. You should not escape or prepare the data. From the documentation of wpdb: data (array) Data to update (in column => value pairs). Both $data columns and $data values should be “raw” (neither should be SQL escaped). This means that if you are using GET or POST data you may … Read more
WordPress – wpdb query does not list same result as sql query
WordPress – wpdb query does not list same result as sql query