Team Staatic

Hello Edson,

Thank you for reaching out and for providing a detailed explanation of the issue you’re encountering with your blog’s permalinks. We understand your concern regarding the URL structure and its potential impact on SEO.

Staatic is designed to adapt to the permalink structure you’ve configured within your WordPress settings. If your permalinks are set to include “.html” at the end, like “/%postname%.html”, Staatic should normally generate links that exactly match this structure, resulting in URLs like “/some/page.html”. The presence of “/some/page.html/index.html” on the filesystem is due to how Staatic organizes content for web delivery. This technical detail is primarily for serving the files correctly and should not affect how your URLs appear to visitors or search engines.

However, the issue you’re experiencing, where a trailing slash is added to your URLs, making them appear as “/year/month/blog-post.html/”, is something we can certainly look into. This behavior isn’t expected based on the permalink structure you’ve described.

To help us diagnose and address this issue more effectively, could you please provide us with your site’s Health screen information? This can be found by going to Tools > Site Health > Info (tab) in your WordPress dashboard. There, you’ll find a button to copy the information to your clipboard. Once you have that information, please send it to us at contact@staatic.com.

Additionally, we appreciate you sharing the C# program you created to address this issue.

Thanks in advance for providing the requested information.

@angelsee, we apologize for the difficulties you’ve encountered with the update. It appears the adjustments we made to URL and path detection, intended to enhance compatibility with environments such as Bedrock and WPMU, especially on the Windows platform, may be contributing factors. We’re actively working to replicate the issue you’ve described and will provide an update promptly. We sincerely regret any inconvenience this has caused.

Thank you for your feedback and suggestions. We are glad to hear that the new filter hooks have been working well for you.

Your suggestion for a GUI textarea for custom code is noted. It’s an interesting idea that could simplify the user experience. We’re also considering your other suggestions, like options for URL redirections and gzip compression.

If you have any other ideas or feedback, please feel free to share them with us.

Hello Ben,

Thank you for reaching out. The current version of Staatic makes it a bit tricky to add custom code to the .htaccess file. However, we’ve introduced new features to help with this. We’ve added two filter hooks: staatic_filesystem_apache_config and staatic_filesystem_nginx_config. These allow you to modify the .htaccess and nginx_rules.conf files before saving them.

To access these new features, you need to update to the latest development version of Staatic. Here’s how to do it:

1. Go to the WordPress Plugin Directory.
2. Find Staatic, click on Advanced View.
3. Scroll down to Advanced Options.
4. Choose Development Version and click Download.
5. Install this new version.

For guidance on using these hooks, check out this example: staatic_filesystem_apache_config.php. You can add this code to your theme’s functions.php file, or as a new file in wp-content/mu-plugins (like staatic_filesystem_apache_config.php).

If you have any more questions or need help, feel free to ask.

@barrypersonalctonet, is everything up and running for you now? If you’re still having trouble, could you let us know where things stand? We’re ready to assist!

Koa ora Raza, thanks for the well wishes! All is good here and we hope the same for you.

Thank you for bringing up your concerns regarding the limitations of our current ‘Publish Changes’ feature. We’re aware of this issue and are actively working on enhancements to address it. Our development team has scheduled these improvements for inclusion in the upcoming plugin update.

In the meantime, utilizing the ‘Publish All’ option serves as the most reliable workaround. We understand this may not be ideal and appreciate your patience as we work to enhance the feature.

As for the second scenario you mentioned, we’re going to look into whether it can also be addressed in the upcoming improvements.

We’ll keep you informed of our progress and will notify you as soon as the updated functionality becomes available.

@gorahul, were you able to get things working? If not, can you please give us an update. We’re here to help!

Hi, thanks so much for using Staatic and glad to hear that you are happy with our plugin.

Having scheduled posts published to your static site automatically requires the Publish on Event automation, which is part of Staatic Premium. This also integrates with the Quick Publications feature, which will only update the actually published post, instead of regenerating the complete static site.

Hopefully this answers your question. If you have any other questions, please feel free to get back to us any time.