Team Staatic

Thanks for sharing your feedback, @djwchess!

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, we just wanted to let you know that we managed to find the root cause of this issue.

Due to an error in the database schema definition, urls longer than 255 characters were not handled correctly. This has been addressed in the latest plugin release, version 1.6.3. We encourage you to download this version at your earliest convenience.

Should you encounter any more difficulties or if you have any more queries, please feel free to reach out.

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

Hi Barry, thanks so much for trying Staatic to improve the performance and security of your WordPress sites.

According to the error, during the crawler initialization phase (where Staatic builds a list of URLs that should definitely be included in the static version of your site), a URL was encountered which was either too long (longer than 2,083 characters), or contains invalid characters (in most cases non-UTF-8 characters).

In order to resolve the issue, we need to find out which URL is causing this, and which URL provider provided the invalid URL. Could you please enable “Detailed logging” and restart the publication? Detailed logging can be enabled from Staatic > Settings > Advanced > Logging. Once the publication has finished, you can view the logs by going to Staatic > Publications > Details > Logs.

Could you then share the last log entries before the publication fails? You may also send an export of the publication logs (using the Export button at the top of the Logs page) as well as a copy of your site’s Health Info report (by going to Tools > Site Health > Info > Copy site info to clipboard) to [email protected]. This will give us a bit more information to work with.

Looking forward to your feedback.

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.

Hello @gorahul ,

We haven’t heard from you for over a week now, so it looks like you don’t have any more questions for us.

Feel free to re-open this ticket if needed.

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

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

Normally, in order to include robots.txt to the build, you should go to Staatic > Settings > Build and add /robots.txt to Additional URLs.

Since the error indicates that robots.txt is being crawled, but with a prefix of /agi, resulting in a 404 page not found error, are you running WordPress from the /agi sub directory? What happens if, in the Additional URLs setting, you change /robots.txt to the full URL, e.g. https://localhost/robots.txt?

Looking forward to your response.

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.

Sure, and if you need any further assistance, feel free to get back to us any time.

The former, i.e. literally https://biteable.com/blog/create-beautiful-charts/

Right, so I need to change some wordpress config somewhere then?

No, in that case Staatic invalidates the correct path by invalidating “/blog/create-beautiful-charts/”. CloudFront invalidation is based on the URL path segment. The fact that the URL internally translates to an S3 object path “/blog/create-beautiful-charts/index.html” should not matter.

Also, I’d like to try premium 1.4.4 but cannot find where to get it.

Older releases of Staatic are currently only available through our package repository at https://packages.staatic.com/ – see also https://staatic.com/documentation/setup/installation/#composer. We will add the ability to download older releases from the customer portal at https://app.staatic.com/ in the near future though.

The only issue remaining now is that the Cloudfront invalidation is not matching the index.html object in S3

The invalidation URL should depend on the permalink structure of your WordPress site, not on the actual file path in S3. Just to be sure, on your public site, is the URL of the page https://example.com/blog/create-beautiful-charts/ or https://example.com/blog/create-beautiful-charts/index.html?

Hello, just checking if 1.4.4 includes the workaround?

Yes, it absolutely does. Please feel free to give it a try and looking forward to hear if it works well for you.

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