It’s not difficult. You need to transfer files to the new server. Create a blank database and keep it’s name, user_name (this user must have all privileges of this newly created database) and password. Edit config.php file on new server with the these new details. Read: WordPress Codex for transferring site
If you’ve got access to the mysql database, you can change the grant tables directly: UPDATE mysql.user SET Host=”%” WHERE Host=”localhost” AND User=”username”; …and an analogous UPDATE-statement to change it back. Also you might need to make changes to the mysql.db table as well: UPDATE mysql.db SET Host=”%” WHERE Host=”localhost” AND User=”username”; and then flush … Read more
WordPress absolutely does need “DELETE“, otherwise it has no way to delete posts or tags or options rows or anything else. The “DROP” command is sometimes used during upgrades, although it’s been a long time. The last time I think it was used was during the WordPress 2.3 update, which removed the assorted categories tables … Read more
Why do your own database queries? Use the WP functions to do it for you. $empid = (int) $_REQUEST[’empid’]; $name = get_user_meta($empid, ‘first_name’, true) . ‘ ‘ . get_user_meta($empid, ‘last_name’, true);
Bulk of WP’s native data structures aren’t meant for direct MySQL access. They are typically accessed via PHP APIs which take care of MySQL generation/execution and many more things, such as allowing to filter data, caching it for performance, and so on. Your issue here is that from MySQL point of view meta values aren’t … Read more
Use stripslashes to remove the slashes. For example: echo stripslashes( $field );
You’re including the table prefix, but $wpdb takes care of that. Change: $query = $wpdb->prepare( “SELECT * FROM $wpdb->wp_terms INNER JOIN $wpdb->wp_term_taxonomy ON ($wpdb->wp_terms.term_id = $wpdb->wp_term_taxonomy.term_id) WHERE $wpdb->wp_terms.name LIKE %s AND $wpdb->wp_terms.count > 0”, $wpdb->esc_like($keyword) . ‘%’); To: $query = $wpdb->prepare( “SELECT * FROM $wpdb->terms INNER JOIN $wpdb->term_taxonomy ON ($wpdb->terms.term_id = $wpdb->term_taxonomy.term_id) WHERE $wpdb->terms.name LIKE … Read more
As Chealion mentioned, there are several ways that your mysql could have been installed. Each of which will place your data dir and/or logs in different locations. The following command will give you (and us) a good indication of where to look. ps auxww|grep [m]ysqld # Putting brackets around the first char is a `grep`+`ps` … Read more
I did mysql> SHOW GLOBAL VARIABLES LIKE ‘PORT’; And that indicated that I was using port 3306 and that my search for the error continues.
You don’t need to write a custom SQL for this. You can always leverage WP’s get_post_custom() that returns array of all custom fields for a particular page or post. https://codex.wordpress.org/Function_Reference/get_post_custom