Fails spectacularly

Hi JB,

Thanks for your interest in this plugin.

Regarding the custom output folders, there is a fix contributed by a user here, not yet in the latest release:

https://github.com/leonstafford/wordpress-static-html-plugin/pull/32

If you are able to manually modify your plugin files to match, that may help in the meantime.

To debug the other issue, please try running the default WP Theme (Twenty Seventeen, or is it now Twenty Eighteen?). This should export.

If that fails, please contact me with some more specific environmental info (PHP version, hosting company/plan, browser, etc): [email protected] and I’ll see what I can do.

Cheers,

Leon

Hi Leon,

I updated to the latest version of twentyseventeen, switched my site to run that, and I see the same behavior – this is all that’s created:


2018
└── 01
└── wp-static-html-output-1-1516913949-jbchrsty
└── wp-content
└── themes
└── twentyseventeen
└── assets
├── css
├── images
└── js

9 directories, 0 files


I’m testing this plugin out on my local dev environment:

Mac OS Sierra 10.12.6
MAMP Pro 4.2.1
Apache
MySQL 5.6.35
PHP 7.1.8 (I also tried with PHP 5.6.31 and got the same results)
Browser: Chrome 63.0.3239.132

One peculiarity about my local dev environment is that it’s served over HTTPS with a MAMP self-signed cert. This is because the production site I’m mirroring is forced to HTTPS, and I don’t want to fiddle with local changes to the config files stored in git. I might be able to temporarily serve my local site over http just to see if that’s the issue. But this will need to work on a site that’s served over https with a (very slightly wonky) SSL cert.

I manually applied the pull request you referenced above, and that seems to make the plugin honor the custom output directory setting. So thanks for that.

I temporarily made my local dev site serve over http (not https with a self-signed cert), and things appeared to work with the twentyseventeen theme. So the spectacular part of the failure is now resolved.

However:

I switched back to my custom theme, which is a child theme of another custom theme I developed. The plugin generates and populates a tree structure for the parent theme, but it does not seem to take any note of the theme that’s actually activated, i.e. the child theme. No directory structures for the child theme is even created, let alone populated. Is this a known limitation of the plugin?

I can probably work around the child theme issue. At this point we rarely make changes to the child theme’s assets, so I can probably just manually populate the necessary theme files in S3 and things will work ok. But of course it would be nice if the plugin handled child themes automagically.

Hi JB,

I’ve just pushed up some other fixes and put the output folder fix in to version 2.2 also.

I’ve had another inquiry this week about child themes, which to be honest, I’ve not ever used, but should be able to look into it and see what’s going on.

The local SSL issue has been previously reported, it sounds very similar. Again, I’ll need to setup a test environment for it (thanks for providing your environment info).

If these fixes are urgently needed, please consider making a donation towards development, that can help me justify allocating time to the project, else I’ll try to get to test them as soon as possible.

Again, thanks for trying the plugin and for taking the time to provide feedback.

Cheers,

Leon

Hi JB,

There have been a few releases since your original support request. I’ve also changed the default uploads directory to not put the export files in /2018/01, etc. This is set to come out in V2.6, but you can try out a recent development version with a solution here (it also cleans up files after export if you choose, which prevents the clutter from building up:

https://github.com/leonstafford/wordpress-static-html-plugin/blob/master/wp-plugin-cleanup-fixed.zip?raw=true

Please let me know if you’re still having issues.

Cheers,

Leon