Team Staatic

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

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!

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 for any updates regarding these features.

We’re glad to hear that you were able to resolve the issue by adjusting the timeout limits. If you need any further assistance, feel free to reach out.

Thank you for updating us, and happy publishing! ??

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 [email protected].

Looking forward to your feedback.

Thank you for the update. It seems that Fleek.xyz hosting might require the index.html for directory URLs to work properly. To better assist you, could you share the URL to your site? If you prefer to keep this information private, you can email it to [email protected]. Thanks!

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.

Hi @kavish895,

When using the “Offline URL” option in Staatic, it generates relative links for static content, which is useful for viewing the site without a web server, using file:// URLs. In this case, each page’s index.html must be explicitly referenced because there’s no server to interpret URLs and serve the default index file.

Could you clarify how you’re running your static site locally? Are you using a web server like Nginx, or are you opening the files directly in your browser?

If you’re using Nginx, you can set a regular destination URL under Build settings, like / or https://www.mysite.local/, depending on your web server configuration. This approach allows Nginx to handle URL requests and serve default index files without needing to specify index.html.

If you’re opening files directly in your browser, the index.html must be included in the URL. What is your reason for wanting to omit index.html in this setup?

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

Thanks for letting us know it worked! If you have any more questions or need further help, feel free to start a new topic.

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!

Since we haven’t heard back from you, we’ll consider this issue resolved for now. If you’re still experiencing any problems, please feel free to reopen the topic or start a new thread. Thank you!

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!

Thanks for providing the additional information. It appears that the high number of resources is causing a timeout during the Netlify deployment initialization step. By default, an additional path is configured under Staatic > Settings > Build to include everything in your wp-content/uploads directory, which might be including too many files.

You can try disabling this additional path temporarily so that the Staatic crawler only includes the directly referenced assets and see if this helps. If this doesn’t resolve the issue, we recommend using the WP-CLI publish command for large deployments, as it bypasses the resource limits that the web publisher encounters.

For more details on the WP-CLI publish command, please refer to the documentation here.

Please let us know if this helps.