WordPress quick app does not download at all
I am trying to initiate a WordPress website but when I do it with the quick app section, it doesn't download the zip file (and don't give any error messages or logs).
It does creates the database, but don't proceed with the download.
Anyone knows how to fix it? Thanks!
i have the same problem, wordpress download dont work!!
with those in
binof the latest curl:
@leokhoa still not working.
First I just overwrited the curl.exe and lubcurl.dll files. It suggested me to register a Proxy under [preferences] in laragon.ini.
Still no success.
Then I unziped the rest of the files from the curl download.
Hasn't worked either.
Did the same as @victormoretti, still not working too
@ivanhalen : Do you have
If yes, can you rename the
curl.exe.deleteand try again?
gitfolder, no luck
I also downloaded v4.0.4, and still having the same problem in downloading Node
@ivanhalen same here. It just keeps the download at 0%.
Also I tried around 10 different proxies but it doesn't change the behaviour.
I have the same problem
i have the same problem in downloading Node. Can you add cancel download button in the quick add screen? thanks in advance
If yes, please chat with me.
@leokhoa, yes, sure! I live in Italy so we have a time zone difference, but tell me how can I get in touch with you nd I'll be glad to help!
here is also giving download error!
same issue here!!
It's still the same way here! WordPress does not work!!
awaiting a new version.
I'll stop at LARAGON when I fix it, I'll use it again.
Same problem here...
Using Windows 10 Home with all firewall permissions granted to Laragon.
Not using proxy.
I downloaded this software, for WordPress quick app sake , if it doesn't work then I have to remove it
See I did download the latest version 4.05 and put debug=1 in laragon.ini. Now I can see it downloads the wordpress just fine to /tmp/downloads. But then it stops and does not unzip the file to /tmp/extract/id-of-pid. So can someone maybe please help and debug also? We are close to getting this to work again on windows 10 again. Looks like it needs some administrator stuff.