It’s possible but requires help from an official WordPress support person (aka “Happiness Engineer”) to do it: As for stats, they can also be moved, but staff have to take care of that. Once you have Jetpack installed on the new WordPress.ORG install, post the relevant URLs in this forum thread and then add the … Read more
I’m assuming you have an sql file that you’re uploading? If so, open that file in a text editor such as Notepad. Search for ‘user_login’, and somewhere nearby that you should see something similar to ‘INSERT INTO wp_users (ID,user_login’ etc. On the next line after this, you should see something like (1, ‘admin’, ‘password’ where … Read more
Moving your sites My recommendation would be to use the the duplicator plugin. Far and away the easiest method I’ve used to back-up, move, and restore sites from local to production or from one host to another. If the old site is WordPress – sounds like it is, you may want to consider creating a … Read more
You’re almost there, it’s just the other way around: define(‘WP_HOME’,’http://www.m2comm-semi.com/new’); define(‘WP_SITEURL’,’http://www.m2comm-semi.com’); WP_HOMEis the URL where the actual files are and WP_SITEURL is the URL under which you access the site. Also be aware that this doesn’t go in the functions.php but in the wp-config.php The Admin is always accessible via the actual location of the … Read more
Commenting out the line innodb_force_recovery = 1 in /etc/my.cnf thus: # innodb_force_recovery = 1 made the mysql innodb tables in the database accessible. Apparently this setting causes innodb to become read-only. I hope this helps someone in the future. If you don’t have access to /etc/my.cnf on shared hosting, ask your host to fix it … Read more
I think htaccess would be fastest way. Overhead of checking 50 simple regexp is very small – page generation is several orders of magnitude slower so you shouldn’t care about it. This wont hit performance, you can set rewrite only for domain mysite.com and it won’t check rules for tech.mysite.com reducing overhead, which isn’t noticeable … Read more
jdm2112 identified the issue as being caused by missing tables as part of the migration process within the comments for the original question: You imported just the single table into another WordPress DB? THAT is the problem. Post IDs are unique between sites… I would avoid working with individual tables unless absolutely necessary After migrating … Read more
Unfortunately there’s nothing native in WordPress to handle searching and replacing your domain name across all your posts, options, etc. The closest you can get is WP-CLI’s search-replace command. It’s not an official WordPress project, but it has quite a high adoption rate, it’s very well maintained and available by default or on demand on … Read more
Do you have any access to the server? SSH access? If you can get to a command line on the server you could try one of these commands. Using sudo would try and run the command as an administrator, so you would need a password: unlink /path/to/symlink sudo unlink /path/to/symlink rm /path/to/symlink sudo rm /path/to/symlink
It’s not enough to edit wp-config.php file and wp-options table. You have to change all URLs and file paths in your database, including those serialized. Use WP Migrate DB or Duplicator plugins to do so. .htaccess file resides in the same server directory as wp-config.php.