What issue or error are you experiencing?
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc
I upgraded to version 10 and all went well. I can start, open and access my site. However, I cannot upload media with error “missing temporary folder”. When I open elementor editor, I can edit site normally but when I try and save I get “server error”. This on both Edge and Chrome, normal and private windows.
Was all working before the upgrade (when I was on v9) and this is happening on all my installations, so I am suspecting something broke during the upgrade. I exported the site and imported it into Wordpress Studio and it works fine (as it did in LocalWP before v10). Can someone help as I much prefer LocalWP to Studio.
Attached: screenshots of errors, screenshot of inspect whilst trying to save from Elementor, logs
Thanks guys.
System Details
Local Logs
Attach your Local Logs here (Help
local-logs.zip (82.9 KB)
Doc - Retrieving Local’s Log)
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
Hi @MarkiSparki! Thank you for raising this.
If you create a new, blank site with Elementor, are you able to save and upload normally? That might help determine if the issue only impacted your current installs or is something more widespread.
There are some steps here that can help generally with this error:
If a new, blank install works you could also try reimporting your site as well to get around the problem. Something else I saw a user mention was running into this on Apache in the past, but switching to NGINX resolved it. If you’re running Apache that might be worth a test as well. https://stackoverflow.com/questions/74288001/wordpress-media-upload-error-missing-a-temporary-folder-on-a-local-server
Thanks for getting back to me so quickly. I appreciate that.
I have created a temp directory and amended the wp-config file. I am already using NGINX. Sadly that hasn’t worked.
I also created a clean site and again it doesn’t work. Everything was fine a couple of days ago before I updated from v9 to v10 and, as I say, the site works fine in Studio.
One thing, I cannot clear the read only on the temp file in windows, it keeps changing back to this:
Nothing seems to make it stick. But it is the same for every other folder in wp-content. Even clearing this box for the whole wp-content folder, it just comes back again.
I checked the other post you mentioned, but I can’t find any php.ini file.
I feel the error must be in the v10 somehow as the exact same exported site works just fine in Studio (even if 10x slower…haha!), plus the error is affecting all of my other local sites too.
Thanks again for any advice.
Oh, and just for completeness I installed apache and tried it with the same error.
My versions are: MySQL 8.4.0 and PHP 8.3.29 on the test site and MySQL 8.0.35 and PHP 8.3.29 on all my other local sites, by the way.
Windows security can be pretty pesky at times, and I have seen this before: after an update, Windows will “reflag” something. That Read Only check makes me think something like that happened here.
Can you check if you are running Local as an administrator @MarkiSparki ? You might also want to check whether there are any security blockers and whether Local has access to update the Hosts file.
If that still doesn’t work you could try downgrading to v9
Our Local Devs didn’t run into any issues when testing v10 on Windows, but I’ll spin up my Windows VM and see if I can replicate anything as well.
OK, thanks @Nick-B that nailed it. Running as administrator got everything working again.
So I don’t know why doing an in place upgrade from v9 to v10 broke access privileges and I would be interested to know what permissions occurred when giving Local admin privileges.
Either way, I would be interested if you did a v9 installation, got a site working, closed the VM down completely, restarted and upgraded to v10 to see if you can replicate.
I will mark this as solved and due thanks to you mate. Cheers
Glad to hear you got things working again, @MarkiSparki, and sorry for the disruption to your workflow!
I went ahead and tested downgrading to v9.2.8 and upgrading to v10, running through image uploads and post creation on both occasions without any issues. I also checked in with our Local devs, who confirmed that no changes in this version should trigger security flags.
Based on everything we’ve looked at, this appears to be a Windows-side permissions change rather than a product bug. I know I’ve seen this come up occasionally in the past for a Local user, but a quick Google search for “Windows changed permissions after update” turns up quite a few users across different apps running into the same issue. So this actually appears to be more of a known Windows quirk that isn’t specific to our app, where, after certain updates, security and permissions settings can shift unexpectedly.
For additional context: roughly 70% of our users are on Windows, so if this were a widespread bug on our end, we’d expect to hear about it much more widely. That said, we’ll absolutely keep an eye out for any similar reports!
If you have any other questions or concerns, don’t hesitate to reach back out!
