So, some progress has been made in my case. The site that wouldn’t import uses the iThemes Security Pro plugin to lockdown the site. One of things it locks down is access to the rest api. In it’s default configuration it provides only restricted access to the rest api for the site. This setting is found in the WordPress Tweaks module. I made many changes to try to fix a problem with passwordless login, so it is possible that it was something else I changed but that setting would make sense in this situation. The home option in the wp_options table is the second value created and I would guess the first one that local would be checking. Anyway, for the moment the site pull for this website is currently working.
Hey everyone, thanks for your patience with this – it’s been an extremely hard thing to find a universal solution for due to the fact that there are many different possible reasons for this error message to be displayed.
This specific string:
Error: Unable to get ‘home’ option from WordPress.
is coming from wp-cli when it’s trying to ask WordPress what the “home” URL for the site is, but WordPress responds by saying that there isn’t any home option. As you might imagine, not having the Home option is definitely a problem for a WordPress site! So how do you go about figuring out what went wrong?
In most cases, when you see this error, it points to something wrong with WordPress’s connection to the database. Think of things like:
- The DB wasn’t imported correctly, possibly due to SQL errors.
- The table prefix isn’t correctly set within the
wp-config.phpfile.
Keeping those things in mind, here are some things to look at:
1. Is there data in the WordPress database?
Open Adminer and make sure that there is data within the database, and that it looks like it has the typical WordPress tables (so wp_posts, wp_users, etc)
If there isn’t any data within the database, you might have to manually import it using Adminer or wp-cli and a database dump in the form of a .sql file.
2. Is the correct table prefix being used?
You can open the wp-config.php file located at app/public/wp-config.php for the site and check to see if the $table_prefix variable has the correct value. In most cases when Pulling or importing a site, Local can figure out and correctly set the prefix that it finds in the sql file, but if it doesn’t choose the right prefix, you might need to manually adjust the wp-config.php file to whatever table prefix contains the data for the site.
In my case after I receive the error the website gets deleted so I wasn’t able to see the database. So I closed the app i the middle of the error so I can keep the website, after I start the site, I can browse it without any issue, even though when I click on Adminer it doesn’t work I just get a 404.
I tried installing Mysql Workbench and connecting with the socket but no luck…
I got this error when pulling (with database) from production to an existing Local site.
The workaround that seems to have worked for me was to pull once with “include database” unchecked (I had to also select “all modified files” from the Pull dropdown menu since there were no “new files” changes to pull). Then pull a second time with “include database” checked this time. In my case both completed with no errors.
Local version: 5.5.3+3667
I can confirm that any symlinks in the theme or plugin directory cause the import to fail. The local error log reports:
{“thread”:“main”,“class”:"",“message”:“Error: [path to symlink] is not a valid path\n at %%appPath%%/node_modules/tar-fs/index.js:302:31\n at %%appPath%%/node_modules/tar-fs/index.js:333:5\n at FSReqCallback.oncomplete (fs.js:166:5)”,“level”:“error”,“timestamp”:“2020-06-10T18:28:09.143Z”}
I am having the same problem, trying to create a site from a saved Blueprint.
Can you describe in a little more detail about how the site is being created? Is it from the “Create site” screen in Local, or are you dragging and dropping a zip file onto Local?
Can you describe in a little more detail about how the site is being created? Is it from the “Create site” screen in Local, or are you dragging and dropping a zip file onto Local?
I click on the + icon to Add Local Site and go through the wizard, choosing “create site from blueprint” under the Advanced Options.
Interesting @dominyza – I wonder if the blueprint has some sort of corruption?
Maybe you can try manually importing the zip that Local has for that blueprint. To get to that zip file, do this:
- Click “Help > Reveal Local Router’s Log”
- Navigate “up” until you get to Local’s configuration directory. You should see a
blueprintsdirectory - Within that
blueprintsdirectory there should be azipfile for the blueprint you are wanting to create a site from. Can you try dragging and dropping that onto Local and see if this creates a new site?
Here’s a screenshot to help clarify where to navigate:
Can you try that manual import process? If you do still have issues, can you please provide your Local Log? See this Community Forum post for instructions on how to do so:
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.