400 Error when importing site from site library - fresh wp install - namecheap

Hi there,

is your server using cloudflare or any other caching plugin? If so can you try disabling them and try to import them again.

I am using namecheaps easy wp. So I have no server side caching that I know of or can disable.

I found a similar issue here:
https://generatepress.com/forums/topic/400-error-upon-importing-a-site-from-the-site-library/page/2/#post-722397

Unfortunately McLean didn't report back afterwards.

Can you check with your host as well?

Your file would be https://gpsites.co/files/arctic/options.json

What location is that file downloaded to on the server?

It should be in your wp-content/uploads folder in the most recent folder.

Hum, interesting yeah I do not see it in that folder. I also cannot edit the permissions of that folder via Transmit 5 through the access that Namecheap has given me.

I did add

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

To my wp-config.php but it had no effect and I see no log files being generated. :(

These issues are making me wish I had just launched my own server on Digital Ocean or something instead of using Namecheap Easy WP.

I guess I will try to reach out to Namecheap again. Not sure how responsive their support is going to be though.

There's no debug.log file in the wp-content folder?

I would definitely reach out to them to ask if there's anything they see on their end. It's possible that your server is refusing to connect with our gpsites.co server.

I have the same problem '400 error'. I'm using namecheap hosting.
I already contacted them? showed them these pages to simplify the explanation:
https://docs.generatepress.com/article/error-codes-importing/
https://generatepress.com/forums/topic/400-error-on-import-from-library/page/4/
https://generatepress.com/forums/topic/400-error-when-importing-site-from-site-library-fresh-wp-install-namecheap/

They disabled their caching. It didn't work out.
The template from the site library didn't upload.
What other options I have?

This is a known issue at the moment. Servers will built-in caching that can't be turned off (easily) can make it so the caching system the library uses doesn't work and fails.

We're working to resolve it in 1.13.0.

This is the advice they told me yesterday:
we can only suggest contacting the theme support again or try to upload .CSV theme file manually, or a file in another format provided by the theme developers.

We can also help to import the file as well. You may upload it to the website directory with the help of SFTP connection, using any of FTP clients: https://www.namecheap.com/support/knowledgebase/article.aspx/9961/2239/easywp-how-to-access-your-wordpress-website-folders-and-files-via-sftp/

I have no idea what they talk about. I'm a beginner in this stuff.

They went to my WP dashboard to do what I did. I explained to them the instructions for importing the template.

This is what they told me today:
I have checked this with our cloud team and there is not any server end issue or conflict when importing the content.
We do not see any kind of error logs on our end.
The error 400 bad request is the code related error triggered by an incorrect request sent by the remote server (plugin/code)

It probably will take months for you guys to resolve this issue. Correct?
The only option I have is to wait or you can give me that CSV theme file for Aspire theme?

The XML file for Aspire can be found here: https://gpsites.co/files/aspire/content.xml

It can be imported in "Tools > Import".

The only downside to this method is you miss the "Site Options" import, which handles things like menu setup, setting the front page etc..

We're hoping to have 1.13.0 in public testing within 2 weeks.

Let me know if you need more info with the content import, sorry for the inconvenience!

Hi,
I have the same problem with Easywp. Any news on when we can expect a fix for this please?

many thanks for your help.

Martin

Hi there,

We've completely rebuilt the Site Library in GPP 2.0.0, which will be entering public alpha testing early next week. This issue should be fixed in this version.

That’s great news. Many thanks for your work, Tom.