well I have a little experience and read all the articles here about moving a site from one server to another
I uploaded the files and linked them to empty database and it works fine and ask me to install wordpress
but when I import the old database to the new empty one, the site doesn't open and keeps loading, all pages with wp-admin the same doesn't open
I think that mysql version has something to do with that, because the new server has an old version 5.1, and the old server where the database was exported from uses 5.5 version
any solution plz?
MySQL is one probability and other probability is issue in your wp_options table. Change site_url and home to match your configuration on the new server.
You may also need to change wp-config.php file to match configuration of your new server. If everything is alright, you should be able to logon to WP-Admin. Once you have logged in successfully, change Permalinks to some other structure and then revert back. This will create all URLs again in MySQL Database.
It turned out to be the openbasedir function, I allowed it and that solved the issue.
Related
I'm transfering a wordpress site from a previous hosting package to our inhouse servers. I've copied the whole directory and taken a .sql backup of the database. Before moving it onto our servers, I want to make sure it works by running the backup locally.
So i've imported the database and changed the siteurl and home fields in the wp_options table to match my localhost. When i go to it, I get a database error, Which is what I wanter so then I entered the correct details in wp_config
But now when I go there, I get err_connection_refused message. I've tried everything I can think of, the url is correct in the database wp_options table so its not that. Any ideas please on what to try next?
Why not leave everything as is, and edit your hosts file to point to your new machine.
Then you can test using the real URL, minimizing the risk that there are URLs in the database that you didn't edit while testing.
We have created a duplicate of our website on a new server as part of a migration. We have a wordpress blog that is part of our website.
The docroot of the wordpress site is set as an alias in our main site. The result is that to access the site home page, the following url is used: https://www.rephunter.net/blog/.
The new environment is not available to the public at this time, and is only accessible within our VPN. When the above link to the blog is followed, instead of the expected home page of our blog, we get the page at https://www.rephunter.net/blog/wp-admin/install.php, which wants to install a new site.
The configuration in the new environment is supposedly an exact copy of our production site from some time back. The permissions on the main files is the same.
What is it that is causing the attempted blog access to be redirected to the installation script?
EDIT:
The responses so far have not really absorbed the intent of the previous information. We are not migrating in the normal sense. Rather we are testing in a new virtual environment that will eventually lead to a more normal migration.
We have an exact duplicate of our original wordpress and database environment that is running in a virtual environment with an updated protocol stack that is only accessible if you are on the VPN for that environment. As far as we can tell, there is no difference in the configuration.
For example, the parameters in wp-config.php are exactly the same as in the original installation. When php runs, it sees the same environment, with host names and everything identical. It would not work otherwise.
Yet if there really were no difference, it would just run. But since WP is trying to install a new database, there is something different that we are missing.
To further illustrate this: supposed you took an image backup of the wordpress installation and the database, and put it in a different VM, and set up the DNS and everything as it needs to be--the new environment looks no different than the old one. All databases, wp-config settings, etc, are the same. So our main website and database functions very similarly.
As I mentioned above, the difference in the protocol stack should be considered. The old system is on PHP 5.6.27--the new one is on 7.3.4. So that could be causing some difference, which maybe somebody might recognize. Wordpress is 5.2.2 and should be compatible with both PHP levels.
We believe there is some relatively simple parameter setting that we are missing. For example, as in the first answer that $table_prefix is set wrongly. But that is not it in this case.
WordPress redirects you to that installation screen because the database it's connecting to is working (meaning, the username and password are correct), but the data it's expecting to be there isn't. Therefore, it assumes it's a new / empty database and prompts you to install WordPress.
I've seen this happen in two scenarios:
The database really is empty, and thus WP needs to install the standard tables and info
The table prefix in your wp-config.php file is incorrect for an existing database
Look at your wp-config.php file in the root directory of WordPress, and look for a line similar to this:
$table_prefix = 'wp_';
Then, open up the database (phpMyAdmin or some other interface to browse what the database structure actually is) and confirm that the table prefixes (the first few characters of the table names) actually match what's set above.
Hopefully this gives you something to go on! Let us know what you find
Migrating Wordpress websites can be quite tricky. I've worked as a WP developer for a number of years and always struggled with manually migrating websites.
There are a number of factors to consider:
WP stores a lot of installation specific information within the database. So you can't do a database dump and upload the export into a new database.
Changing the website url within the wp_options table in the databased there are still other references to the original url scattered throughout the db.
You could try a find and replace all using an editor that supports this sort of functionality (vscode, sublime, atom) but things always end up breaking and your doing tons of "find & replace" actions.
I have always relied on a 3rd party tool Backup Buddy as it simplifies the entire backup and migration process and offers the peace of mind of having easily deployable backups for your website.
Backup Buddy allows you to export your website as a zip and then you can move the zip to any server you want and the plugin provides an installer script (php) to guide you through the migration of your wp site to any host and database of your choosing.
Note: I am not in any way affiliated with iThemes or Backup buddy, and I do not stand to benefit in anyway if you decide to use the plugin. This is only advice on a tool that I have found helpful, reliable, have had success with, and currently actively use on a number of websites that I maintain.
WordPress display installation page because you have not update your wp-config.php file after migrating server so please follow below steps in future when you migrate your website.
Please follow this steps when you migrate your WordPress website from one server to another server.
Back up your website files/database
Export wordpress database.
Create database on your new host server.
Edit the wp-config.php File and edit this details.
Add new database name
Add new database username
Add new database user Password
Add new host as per your hosting provider or (localhost is default)
Import your database to new server.
upload the WordPress files to your new host
defining new domain URL & Search/Replace old domain URL
A client asked me to migrate a website to wordpress. The theme is made, everything is working fine locally and now im thinking the best way to make the migration. I'm thinking on makeing the instalation on a subfolder for testing and then moving it to the root of the server. Is there anything i need to do other than copy the files from wordpress folder to the root? Anyone know a good tutorial or a better way to make the migration?
Take a look at this tutorial from Sitepoint I'm always referring to it when I want to move WP websites and it works.
Example: yourlocalwebsite.com
Example: yourlivewebsite.com
Step 1 Upload you all local files or WordPress setup to the live server.
Step 2 Export your localhost database and edit it with notpad++ editor.
Step 3 find your local website name into notpad++ something yourlocalwebsite.com then go to replace tab and all replace tab your yourlocalwebsite.com with yourlivewebsite.com. now save it.
Step 4 check database name username and password into wp-config.php it should be correct which one you using live server database.
Step 5 go to you live database and take backup it then removes it and then imports your local database now.
Step 6 for making sure go to wp_options table and check the URL it should be now yourlivewebsite.com if not then change it
Step 7 go to wp-admin and set the permalinks to the post name
and check it is working fine or not.
local site comes properly but when we deploy same folder on server ... it shows broken pages
In order to migrate a Wordpress website you should
1. Copy your www folder using FTP Client (FileZilla, Fire FTP or WinSCP).
2. Export you database (important!) and then import the database in your new Web Hosting (Like OVH or other..).
Let me know if you have any others question !
Yes, you have to do lot more things than you specified.
Follow below steps :-
Download "Wp Migrate DB" plugin from https://wordpress.org/plugins/wp-migrate-db/ to your existing site
Open db migrator. When you will try migrating, it will prompt you to give folder path and website url for new site(old site is already filled by plugin so don't change them)
After adding folder path and URL start db migration
Copy files and folders from your local to live
Import migrated db to new database
Copy new credentials for db connect to wp-config file
Re save permalinks, as it may won't work after migration
After this you are all set to go...
Let me know if you need further assistance.
followed this tutorial and worked like a charm. Wordpress installation moved to the root of the server and everythig works fine. Themes and plugins. Just made the test right now.
http://www.inmotionhosting.com/support/edu/wordpress/329-move-folders
Thanks for the answers.
I have a client's wordpress site that is built using Wordpress and Headway. I need to move it to a new domain on a new shared server ( same host provider with the same hardware configuration ).
I've moved many wordpress setups like this before, including Wordpress / Headway combos. I've also, during debug, used Headway's documentation and videos to double check that I'm doing everything correctly.
I moved the database over and replaced all occurrences of the old domain with the new domain, and updated all filepaths. Then I copied the public_html folder to the new server. The site should be working at this point.
Instead I get the Headway error message No Content to Display on an otherwise empty html page. I've traced the problem to the wp-config table where Headway stores serialized data for it's blocks. I can update data throughout the database to the new domain everywhere except in these Headway entries in the wp-config table. As soon as I update those, the site starts to fall apart all over the place, and if I update them all, the site loads the Headway error message No Content to Display. The underlying Wordpress system seems to still be working as I can load the /wp-admin console and all my content exists and looks correct.
If I trace the problem deeper, it appears that the Wordpress function get_options() is failing in the Headway file data-layout-options.php. I have been unable to debug any further.
The site works perfectly on the original domain, and, in theory, I'm doing a direct copy of all data and then simply replacing the old domain with the new domain.
Can anyone help with a similar problem? It feels like I'm chasing a bug in the code when really it's some sort of simple oversight or config setting that has been munged. Please help!!!
I was indeed close to the problem.
The serialized Headway data in the Wordpress wp-config table contains string lengths. Migrating the database oneself, and then grepping and replacing the old domain with the new domain and old web folder file path with the new web folder file path causes unserialization to fail in the Wordpress system ( eg. the get_options() Wordpress function ).
Instead of writing a custom script to deal with the string lengths, I tested a few database migration plugins. WP Migrate DB was the winner and solved the problem.
Migrating the Database
Install the plugin on the original domain ( original Wordpress install ). It will ask you to input the new domain and the new file path of your web directory ( the web directory file path is very important as well ). In my case, for example, the file path of the web directory had changed from /home2/old_username to /home6/new_username.
The plugin will then dump the entire Wordpress Database and replace all occurances of the old domain and old file path with the new domain and file path of the web directory. The .sql dump will then save locally on your computer.
This was not perfect however, and I still needed to do a few of my own grep and replaces. Additionally, I had to be careful about this because a few of the ones that were missed were in the Headway serialized data and I had to do MySQL queries to make sure I updated the string length properly.
These few updates were missed because some of the database entries had http://www.olddomain.com and some had http://olddomain.com. The plugin did not catch it all, but made it manageable to replace by hand.
Finally, I had to import this updated .sql dump into an empty Wordpress database on the new domain.
Moral of the story is that Headway V3 is not simple to migrate to a new domain. You must be very meticulous.
Another option, that I did not try because it costs >$75 was BackupBuddy. It's likely that BackupBuddy will still miss some domain and file path updates, so be careful.
I have found the solution of T. Brian Jones and have just applied it for WordPress 3.8.1 with HEADWAY 3.6.2.
All works fine.
One trick for newbes like me: if you don't know the file path on the server where you are moving your database, before you do database dump install WP Migrate DB on this server, run the plugin (Tools) and get the path from there...
Thank's TBJ
Maciej
I'm trying to replace the WordPress database I have on my live server. Here's the scenario: I have two databases on my server. The old one and the new one. When I edit config.php to change the database name from the old one to the new one, WordPress wants me to re-install. Here's why I'm confused...
The tables in the new database have been updated to the old URL (I'm keeping the same URL).
It's the same database user so the db user and db password don't need to change.
The db user has permissions for the new database.
I thought that I should be able to change the database name and go, but WordPress isn't letting me. Any help would be greatly appreciated. I've been working on this for several hours and I'm at my wit's end. I know there just HAS to be a way that doesn't involve manually adding/editing content in the WordPress admin.
Have you made sure that the wp-config.php:
$table_prefix = '';
Is the same as the prefix in the database (phpMyAdmin) if you use that? Usually that can keep displaying the admin/install.php page.
Wordpress prompts you to reinstall Wordpress because you're missing a whole directory in your Wordpress files (forget which one, sorry). In part, it will create the wp-config file which will store the database info.
I can't see it be bad to follow the install process, it'll ask you for the credentials to your database, which should atleast overwrite the old file and configuration. Don't forget to backup your files before doing this, in case it all goes to hell.
I had the same issue. It turned out that my new MySQL DB had an issue.
I restored the DB with innobackupex and didn't apply the --apply-log parameter on the backup directory to create the correct log files for the InnoDB engine.
Check your MySQL error log file to make sure that everything is normal. The log file's location is /var/log/mysql/[hostname].err.