Failed to move uploaded file

I have installed WP All Import on 3 different sites with different stacks but when I try to upload a few kb csv I get this message: Failed to move uploaded file.

I am a beginner which means, do not assume that I can implement any suggestion without proper instructions.

Many thanks

Hey @Bellerofonte

I found a similar topic in the WordPress forum for WP All Import. Their support has some suggestions and links here:

Thanks for sharing.

1 Like

Did you run into the same issue @Moon1?

I anticipated that I am a beginner. I had read your suggestion the screenshot below should demonstrate that I have no authorization problems. Right?

If it can be useful I can post the WordPress health report. I understand that it contains all the information on the state of the system.

Have you specifically checked the /wp-content/uploads/wpallimport folder and its subfolders as mentioned by the WP All Import team in that link? Here is an example in my Local app. If you click on Go to site folder, you can follow the path at the bottom of my screenshot to navigate to where that file is.

Additionally, did you check your disk space as recommended as well?

Thanks for the feedback.

I have located the wp-all-import folder but for some reason unknown to me I cannot change the read/write attribute. In order not to risk misinterpreting what I see and am doing I am sending you a screen recording. The attempt was made with Locale closed.

As for disk space. If you are referring to the system disk where Local is installed, no, I have no space problems.

2024-11-20_16-14-32

@Bellerofonte you might check your system settings and make sure you are running Local as administrator:

Additionally, I think I noticed an issue in your recording which is a Windows bug in which user names cannot have spaces or special characters. The easiest way to get around this is to create a new user without those items.

After starting Local in administrator mode, the problem was solved.

I use a user with administrator privileges and when I use Local I do it by booting in “standard” mode.
So, considering that I was unable to change the attributes of the wp-all-import folder, I have to conclude that the problem that was preventing the file from loading was Local’s startup mode. Question: does Local’s specification require or recommend starting with administrative privileges?

Regarding the username syntax, are there no important reasons why I should not continue this way? This question is motivated by my inexperience as a windows administrator and my lack of confidence in this OS. I have enough headaches procured by the complexity of web project development work, going to wake sleeping dogs…

Many thanks for your help.

1 Like

Glad to hear that fixed things up @Bellerofonte!

Running an application like Local as an administrator gives it elevated privileges that can sometimes resolve issues where Local might be blocked by a security or permissions setting. Local needs these to be able to update things like the hosts files when changes are made so that’s why it’s necessary to have those admin rights.

If you’re not running into any other issues with Local then you can ignore the username syntax maybe I was mistaken on that playing a role here. I’ll close this thread, but if you have any other questions or concerns don’t hesitate to reach back out. We are always happy to help!