Title: patrickposner's Replies | WordPress.org --- # patrickposner [ ](https://wordpress.org/support/users/patrickposner/) * [Profile](https://wordpress.org/support/users/patrickposner/) * [Topics Started](https://wordpress.org/support/users/patrickposner/topics/) * [Replies Created](https://wordpress.org/support/users/patrickposner/replies/) * [Reviews Written](https://wordpress.org/support/users/patrickposner/reviews/) * [Topics Replied To](https://wordpress.org/support/users/patrickposner/replied-to/) * [Engagements](https://wordpress.org/support/users/patrickposner/engagements/) * [Favorites](https://wordpress.org/support/users/patrickposner/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 1,213 total) 1 [2](https://wordpress.org/support/users/patrickposner/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/patrickposner/replies/page/3/?output_format=md)… [79](https://wordpress.org/support/users/patrickposner/replies/page/79/?output_format=md) [80](https://wordpress.org/support/users/patrickposner/replies/page/80/?output_format=md) [81](https://wordpress.org/support/users/patrickposner/replies/page/81/?output_format=md) [→](https://wordpress.org/support/users/patrickposner/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] 3.8.6 on WP 7.0.2 no Zip generated](https://wordpress.org/support/topic/3-8-6-on-wp-7-0-2-no-zip-generated/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [2 weeks, 4 days ago](https://wordpress.org/support/topic/3-8-6-on-wp-7-0-2-no-zip-generated/#post-18977469) * Hey [@tplomari](https://wordpress.org/support/users/tplomari/), thanks for reporting this! I tracked down a path-to-URL issue affecting some Local and custom uploads- directory configurations. The ZIP may be written successfully, but Simply Static cannot derive its download URL, resulting in the empty “ZIP archive created:” entry. * I’ve prepared a fix for the next update. As a temporary workaround, set the Temporary Files Directory under Simply Static → Settings → Debug to a writable directory inside `wp-content/uploads`, then run the export again. If that doesn’t help, please share the Simply Static debug log so I can confirm the configured paths! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Zip File is not a link](https://wordpress.org/support/topic/zip-file-is-not-a-link/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [2 weeks, 4 days ago](https://wordpress.org/support/topic/zip-file-is-not-a-link/#post-18977454) * Hey [@facsimilebrian](https://wordpress.org/support/users/facsimilebrian/), * we just fixed that now, sorry! * Please update to 3.8.6 and re-run the export – the link should now appear correctly. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Question about hashed image files generation during incremental exports](https://wordpress.org/support/topic/question-about-hashed-image-files-generation-during-incremental-exports/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [3 weeks, 2 days ago](https://wordpress.org/support/topic/question-about-hashed-image-files-generation-during-incremental-exports/#post-18972842) * Thank you! The exact URL explains the behavior. * This is an upgrade edge case between the full export created with Simply Static 3.1.8 and the filename sanitization used by 3.8.4. The existing media record is considered unchanged during the incremental export, even though its expected exported filename has changed. The HTML is therefore updated to the new filename, but the media file is not copied again. * The generated filename is deterministic: `933db1a4d7081b14748e63e95353a2a4` is the MD5 hash of `top-menu-04@2x`. This also suggests that WP Multibyte Patch, or an equivalent `sanitize_file_name`filter, is active. * No additional setting is required. Running one full export after the upgrade is the correct workaround and establishes a compatible baseline for future incremental exports. * We’ll address the migration case so an incremental export can detect when an existing asset’s stored output path no longer matches its current sanitized path and re-export it automatically. * Thanks again for the detailed reproduction steps. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] All releases since 3.80 have not worked properly](https://wordpress.org/support/topic/all-releases-since-3-80-have-not-worked-properly/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [3 weeks, 2 days ago](https://wordpress.org/support/topic/all-releases-since-3-80-have-not-worked-properly/#post-18972834) * Hey [@liamdj](https://wordpress.org/support/users/liamdj/), * thanks for the confirmation! * I think I should rethink our defaults to avoid the extra step here – 3.8.0 was primarily a security release. We want to lead by example here, especially with all the AI-related security issues popping up every day now within WordPress, but we might have taken that one step too far. * I’ll review your case specifically and think of a good middle ground here – maybe we can disable the SSL check as soon as we detect a localhost environment * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] All releases since 3.80 have not worked properly](https://wordpress.org/support/topic/all-releases-since-3-80-have-not-worked-properly/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [3 weeks, 3 days ago](https://wordpress.org/support/topic/all-releases-since-3-80-have-not-worked-properly/#post-18972145) * Hi Liam, * Thanks for the detailed report – especially for narrowing the change down to 3.8.0. * There is a strong Herd-specific candidate here: starting with 3.8.0, Simply Static began verifying SSL certificates for its internal crawler and background loopback requests. Version 3.7.9 did not. On an HTTPS `.test` site, PHP/cURL can reject Herd’s local certificate even though the browser trusts it. * When that loopback fails, the export may fall back to running inside the REST request that started it. A timeout or PHP warning can then produce the “response is not a valid JSON response” message. WordPress provides a dedicated [`https_local_ssl_verify`](https://developer.wordpress.org/reference/hooks/https_local_ssl_verify/) filter for these local requests. * Could you confirm whether the Herd site uses HTTPS? * If it does, please temporarily add the following on the local site only: * ```wp-block-code add_filter( 'ss_remote_get_sslverify', '__return_false' ); add_filter( 'https_local_ssl_verify', '__return_false' ); add_filter( 'wp_archive_creation_job_loopback_available', '__return_true' ); ``` * Then, using Simply Static 3.8.4: 1. Go to **Simply Static → Settings → Utilities**. 2. Click **Reset Background Queue**. 3. Run another export. * Please remove the snippet after testing and don’t use it on a production site. * If that resolves it, we’ll have confirmed the affected code path. If it doesn’t, could you provide: - WordPress, PHP and Herd versions - Whether the site uses HTTP or HTTPS - The status and response shown for `/wp-json/simplystatic/v1/start-export`  under the browser’s **Developer Tools → Network** tab - The relevant Simply Static debug-log entries, with local paths redacted * The response from that REST request should reveal the underlying PHP error or HTML response behind the JSON message. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Won’t export pages – gives 403 error](https://wordpress.org/support/topic/wont-export-pages-gives-403-error/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [3 weeks, 3 days ago](https://wordpress.org/support/topic/wont-export-pages-gives-403-error/#post-18972135) * Hi [@rwhaun](https://wordpress.org/support/users/rwhaun/), * Thanks for the detailed troubleshooting. This doesn’t appear to be related to` robots.txt`, `.htaccess`, or the export destination. * Simply Static retrieves each post/page by making an HTTP request from WordPress back to the site itself. Many assets can be handled separately from the filesystem, which explains why they export while the rendered posts and pages receive 403 responses. ZIP versus local deployment only changes what happens after those requests. * I checked the site and its response headers show that it is running through StackCDN. Westhost confirms that its CDN is [enabled by default on all hosting packages](https://www.westhost.com/knowledgebase/article/how-to-use-the-content-delivery-network-cdn/), even without Cloudflare or a WordPress caching plugin. * As a first test, please: 1. Enable **Development Mode** under **StackCP → CDN → Edge Caching**, then retry the export. 2. Check **StackCP → CDN → Block Visitors** for any IP or country restrictions. 3. Check **Tools → Site Health** for a failed loopback request. WordPress explains these requests [here](https://developer.wordpress.org/advanced-administration/wordpress/loopback/). * If it still fails, please ask Westhost to inspect their security logs at the exact time of an export. You can send them this: _WordPress on jeremykronbach. com receives HTTP 403 responses when making loopback GET requests to its own public domain. The requests use the `Simply-Static` user agent and include the` simply\_static\_page` query parameter. Please check the ModSecurity/CDN/visitor- blocking logs, provide the triggered rule ID, and allow requests from the hosting server’s outbound IP to its own domain._ * Westhost also notes that a 403 can result from a ModSecurity rule and that their support team must investigate the triggered rule in that case: [Westhost 403 documentation](https://www.westhost.com/knowledgebase/article/how-to-resolve-the-http-error-403-forbidden/). * If Westhost confirms that nothing is being blocked, please share one failed URL from the Simply Static activity log and the Site Health loopback result, with any sensitive paths redacted. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Breaking changes version 3.8.4](https://wordpress.org/support/topic/breaking-changes-version-3-8-4/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [3 weeks, 3 days ago](https://wordpress.org/support/topic/breaking-changes-version-3-8-4/#post-18972132) * [@muslimpribadi](https://wordpress.org/support/users/muslimpribadi/), please either provide a meaningful error report or don’t open a request – no one asked for opinions. Thanks! [@rwhaun](https://wordpress.org/support/users/rwhaun/) Stop hijacking other posts; you’ll get a reply on your own post once we’re done investigating. Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Question about hashed image files generation during incremental exports](https://wordpress.org/support/topic/question-about-hashed-image-files-generation-during-incremental-exports/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [3 weeks, 3 days ago](https://wordpress.org/support/topic/question-about-hashed-image-files-generation-during-incremental-exports/#post-18972124) * Hi [@pbsalt](https://wordpress.org/support/users/pbsalt/), * Thanks for the detailed report. No additional setting is required. * An incremental export is a delta and must be applied on top of an existing full export. It does not recreate every unchanged file. Therefore, if the destination directory was emptied before the incremental export, missing image files would be expected. * That said, I found an edge case in the current versions: an existing media file newly referenced by a changed page – including through a custom field – may remain classified as unchanged, while its URL is still rewritten in the generated HTML. Filenames requiring sanitization make this especially visible because the exported path differs from the original path. * Could you please confirm: 1. Was the incremental export applied over the existing full-export directory, without clearing it first? 2. Is the image also missing from that final destination? 3. Could you paste one exact original URL and generated URL inside a code block? The current example only contains a placeholder. * If the file is missing after applying the update over the full export, that is not expected and is not a configuration issue. As a temporary workaround, please use a full export when adding or newly referencing affected media files. * Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Breaking CSS url()](https://wordpress.org/support/topic/breaking-css-url/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [4 weeks ago](https://wordpress.org/support/topic/breaking-css-url/#post-18968603) * [@jamesjosephfinn](https://wordpress.org/support/users/jamesjosephfinn/) Thanks for confirming! * I guess all those hours that we invest in automated test coverage are finally paying off – much easier these days to get this fixed and continuously track that they don’t happen again! * I’ll wrap this into an official release alongside a few other improvements – so it should be safe for you to update on Monday! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Subdirectory install: /wordpress removed from asset paths after update](https://wordpress.org/support/topic/subdirectory-install-wordpress-removed-from-asset-paths-after-update/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [4 weeks, 1 day ago](https://wordpress.org/support/topic/subdirectory-install-wordpress-removed-from-asset-paths-after-update/#post-18968183) * [@pbsalt](https://wordpress.org/support/users/pbsalt/) patch is on the way: [https://github.com/Simply-Static/simply-static/commit/608de1283b6fb394d0c3edb1f8489535a76de7cb](https://github.com/Simply-Static/simply-static/commit/608de1283b6fb394d0c3edb1f8489535a76de7cb) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Breaking CSS url()](https://wordpress.org/support/topic/breaking-css-url/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [4 weeks, 1 day ago](https://wordpress.org/support/topic/breaking-css-url/#post-18968181) * [@jamesjosephfinn](https://wordpress.org/support/users/jamesjosephfinn/) that was helpful! * I got another patch in (yes, even more regex fine-tuning.. 😅): [https://github.com/Simply-Static/simply-static/commit/e01c3ab99991ac3b7eaa7b0fcaedb2870c079789](https://github.com/Simply-Static/simply-static/commit/e01c3ab99991ac3b7eaa7b0fcaedb2870c079789) Updated file: [https://github.com/Simply-Static/simply-static/blob/master/src/class-ss-url-extractor.php](https://github.com/Simply-Static/simply-static/blob/master/src/class-ss-url-extractor.php) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Blank plugin settings etc pages with WP 6.2.9](https://wordpress.org/support/topic/blank-plugin-settings-etc-pages-with-wp-6-2-9/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [4 weeks, 1 day ago](https://wordpress.org/support/topic/blank-plugin-settings-etc-pages-with-wp-6-2-9/#post-18967999) * [@lovingboth](https://wordpress.org/support/users/lovingboth/) sorry for that! I’m getting this fixed and shipped with the next update – it should definitely work with WP 6.2! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Breaking CSS url()](https://wordpress.org/support/topic/breaking-css-url/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [1 month ago](https://wordpress.org/support/topic/breaking-css-url/#post-18966105) * [@jamesjosephfinn](https://wordpress.org/support/users/jamesjosephfinn/), great! I wrote a small fix here: [https://github.com/Simply-Static/simply-static/commit/6266e30f826a0c0659655c5e1c1deb1a260a481e#diff-ee9b14e40d7172b0e4f2bc6f614cfcadec282c85544d24742350bdcbc9d53cce](https://github.com/Simply-Static/simply-static/commit/6266e30f826a0c0659655c5e1c1deb1a260a481e#diff-ee9b14e40d7172b0e4f2bc6f614cfcadec282c85544d24742350bdcbc9d53cce) You might want to download and test this file from here: [https://github.com/Simply-Static/simply-static/blob/master/src/class-ss-url-extractor.php](https://github.com/Simply-Static/simply-static/blob/master/src/class-ss-url-extractor.php)( it already includes the patch), but given the 24-hour delay for every release right now on w.org – we might want to confirm that before I push that into an official update! 😅 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] Breaking CSS url()](https://wordpress.org/support/topic/breaking-css-url/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [1 month ago](https://wordpress.org/support/topic/breaking-css-url/#post-18966041) * Hey [@jamesjosephfinn](https://wordpress.org/support/users/jamesjosephfinn/), * happy to look into that! * Could you paste the full CSS in something like a Gist on [GitHub](https://gist.github.com) or send the it directly to [support@simplystatic.com](https://wordpress.org/support/users/patrickposner/replies/support@simplystatic.com?output_format=md)? Without it, it’s probably hard to track down 😅 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Simply Static - The Static Site Generator] wp-includes URLs become invalid with Absolute URLs on subdirectory installs](https://wordpress.org/support/topic/wp-includes-urls-become-invalid-with-absolute-urls-on-subdirectory-installs/) * Plugin Author [patrickposner](https://wordpress.org/support/users/patrickposner/) * (@patrickposner) * [1 month, 2 weeks ago](https://wordpress.org/support/topic/wp-includes-urls-become-invalid-with-absolute-urls-on-subdirectory-installs/#post-18953930) * [@thewpuser1](https://wordpress.org/support/users/thewpuser1/) amazing, thank you! Viewing 15 replies - 1 through 15 (of 1,213 total) 1 [2](https://wordpress.org/support/users/patrickposner/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/patrickposner/replies/page/3/?output_format=md)… [79](https://wordpress.org/support/users/patrickposner/replies/page/79/?output_format=md) [80](https://wordpress.org/support/users/patrickposner/replies/page/80/?output_format=md) [81](https://wordpress.org/support/users/patrickposner/replies/page/81/?output_format=md) [→](https://wordpress.org/support/users/patrickposner/replies/page/2/?output_format=md)