Magento – After changing the base url in the backend is the backend / The shop is no longer available

It happens like once, that in the wake of fundamental changes in the Magento Base URL back in the system > Configuration > Web changes. No sooner have we saved, is the backend, or even the entire store suddenly no longer available. This is a horror and a trail of one is not really as comfortable. The favored method we, to solve this mishap quickly, is not completely harmless, but leads to the goal: It is said to be very careful!

It is in fact in the database of the shop and thus into the heart. EIn errors here can have serious bugs quickly, Therefore, changes to rethink exactly and still the best backup / To make backups. In any case it should be noted the exact spot or noticed any change BEFORE, so it does not you should have been so well-- this can be undone. CTRL A + Z is not here.

We work in this example with the widespread phpMyAdmin. It is usually on the hosting directly accessible. After the start there is a little older-looking surface. If the hosting several databases are, must first be selected affected.

If this is selected, is best on top “Search” be clicked. Now it would be good, if you remember, which has entered the URL to the base URL, so that the shop was not reachable then. This is type in the search, Select all tables and then to “OK” click.

Now, the individual meetings will be displayed. Our attitude (in this example) lay the table and had core_config_data there a value of 1195 (whether the other is so, can not be said). Furthermore, this is also web / unsecure / base_url . Now enter the URL again, before the change in the Base URL box, and then got down OK.
To make the job a little easier, can also use the following SQL command to be entered:

select * from core_config_data where path like 'web/%/base_url';

Well, at least delete the browser cache. If it still will not work, go with the FTP program in the root directory of the shop and there in the directory “var / cache”. The contents of the folder “cache” delete (only the content, not the folder “cache” themselves!).

Then try again. Now, the store should be accessible again.

So each step is important to think through and be sure to remember from what to what has been changed, so you can look for the amendment and the amended return can adjust.

Used in 1.4.1.1