Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Frank

    (@staaticfrank)

    Hi @zarzadzany , we haven’t heard back from you for a while, so we’ll assume you managed to get this sorted and we’ll mark the topic as resolved.

    If you’re still unable to exclude /robots.txt, feel free to open a new topic with what you currently have in Excluded URLs and whether /robots.txt is listed under Additional URLs, and we’ll be happy to help further.

    Plugin Support Frank

    (@staaticfrank)

    Hi @antdantd , thanks for reaching out and you’re correct.

    This happens due to the default PHP DOM-based parser, which can normalize HTML and serialize non‑ASCII characters (like Cyrillic) into numeric entities (e.g. а). It’s usually only cosmetic (browsers render it the same), but we understand it’s not ideal if you want the source HTML to remain readable. To keep national characters as-is, switching the parser to Simple Html Dom Parser often preserves the original characters/markup better than the PHP DOM wrapper.

    Thanks for sharing your solution!

    Plugin Support Frank

    (@staaticfrank)

    Hi there,

    Thanks for reaching out! The Excluded URLs setting should definitely work for /robots.txt, so let’s figure out what’s going on.

    A few questions to help troubleshoot:

    1. What exactly did you enter in the Excluded URLs field? It should be /robots.txt with the leading slash. If your WordPress is installed in a subdirectory (e.g., /blog/), the path would need to be /blog/robots.txt instead.
    2. Is /robots.txt also listed in your Additional URLs? By default, Staatic adds /robots.txt to the Additional URLs list (Settings > Build > Additional URLs). If it’s there, that would explain the issue; removing it from Additional URLs would be the simplest fix.
    3. Did you run a fresh publication after saving the settings? Sometimes a previous build’s data can persist.

    Let us know what you find and we’ll get this sorted!

    Plugin Support Frank

    (@staaticfrank)

    Thank you for your review. We’re sorry to hear about the difficulties you experienced with the S3 functionality and URL management in our plugin. We understand how frustrating this can be, and we strive to ensure our plugin performs seamlessly for everyone.

    We would have appreciated the opportunity to assist you directly, as the issue you’re facing might be a basic configuration or environment specific problem. Our S3 support is working well for many other users in production, and we are confident we can help resolve your issue too.

    Please feel free to reach out to us by opening a support topic on our forum or emailing us at [email protected]. We are committed to helping all our users and would love to work with you to find a solution.

    Looking forward to the possibility of assisting you further.

Viewing 4 replies - 1 through 4 (of 4 total)