WebSite X5Help Center

 
David S.
David S.
User

I cannot upload my website with Evolution 14  en

Author: David S.
Visited 2431, Followers 1, Shared 0  

Once I upgraded to Evolution 14, I find I am unable to upload my website files now. I get an error saying "Error in folder creation, pleae try later" 

If I go back to using Evolution 13, It all works! What is wrong with E14 to prevent me from uploading?

Posted on the
7 ANSWERS - 1 USEFUL - 1 CORRECT
Barry Maloney
Barry Maloney
User

I had the same problem

Answer from 

Massimiliano wrote:

In the optional export parameters, remember to put / before the export folder address example (/nomecartella.**)

this worked perfectly

Read more
Posted on the from Barry Maloney
David S.
David S.
User
Author

That unfortunately did not work for me. IN adding the "/" I get a new popup indicating "Unable to connect to Server. Incorrect destination folder"

Read more
Posted on the from David S.
Esahc ..
Esahc ..
Moderator

David, have you confirmed recently that there is no issue with your host (use V13, filezilla, etc)?

If so, please also confirm that the ftp setting in WX5 V14 are identical to V13 with the exception that the destination field must have either  "/" or "/destination-folder" (please double check the passord is also correct).

If this still does not work, you could temporarily disable any anti-virus of firewall.

Read more
Posted on the from Esahc ..
David S.
David S.
User
Author

As far as I am aware, no issue with the host. I use A2Hosting, which is recommended by Website X5. 

Read more
Posted on the from David S.
Esahc ..
Esahc ..
Moderator

David, can you still upload using V13 or if you have updated your site in V14, can you export to disk and upload via Filezilla (free)?

Read more
Posted on the from Esahc ..
Incomedia
Claudio D.
Incomedia

Hello David,

Install the new update and then test please the export again to see if it works.

Many thanks!

Read more
Posted on the from Claudio D.
David S.
David S.
User
Author

Claudio-I've been away but just tried the new update, and BAM! That solved the issue! Thank you!

Read more
Posted on the from David S.