- This topic has 24 replies, 3 voices, and was last updated 7 years, 5 months ago by
.
-
Posts
-
Just basically what the title says, upon wanting to import a site from the library I encounter the 400 error.
The colors and demo content was imported but not the widgets..
Lead Developer
Is the 400 error happening during the backup phase, or after? How did you get to the demo content?
At the beginning the 400 error upon importing the content, then the 400 error appeared. I hit the button to start over, now is just stuck there.
Can you try the “Further Debugging” tips here?: https://docs.generatepress.com/article/error-codes-importing/#further-debugging
That should give us a more detailed error to work with.
I added the two lines you mentioned. I re-created the problem, but I don’t see any debug.log file..
There’s no
debug.logfile in thewp-contentfolder? Give it a refresh maybe.Note: I am not using a shared hosting, I am using a VPS with EasyEngine installed, IDK if I makes a difference or not..
Just did, nothing there
Take a look: http://prntscr.com/lcejzt
Can you clear your browser cache and give it another go?
I just imported that site on one of my test installs and it all went through nicely.
I use opera as the main browser, just installed chrome, but it still persists.
So it got to importing the site options that time.
Do you have a different server to test on? I wonder if there’s something preventing it from going through on your current server.
Super tough to debug this kind of stuff without specific errors. Anything in your
error_logfile?It seems that there is something blocking it. I tried locally it worked, on a shared server and it also worked..
Nothing on the error_log,
Thanks anyways
The process is downloading a
.jsonfile and then parsing it and extracting the necessary data. Perhaps there’s something on your server preventing the download/parsing of JSON files?I’ve deactivated pretty much everything that I think it was causing it, but the error still persists. I am going to reinstall everything and I’ll try again tomorrow or the day after.
Let me know how it goes – sorry for the hassle!
- You must be logged in to reply to this topic.
