Team Staatic

Hello!

Thank you for your kind words about the plugin. We’re sorry to hear you’re encountering an issue where the build process stalls. When a publication stalls without any errors, it often indicates a HTTP timeout or an uncaught fatal error. Let’s work through some steps to resolve this.

First, we recommend trying to initiate the publication using the Staatic publish WP-CLI command instead of through WP-Admin. The CLI command bypasses the usual web request constraints such as memory and time limits. You can find detailed instructions on how to use the WP-CLI command in our documentation.

If using WP-CLI isn’t feasible, please enable WP_DEBUG and WP_DEBUG_LOG in your WordPress configuration and restart the publication process. When it stalls, check the /wp-content/debug.log file for any error messages. For detailed instructions, have a look here.

Should there be no errors in the log, it would be helpful if you could share the site health information. This can be done by navigating to WP-Admin > Tools > Site Health > Info (tab) and clicking “Copy site info to clipboard”. You can paste this information here or email it to us at contact@staatic.com.

Looking forward to your feedback.

Thank you for clarifying your use case.

To address your requirement of excluding the /index.html part from URLs, we’ve added an experimental option in the development version of the Staatic plugin. You can download this version by going to the plugin’s page advanced view, navigating to Previous Versions under Advanced Options, and choosing the Development Version. Once downloaded, update your plugin to this version.

After updating, go to Staatic > Settings > Build, where you will find the option “Append /index.html to directory URLs”. Uncheck this option and click Save Changes at the bottom of the page. Then, start a new publication to apply these settings.

Please let us know if this resolves your issue or if you need further assistance.

Thank you very much, @giampiero , for the wonderful review! Your support is truly appreciated and motivates us to continue enhancing our plugin.

Hi @webverts.

First of all, thanks for using Staatic! While there’s currently no built-in feature in the interface to change the 404 path, you can achieve this through a custom action hook.

You can find a working example of such a script here: https://gist.github.com/staaticdotcom/c42db4699118b3c83518be431a340013. To use it, simply download the staatic_post_processor_cloudflare.php file and place it in your /wp-content/mu-plugins folder (you might need to create this folder if it doesn’t already exist). Once you’ve done that, on the next publication, the 404 page should be stored as 404.html.

We’re also considering adding direct support for this feature from the interface in future updates, but for now, this should serve as a solid workaround.

Let us know how it goes, and feel free to reach out if you have any questions or run into any issues!

Thank you, @hatisenang , for your review and feedback! We’re glad Staatic is helping with your site conversions.

We do support incremental pushes using the Publish Selection feature, which allows you to update only a subset of your site’s pages. Our premium plugin expands this further with the Publish Changes feature, which automatically publishes new, updated, or deleted posts/pages. If that’s what you’re looking for, the premium version might be worth considering.

Thanks for supporting Staatic!

Hi @slawa19, just checking in to see if you were able to resolve the timeout issue you were experiencing during the deployment of your static site. If you’re still having trouble, please let us know so we can assist you further. Thanks!

Since there hasn’t been any update for a while, we’ll be marking this issue as resolved due to inactivity. If the issue persists, please feel free to reopen the thread.