Title: Team Staatic's Replies | WordPress.org --- # Team Staatic [ ](https://wordpress.org/support/users/staatic/) * [Profile](https://wordpress.org/support/users/staatic/) * [Topics Started](https://wordpress.org/support/users/staatic/topics/) * [Replies Created](https://wordpress.org/support/users/staatic/replies/) * [Reviews Written](https://wordpress.org/support/users/staatic/reviews/) * [Topics Replied To](https://wordpress.org/support/users/staatic/replied-to/) * [Engagements](https://wordpress.org/support/users/staatic/engagements/) * [Favorites](https://wordpress.org/support/users/staatic/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 112 total) 1 [2](https://wordpress.org/support/users/staatic/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/staatic/replies/page/3/?output_format=md)… [6](https://wordpress.org/support/users/staatic/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/staatic/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/staatic/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/staatic/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Errors](https://wordpress.org/support/topic/errors-337/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [7 months, 3 weeks ago](https://wordpress.org/support/topic/errors-337/#post-18651855) * Hi, thanks for reaching out and for using Staatic to optimize the speed and security of your WordPress site. The error you’re seeing typically indicates a timeout issue with the LocalWP server. By default, LocalWP can impose strict concurrency limits depending on the web server configuration. * To resolve this issue, you can try switching your web server from Nginx to Apache or vice versa. This simple change might help alleviate the timeout errors. Additionally, I recommend checking out our [troubleshooting guide](https://staatic.com/documentation/setup/troubleshooting/) for more solutions you can try. * If you continue to experience issues, please don’t hesitate to reach out for further assistance. It would be helpful if you could provide a site health information report. You can obtain this by going to WP-Admin > Tools > Site Health > Info( tab) and clicking “Copy site info to clipboard”. You can share this information here or email it to [contact@staatic.com](https://wordpress.org/support/users/staatic/replies/contact@staatic.com?output_format=md). * We’re here to help, so feel free to reach out with any additional questions or concerns! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Ignoring Attributes / Incorrect rewriting of certain URLS](https://wordpress.org/support/topic/ignoring-attributes-incorrect-rewriting-of-certain-urls/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [8 months ago](https://wordpress.org/support/topic/ignoring-attributes-incorrect-rewriting-of-certain-urls/#post-18639033) * Hi [@donamyk](https://wordpress.org/support/users/donamyk/) , * Great news! All the issues you reported have been addressed in **Staatic 1.12.0** which was just released. * **Issue #1 & #3 (malformed URLs with `https:/` prefixes):** This was indeed a bug with `FallbackUrlExtractor` when `staatic_extended_url_context` was enabled. URLs appearing after incomplete protocol prefixes were incorrectly matched, causing the malformed output you observed. We’ve implemented a two-pass extraction algorithm that properly handles these cases. You can now safely use `staatic_extended_url_context`. * **Regarding preserving absolute URLs for canonical/Open Graph tags:** You identified an important limitation in the documentation. The `staatic_should_crawl_url` filter controls crawling, not transformation; returning `false` prevents crawling entirely, which isn’t what you want. * For your specific requirements (canonical, Open Graph, Yoast Schema with absolute URLs pointing to your static site), you have two approaches: * **Option 1: use an absolute Destination URL** Set your Destination URL in Staatic’s Build settings to your static site’s full URL (e.g., `https://example.com`). This will automatically keep all URLs absolute while pointing to the correct static domain. * **Option 2: custom Transformer for selective absolute URLs** If you need relative URLs for most content but absolute for specific tags, you’ll need a custom Transformer during the publication process. This would rewrite specific URLs to be absolute with your static domain. See our [transformer hooks documentation](https://staatic.com/documentation/developer-guide/action-and-filter-hooks/#updating-transformers)– while the docs are limited at the moment, reviewing the source code along with the `staatic_transformers` filter should give you a starting point. * **New in 1.12.0:** We’ve added the `staatic_should_transform_url` filter which provides independent control over URL transformation. While this won’t solve the absolute URL requirement directly (as it would keep original WordPress URLs), it could be useful for preventing transformation in other scenarios: * ```wp-block-code // Example: Keep WordPress admin-ajax.php URLs unchanged add_filter('staatic_should_transform_url', function ($transform, $url, $foundOnUrl, $context) { // Don't transform admin-ajax endpoints (for forms/dynamic features) if (str_contains($url->getPath(), '/wp-admin/admin-ajax.php')) { return false; // Keep original WordPress URL } return $transform; }, 10, 4); ``` * We’ll be updating the documentation and the Advanced Publication article shortly to clarify these distinctions. * Also, thanks for your excellent debugging work! Your logs showing the partial protocol in the “before” context were exactly what we needed to identify the root cause. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] HTML5-PHP parser fails if `extendedUrlContext` is set](https://wordpress.org/support/topic/html5-php-parser-fails-if-extendedurlcontext-is-set/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [8 months, 1 week ago](https://wordpress.org/support/topic/html5-php-parser-fails-if-extendedurlcontext-is-set/#post-18629401) * Hi [@donamyk](https://wordpress.org/support/users/donamyk/) , * Thanks for reporting this HTML5 parser issue. * We’ve found and fixed the problem – the HTML5 parser’s DOMElement doesn’t support string conversion which the extended URL context was attempting. The fix adds proper element serialization across all parser implementations. * The fix is in the latest development version: 1. Go to the [Staatic WordPress plugin page](https://wordpress.org/plugins/staatic/) 2. Click “Advanced View” → “Advanced Options” → “Previous versions” 3. Download the latest development version * Thanks for the detailed error report. Let us know if you need anything else! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Ignoring Attributes / Incorrect rewriting of certain URLS](https://wordpress.org/support/topic/ignoring-attributes-incorrect-rewriting-of-certain-urls/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [8 months, 1 week ago](https://wordpress.org/support/topic/ignoring-attributes-incorrect-rewriting-of-certain-urls/#post-18629386) * Hi [@donamyk](https://wordpress.org/support/users/donamyk/) , * Thanks for the detailed bug report and test cases. * **Good news on issue #2 (SVG paths):** We’ve identified and fixed the SVG data URL issue where `url(%23a)` references were being incorrectly extracted and transformed. The fix is in the latest development version: 1. Go to the [Staatic WordPress plugin page](https://wordpress.org/plugins/staatic/) 2. Click “Advanced View” on the right 3. Under “Advanced Options” → “Previous versions”, download the latest development version * **For issues #1 and #3:** We haven’t been able to reproduce these yet. The `https:/` pattern and `https:/#website` URLs suggest URL transformation issues specific to your configuration. * To help us reproduce and fix these, please provide: 1. **Site Health Report:** WP-Admin → Tools → Site Health → Info → “Copy site info to clipboard” (or email to [contact@staatic.com](https://wordpress.org/support/users/staatic/replies/contact@staatic.com?output_format=md)) 2. **Staatic Settings:** * - Destination URL (Settings → Build tab) - Any Advanced tab customizations - Custom filters/transformations you’re using - Which specific PHP-DOM-Parser option you selected * The inconsistent results between generations is particularly interesting – might be related to processing order or caching. * **Regarding exclusion by data attribute/comment:** This feature doesn’t exist currently, though it would be useful for future versions. * We’re committed to resolving all three issues. Once we can reproduce them with your configuration details, we’ll provide fixes promptly. * Thanks for using Staatic! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Doesn’t Work With Speculative Loading](https://wordpress.org/support/topic/doesnt-work-with-speculative-loading/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year ago](https://wordpress.org/support/topic/doesnt-work-with-speculative-loading/#post-18440376) * Hi Muslim Syamsul Arifin, * Since we haven’t heard back from you, we’re going to close this thread for now. If you still need assistance, please feel free to reopen the topic or reach out to us directly. We’ll be happy to help you resolve any issues. * Best, Staatic Support Team * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Doesn’t Work With Speculative Loading](https://wordpress.org/support/topic/doesnt-work-with-speculative-loading/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 1 month ago](https://wordpress.org/support/topic/doesnt-work-with-speculative-loading/#post-18378727) * Hi Muslim Syamsul Arifin, * First of all, thank you for trying Staatic to enhance the performance and security of your WordPress site. I’m sorry to hear about the issue you’re encountering with the Speculative Loading plugin. * The error message you mentioned indicates that the web server hosting your WordPress site may have limited support for handling concurrent HTTP requests, which leads to the Staatic crawler requests timing out. To address this, you might try increasing the timeout settings. You can find more detailed guidance in our troubleshooting article here [https://staatic.com/documentation/setup/troubleshooting/](https://staatic.com/documentation/setup/troubleshooting/)( see Time-Outs section, specifically regarding Nginx/Apache/Litespeed). * If adjusting the timeouts doesn’t resolve the issue, it would be helpful to gather more information about your WordPress environment. Could you please provide details such as the web server software and operating system you’re using? You can easily obtain this information by navigating to WP-Admin > Tools > Site Health > Info( tab) and clicking “Copy site info to clipboard”. * Looking forward to helping you resolve this. * Best, Staatic Support Team * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] cURL error 6: Could not resolve host](https://wordpress.org/support/topic/curl-error-6-could-not-resolve-host-9/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 3 months ago](https://wordpress.org/support/topic/curl-error-6-could-not-resolve-host-9/#post-18295634) * The issue was confirmed to be due to resource limitations, which were addressed by adjusting concurrency settings and timeouts. Since there have been no further updates, we assume the solution worked. * If similar issues arise, please don’t hesitate to reach out. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] cURL error 6: Could not resolve host](https://wordpress.org/support/topic/curl-error-6-could-not-resolve-host-9/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 3 months ago](https://wordpress.org/support/topic/curl-error-6-could-not-resolve-host-9/#post-18262865) * hi [@rafczy](https://wordpress.org/support/users/rafczy/) , thanks for the update. The error message indicates an issue with resolving the host, so it doesn’t seem related to the `ulimit`. To help us investigate further, could you share your Site Health info? * Alternatively, please check under the Site Health status to ensure that both “ Your site can perform loopback requests” and “Staatic can perform loopback requests” are listed under Passed tests. These loopback requests are crucial for Staatic to function correctly. * Looking forward to your feedback and helping you resolve this issue! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] cURL error 6: Could not resolve host](https://wordpress.org/support/topic/curl-error-6-could-not-resolve-host-9/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 3 months ago](https://wordpress.org/support/topic/curl-error-6-could-not-resolve-host-9/#post-18257935) * Hi [@rafczy](https://wordpress.org/support/users/rafczy/), * Thanks for reaching out, and sorry to hear you’re having trouble. It sounds like your WordPress site is having difficulty resolving its own host, which Staatic relies on to generate the static version by crawling the site. * Here are a few things you can try: 1. **Check Site Health**: head over to WP-Admin > Tools > Site Health. Look for any issues or errors that might be causing the problem. Fixing these is probably enough to resolve this issue. 2. **DNS and hosts file**: make sure your DNS settings are correct. You might need to add a DNS entry for `my.host.com`, or an entry in your `/etc/hosts` file to ensure it resolves correctly. 3. **Check security settings**: sometimes, firewalls or security plugins can block internal requests. Try temporarily disabling them to see if that’s the issue. * If none of these steps work, it would be helpful to check the Site Health info. You can get this by going to WP-Admin > Tools > Site Health > Info (tab) and clicking “Copy site info to clipboard”. You can send this info to us at [contact@staatic.com](https://wordpress.org/support/users/staatic/replies/contact@staatic.com?output_format=md), and we’ll take a closer look. * Please let us know if this helps or if you have any other questions. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Add WP-CLI Support for Configuring Destination URL](https://wordpress.org/support/topic/add-wp-cli-support-for-configuring-destination-url/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 4 months ago](https://wordpress.org/support/topic/add-wp-cli-support-for-configuring-destination-url/#post-18218938) * Hi [@andrelauret23](https://wordpress.org/support/users/andrelauret23/) , thanks for your enthusiasm and for suggesting improvements to the Staatic plugin! We really appreciate your input. It turns out that configuring the Destination URL via WP-CLI is already possible using the built-in `wp option update` command. * Here’s how you can do it: * `wp option update staatic_destination_url 'https://example.com/'` * This command will update the URL directly in your WordPress database. You can find other settings related to Staatic in the `wp_options` table, usually prefixed with “staatic_”. * As for contributing, we currently don’t have a public GitHub repository. This is mainly due to the complex build process we have in place, which involves scoping vendor dependencies and downgrading PHP 8 code to PHP 7.4 to ensure compatibility across a wide range of environments. We’re actively exploring solutions to manage these challenges, so we can eventually open up the repository for public contributions. * In the meantime, if you have any cool features or improvements, you might consider creating a separate plugin to enhance Staatic’s functionality. * Thanks again for your interest and ideas. We’re excited to see what you come up with! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Add WP-CLI Support for Configuring Destination URL](https://wordpress.org/support/topic/add-wp-cli-support-for-configuring-destination-url/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 5 months ago](https://wordpress.org/support/topic/add-wp-cli-support-for-configuring-destination-url/#post-18200267) * [@andrelauret23](https://wordpress.org/support/users/andrelauret23/) , thank you for your feedback and for outlining this suggestion clearly. Adding WP-CLI support for configuring the Destination URL is indeed a valuable idea, and we’ll definitely consider it for future updates. * If you have any additional suggestions or feedback, feel free to share them. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Statically generated WordPress include index.html in each URL](https://wordpress.org/support/topic/statically-generated-wordpress-include-index-html-in-each-url-2/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 5 months ago](https://wordpress.org/support/topic/statically-generated-wordpress-include-index-html-in-each-url-2/#post-18166434) * Since we haven’t heard back from you, we’ll go ahead and mark this as resolved. If the issue persists, please feel free to open a new topic. Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] WP-CLI –merge Command Not Found](https://wordpress.org/support/topic/wp-cli-merge-command-not-found/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 5 months ago](https://wordpress.org/support/topic/wp-cli-merge-command-not-found/#post-18166429) * Hi [@anthonyeden](https://wordpress.org/support/users/anthonyeden/) , thanks for reaching out. It seems there is some confusion regarding the `--merge` parameter. This feature, along with the `--partial` flag, is exclusive to the Staatic Premium version and is not available in the community edition. The ability to merge a subset of specified or automatically tracked changes is a key feature of the Premium version, alongside other advanced functionalities like integrated search and form handling. * We apologize for any confusion caused by the documentation and will update it to better clarify the differences between the versions. If you have any further questions or need assistance, please feel free to reach out. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Statically generated WordPress include index.html in each URL](https://wordpress.org/support/topic/statically-generated-wordpress-include-index-html-in-each-url-2/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 5 months ago](https://wordpress.org/support/topic/statically-generated-wordpress-include-index-html-in-each-url-2/#post-18145479) * Hi [@kavish895](https://wordpress.org/support/users/kavish895/), just checking in to see if there are any updates on the directory URL issue. If you could share your site URL or any updates on your end, that would be helpful.  Thanks! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Staatic - Static Site Generator] Feature request: Delete publications via CLI](https://wordpress.org/support/topic/feature-request-delete-publications-via-cli/) * Plugin Author [Team Staatic](https://wordpress.org/support/users/staatic/) * (@staatic) * [1 year, 6 months ago](https://wordpress.org/support/topic/feature-request-delete-publications-via-cli/#post-18131059) * Hello @error418, thank you for reaching out with your feature request. Adding a command to delete publications via CLI is indeed a valuable suggestion and we will definitely consider it for a future update. * In the meantime, please note that our system already includes an automatic cleanup routine that deletes publications older than 7 days. We understand that flexibility in this feature could be beneficial as well, so adding a filter hook to adjust the cleanup period is also on our radar. * We appreciate your input and encourage you to keep an eye on our [changelog](https://staatic.com/documentation/setup/changelog/) for any updates regarding these features. Viewing 15 replies - 1 through 15 (of 112 total) 1 [2](https://wordpress.org/support/users/staatic/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/staatic/replies/page/3/?output_format=md)… [6](https://wordpress.org/support/users/staatic/replies/page/6/?output_format=md) [7](https://wordpress.org/support/users/staatic/replies/page/7/?output_format=md) [8](https://wordpress.org/support/users/staatic/replies/page/8/?output_format=md) [→](https://wordpress.org/support/users/staatic/replies/page/2/?output_format=md)