Team Staatic

Hi @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 – 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:

// 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.

Hi @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
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)
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!

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/ (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

hi @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!

Hi @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!

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!

Hi @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!