Open guillaumemeyer opened 5 years ago
Thanks @guillaumemeyer ,
Will look into it. Could you try putting teststatic
in the subdirectory field in the plugin settings?
And please share me some info of your hosting environment. Windows is rather untested. If you can use Local by FlyWheel or something else on your Windows that will use UNIX filepaths, that may solve it for you.
Cheers,
Leon
For now, we're using the default WordPress template from Microsoft Azure, which is a Windows container: OS version: Microsoft Windows NT 10.0.14393.0 64 bit system: True 64 bit process: False Processor count: 1 CLR version: 4.0.30319.42000 System directory: D:\Windows\system32 Current working directory: D:\Windows\system32 IIS command line: ...
Same issue using a "teststatic" subfolder:
OK, thanks. I'll be adding Azure Blob Storage support as a deploy method soon, so may as well start some testing on Azure itself. Uggh, last time I tried signing up, was a nightmare to enable billing. Will try again
Additional info:
OK, thanks. I'll be adding Azure Blob Storage support as a deploy method soon, so may as well start some testing on Azure itself. Uggh, last time I tried signing up, was a nightmare to enable billing. Will try again
For now, I'm trying wp2static deployment to GitHub Pages, but we're using Azure intensively, so count me in as a beta-tester if you're releasing an Azure Blob Storage connector ;-)
@leonstafford Quick inspection at the corrupted generated zip file, it appears that it's the same issue with folder names.
Any ETA @leonstafford ? The "Subdirectory on current server" deployment works perfectly, so I'll buy the solution as soon as this issue is solved... ;-)
When using the GitHub export with this configuration, the static files are expected to be found in the root of the repo: Instead, even if files are correctly generated, they're pushed in an incorrect subfolder:
BTW, this extra sub-folders prevents local git cloning...