Good day. There is a site on Drupal 7, vinokuram.ru. For convenience of working with it, I copied it to another folder on the same hosting, created a copy of the database, the folder on the hosting is called testvinokuram.ru. I didn’t start a separate domain name for it, it is accessed from the browser using the test domain testvinokuram.ru.to show.

The problem is that when accessing a copy of the site on the test domain - it is impossible to log into the admin area, immediately says "login or password is incorrect." Links to password recovery send in the form: http://testvinokuram.ru/user/reset/1/1471151912/g5a3pbM-1vY5IjxxODyL9491d8lCl16h <blah blah blah>

Those. as you can see, the name of the site when you restore the password to the mail does not come at all, through which the test site is available in the browser. Naturally, such a link does not work - and when you try to add to this link ". Show. Website" the link becomes inoperative.

Changing $ base_url in settings.php makes all the pictures inaccessible and moves the layout. Where to dig so that I could get into the admin site of the test site?

Ps. Thanks in advance.

    1 answer 1

    If you reduce your task to “transfer a drupal to another domain” (and the task “make a copy of a drupal on another domain” is practically no different from this), then everything is done simply: transfer files, copy the database, clean the drupal cache. And it will work.

    Why does not work for you. Many hosters offer a quick way to create a site - they have added another folder, uploaded files - and the site is seen at some technical address like http: //name.apams.domain.provider.ru But you did something wrong and you need to understand this - you need to dig exactly on the side of the service provider: how exactly he does it and what chemite. See for yourself, ru-co is not free freelancing and nobody will do your work for you.

    In general, the desire to move away from editing the code on the production site is commendable. You decided to put together a developer environment right at the hoster, on the same server - this is not very good. Lift the environment on your work computer and use two environments: development and production. What you do at the hoster can be considered rather closer to staging. This model (dev -> stage -> prod) is closer to the ideal, but the overhead is higher.

    • No matter how hard Drupal tried to run on different Apaches (just like Apache under Windows, or XAMPP), it’s terrible brakes. Lenovo S10-3 netbook. Interestingly, wordpress-sites fly to LAN. - NDanilov2015
    • one
      @ NDanilov2015 The parable says that "one must search where he has lost, and not where it is lighter." It is more correct to deal with the problem, why the local drupal slows down (for others it does not slow down), and not to create new problems for oneself, walking along the wrong path. - AK ♦
    • I sinned on a weak laptop, although the CPU usage of Apache is not very high. Okay, I'll try to figure out what's wrong in localhost - NDanilov2015