Duplicator: issue with installer.php and DB

  • Murdoch

    (@murdoch)


    8 years, 1 month ago

    As a test and prior to using Duplicator to upload a local site to one online I wanted to test it by cloning this local site (running under Desktop Server/XAMPP) to another local site location. The working site is site00.dev and the second location is test00.dev. This second site has a minimal WP installation though I’ve also tried it with nothing whatever in the relevant directory J:\webdev\test00.dev and the results are the same. Site00 has been created using the Divi theme.

    I’m going round in circles!

    Creating the installer.php and the srchive.zip files (approaching 60MB in total) seems to work correctly. I then copy these files to J:\webdev\test00.dev and browse to test00.dev/installer.php and this correctly starts the installer. The Deploy step shows a pass for the requirements.

    I created a new MySQL DB named test00_0, added a user test00 with all global privileges, on one occasion with and on another without a password, and connected it to the DB. PHPMYAdmin showed the DB as present, the user as present and the two connected.

    If I select Create New Database OR Connect and Remove … and test the connection I get Success on Server Connected, fail on DB found. If I then run deployment with the first option checked it gives me eventually a server code 200 and a claim that it’s unable to create the DB and that the user may not have that ability, this despit having all privileges. I then delete the newly created wpconfig.php and rerun using the second option Connect and remove … this almost immediately gives me a server code 200 and says that the DB does not exist – this despite its clearly showing up in PHPMyAdmin.

    I guess I might be missing something very obvious but I have no idea what it could be and so any advice or help would be much appreciated.

    Thanks, M

Viewing 1 replies (of 1 total)
  • Thread Starter Murdoch

    (@murdoch)

    8 years, 1 month ago

    Update. I seem now to have got this sorted and the comment following is made in case it’s helpful for others in a similar situation.

    The problems appeared to be with the entries for the DB and for the user. Using PHPMyAdmin I confirmed that the DB name autofilled in the relevant Duplicator table which appeared when running Installer to paste the site in its new location was indeed one of the tables present. It seemed logical, therefore, that that name be used.

    Checking further I confirmed that my own user name appeared in the relevant tables and because I knew the password to that it appeared logical here to use that user name and password. I confirmed, also, that my user had adequate privileges and was indeed linked to the DB.

    None of that mettered, it seemed, in practice. If I tried to clear the DB I was told I didn’t have relevant privileges. If I tried to delete the DB and create a new one I was told I didn’t have Create privileges.

    I believe, although not certain of this, the whole process having got some what confused, that at some point I was told the pasword was wrong.

    Guessing that the DB referred to was a DB in the new site intended to hold the relevant data it seemed irrelevant what the name was and I therefore exerpimented with simple new names. Yet again, the issue of privileges arose despite PHPMyAdmin confirming both that I had the relevant privileges and that I was linked as a user to the DB I had just created through PHPMyAdmin for the new site.

    This was becoming intensely frustrating but in the end the solution was simple – ignore the DB name and enter “root” as the user.

    It seems that my surmise the the DB name was irrelevant was correct. As for “root” I chose that as it was shown as having all privileges, connected all over the place and having no password; others that met similar criteria did have passwords and as I would have no way of finding these out that rendered them unsuitable.

    So there it is – simple solution. And now that that approach has been winkled out the plugin seems to perform flawlessly being rapid and complete in its action and so thoroughly to be recommended, albeit with the small caveat that a comment in the general documentation along the lines of what I’ve written immediately above would have been very helpful.

    M

Viewing 1 replies (of 1 total)
  • The topic ‘Duplicator: issue with installer.php and DB’ is closed to new replies.