Team Staatic

@angelseee , we’re very sorry for the inconvenience. A bug has slipped through our testing process and we have made changes to this process to prevent this case from happening again in the future. An update, Staatic v1.4.5, has just been released which should fix this issue.

@okdv, thank you for taking the time to review our WordPress plugin. We appreciate your feedback and concerns regarding the pricing model and clarity of features. As a dedicated plugin developer, we strive to create products that add value and enhance the WordPress ecosystem.

Regarding the premium plugins’ monthly pricing, we understand your perspective regarding the open-source ecosystem. While we have chosen a subscription model for our premium plugin, it allows us to continuously support and improve the product by providing regular updates, bug fixes, and dedicated customer support. We believe this approach ensures the longevity and sustainability of the plugin, enabling us to deliver the best experience to our users. Note that we also provide a completely free community plugin, which provides all of the features needed to convert any WordPress site into a fast and secure static site.

We apologize for any confusion caused by our feature descriptions. Where possible, we will work on making them clearer to save users’ time and ensure informed decisions.

Your feedback is valuable to us, and we are committed to improving our plugin to better serve the WordPress community. If you have any further suggestions or questions, please feel free to reach out to us.

After further testing we have been able to reproduce the issue locally. We noticed that during the saving of a post, the post changes are spread across several updates. Since Staatic is immediately triggered after the first update, subsequent updates may not be included in the publication.

We have prepared a workaround for the next plugin version, which will add a small delay to the trigger, causing all updates to be picked up in the publication. This update is planned to be released before the end of this month.

Plugin “Staatic HTML Minifier” does not put these tags at the end of the html code of a static page:
</body></html>

This is by design, since these tags are optional in HTML5. See also: https://html.spec.whatwg.org/multipage/syntax.html#syntax-tag-omission.

We have created an example HTML minification plugin which uses voku HtmlMin under the hood, in order to minify any HTML resources processed by Staatic during the publication process. Feel free to modify the plugin as needed.

Unfortunately Staatic is unable to retain the minified HTML code completely, since it alters the HTML code during the rewriting of URLs.

However, you may have better results while using “Simple Html Dom Parser”, which can be configured in Staatic > Settings > Advanced. From our experience, this HTML DOM Parser leaves unchanged HTML mostly as-is.

To ensure fully minified HTML code, the minification process should be applied after all pages have been processed by Staatic.

Note that some CDN services have built in HTML (and CSS/JS) minification available, like Cloudflare and Netlify, which could make this very easy if available to you.

Hi @angelseee , thanks so much for opening this topic. This could be very helpful to other users on Staatic 1.4.3 facing the same issue.

As you may have noticed, we have experimented with several methods to enhance the reliability of the frontend (WP-Admin) publication process, with varying degrees of success. The reason it is so difficult to find a universal value that fits all, is due to the many different hosting environments (and limitations) the plugin needs to support.

In the upcoming version 1.4.4, we have implemented a new approach that will determine the correct Publication Task Timeout value automatically based on an automated internal test, executed immediately after plugin activation. This will hopefully sort out these kinds of issues once and for all.

Hi @levyimage,

Thank you for taking the time to leave a review of our Staatic plugin. We appreciate all feedback, whether positive or negative, as it helps us to improve our product.

We apologize that our offering may not have been fully clear to you. Our community version is completely free of charge and allows you to generate a static version of your WordPress site at any time, without any limitations.

However, our Staatic Premium offering provides additional features and services, such as API-based (hosted) services to handle automatic form and search integration, as well as professional maintenance and further development of the Staatic plugin. We believe that these added features are valuable and justify the monthly subscription fee.

We understand that you may not agree with our pricing model, but we would like to clarify that the premium offering has nothing to do with the community plugin reviews. We are saddened to see a negative review in this context.

Please feel free to reach out to us if you have any further questions or concerns.

Best regards,

Team Staatic

Thanks for providing the additional information. We will be performing some further tests and will get back to you as soon as we know more. Will keep you updated.

Hi @angelseee , first of all thanks for trying Staatic to improve the speed and performance of your WordPress site.

In order for Staatic to be able to extract and replace URLs in the HTML source, it relies on a HTML DOM parser. The default HTML DOM parser used is “PHP DOM Wrapper (scotteh/php-dom-wrapper)”, which (from our experience) performs really well when processing a large number of pages. However, as a side effect it may alter the HTML source, and in this case causing the Cyrillic characters to be replaced by numerical character references (NCRs). This is perfectly valid HTML and may even improve compatibility with certain clients.

However, if you prefer to keep the HTML as original as possible, we recommend using “Simple Html Dom Parser (voku/simple_html_dom)”. This can be changed from Staatic > Settings > Advanced, and then Crawler > HTML DOM Parser. See also this article from our documentation: https://staatic.com/documentation/administrator-guide/configuration/advanced-settings/#crawler-html-dom-parser.

Does this answer your question?

Hi @jkburges, that’s quite an interesting case. Staatic hooks into the post_updated and save_post actions to track changes. When editing a post, the post_updated action hook should be triggered after the post has been updated, and only then Staatic will start the publication process.

Do you by any chance have a caching plugin enabled? That could cause Staatic to see cached results while crawling the updated post.

Also, just to see if it changes anything, would delaying the hook propagation make any difference? This could be achieved by adding the following code into your theme’s functions.php file, or in a separate mu-plugin file (e.g. wp-content/mu-plugins/staatic_delay.php):

<?php

add_action( 'staatic_change_event', function () {
    sleep( 5 );
}, 5 );

This will delay the saving of a post by 5 seconds, so it is not really a solution. However, it can help answer some questions.

If this does not make any difference, it could be the case that Elementor updates the post in multiple stages. In that case we could consider delaying the publication trigger itself.

Looking forward to your feedback.

The final 1.4.3 release is scheduled for today. You can expect the update to become available within the next couple of hours.

Can you download the Development Version again and try once more? We noticed a small error that got introduced by our build system that should now be fixed. We’re sorry for the inconvenience.

No configuration is needed to enable this integration. Once Staatic detects Yoast Premium Redirects, it activates automatically.

Staatic 1.4.3-beta1, which includes integration with Yoast Premium Redirects, has just been released and can now be downloaded from the plugin directory’s Advanced View. Under Advanced Options, select Development Version and click the Download button.

Hi @jkburges, I just wanted to let you know that we are planning to improve support for Yoast Premium by detecting the (plain) redirects automatically. A beta release with this functionality is expected to be available before the end of next week. I will update this topic as soon as it is available.