Forum Replies Created

Viewing 15 replies - 91 through 105 (of 112 total)
  • Plugin Author Team Staatic

    (@staatic)

    This thread was marked resolved due to a lack of activity, but you’re always welcome to re-open the topic.

    Plugin Author Team Staatic

    (@staatic)

    Alright, thanks for sharing.

    In order for Staatic to be able to crawl your site with HTTP basic authentication enabled, you need to make sure that the basic authentication credentials are filled in within Staatic > Settings > Advanced > HTTP authentication. See also this article from our documentation: https://staatic.com/documentation/administrator-guide/configuration/advanced-settings/#http-auth

    Does this resolve the issue for you?

    Plugin Author Team Staatic

    (@staatic)

    Hi @atleet, we’re glad to hear that you managed to resolve the issue. It would be good to hear what the cause was, for future reference and helping others facing the same issue.

    Regarding your question, there are multiple methods to prevent or discourage search engines from indexing your backend WordPress site, for example:

    – restricting site access using HTTP basic authentication or similar;
    – implementing the “X-Robots-Tag” HTML meta tag or HTTP header;
    – implementing the robots.txt file;
    – setting the Search engine visibility setting in WP-Admin > Settings > Reading to Discourage search engines from indexing this site.

    We highly recommend HTTP basic authentication or the X-Robots-Tag HTTP header, or a combination of the two. The X-Robots-Tag HTML meta tag, robots.txt and Search engine visibility setting are discouraged, because these can leak into your public static site, preventing it from being indexed as well.

    Please let us know if this answers your question.

    Plugin Author Team Staatic

    (@staatic)

    Got it. This is something we will definitely consider for a future release of the plugin. We don’t have a clear timeline yet, but depending of the amount of changes required to accommodate such functionality, it can be added sooner than later.

    Thanks @vojdany for your feature request. We really appreciate it and if you have any other requests, feel free to open another topic.

    Plugin Author Team Staatic

    (@staatic)

    Hi @atleet, first of all thanks for using Staatic.

    From what I understand, the static version of your site has been deployed to an AWS S3 bucket with website hosting enabled. A CloudFront distribution has been created with the S3 website bucket configured as the origin. When requesting as asset through CloudFront like style.css, CloudFront translates this to style.css/index.html, is that correct?

    In order to set up this configuration, did you follow this article from our documentation? https://staatic.com/documentation/administrator-guide/deployment/amazon-s3-or-compatible/#preparation

    Also, can you find the asset file in S3 using the AWS Console, within the correct path? Does the origin (S3 website) asset URL work?

    Looking forward to your feedback.

    Plugin Author Team Staatic

    (@staatic)

    If I understand your question correctly; what you are looking for is a way to convert a specific page or post with all of its images/styles and scripts into a static version of that page or post, which you would then upload to a specific S3 bucket? If that is the case, then I’m afraid that this use case is indeed not supported by Staatic at this moment.

    However, depending on your use case, we could add additional hooks to the plugin, allowing you to make this work with the help of a small companion script/plugin. For that to work though, we would need to know a bit more about your specific use case and the procedure you would follow to export and upload these pages. Would such a solution be workable for you?

    Plugin Author Team Staatic

    (@staatic)

    Hi @gorahul, first of all thanks for using Staatic. We’re sorry to hear that you are experiencing this issue on your site.

    The error you encountered is usually caused by having values in the rich content markup where a domain is targeted which is different from the site’s domain. You can use the Rich Results Test Tool from Google to find the error details.

    In case you think the relevant domain or URL should have been transformed by Staatic and was missed, please send us an email with your Staatic diagnostics file.

    The diagnostics file can be generated by going to /wp-admin/admin.php?staatic=diagnostics and may be sent to contact@staatic.com. It contains some environment information (feel free to open it in a text editor to verify). Please include the relevant URL as well.

    Looking forward to your response.

    Plugin Author Team Staatic

    (@staatic)

    Hi vojdany. First of all, thanks for your interest in using Staatic to improve the speed and security of your WordPress site.

    Staatic is designed to transform a dynamic WordPress site into a completely static site. It achieves this by removing any references to the dynamic WordPress installation. Therefore, it is not possible to generate a single static page within a dynamic WordPress installation.

    If you would be using Staatic to transform your complete site, we do offer a premium version of the plugin that is able to only (re)publish the changed posts and pages since the last publication.

    Does this answer your question?

    Plugin Author Team Staatic

    (@staatic)

    After some testing, we managed to find the reason for the URL to have not been transformed.

    When WordPress multi-site is setup with the subdirectories method, then network sites have a URL structure like this:

    https://example.com/ – main network site
    https://example.com/subsite/ – first network subsite
    https://example.com/subsite2/ – second network subsite

    In case the first subsite would be published, and it contains a link that references the subsite URL without an ending slash, e.g. https://example.com/subsite, then Staatic is unable to safely replace this URL with the URL of the resulting static site (based on the destination URL). If it would do so, any links from the first subsite referencing the second subsite would break. Therefore the solution in this case is to make sure to link to https://example.com/subsite/ (with an ending slash) instead of https://example.com/subsite.

    We will investigate whether it would be possible to automatically handle this situation in a future release of the plugin.

    Plugin Author Team Staatic

    (@staatic)

    Hi John. First of all, thanks for trying Staatic to speed up and secure your WordPress site.

    In order to find out why the site logo link is not replaced, would it be possible to share your diagnostics file with us?

    The diagnostics file can be generated by going to /wp-admin/admin.php?staatic=diagnostics and may be sent to contact@staatic.com. It contains some environment information (feel free to open it in a text editor to verify).

    This might give us some clues and could help us reproduce the issue on our environment.

    Looking forward to your feedback.

    Plugin Author Team Staatic

    (@staatic)

    The issue has been resolved after testing with a new beta version. The final version containing the fix will be released by the end of this week.

    Plugin Author Team Staatic

    (@staatic)

    Hi there. First of all, thanks for trying Staatic to speed up and secure your WordPress site, and sorry to hear that you are having issues with the publication.

    In order to find the cause of the stall, we need some more information. At which step does the publication stall exactly, and how many pages were crawled (or deployed) until then? You can find this information on the publication details page.

    Also a screenshot from the publication details page, and diagnostics file would be helpful to troubleshoot the issue. The diagnostics file can be generated by going to /wp-admin/admin.php?staatic=diagnostics and may be sent to contact@staatic.com. It contains some environment information (feel free to open it in a text editor to verify).

    Looking forward to your feedback.

    Plugin Author Team Staatic

    (@staatic)

    After some troubleshooting we found out that the error was caused by a URL with double slashes at the start of the path segment (http://example.com//something), which Staatic was unable to process.

    This should be fixed in the next release of the plugin.

    Plugin Author Team Staatic

    (@staatic)

    Restricting access by IP on cPanel can be done using a .htaccess file. However, if you have configured HTTP basic authentication, then that should be enough.

    Regarding the other error, there is either an invalid URL referenced somewhere within your site, or Staatic was unable to extract/transform the URL for some reason.

    In order to identify the responsible URL, can you please provide us with a diagnostics JSON file as well as the publication logs?

    The diagnostics file can be generated by going to /wp-admin/admin.php?staatic=diagnostics. It contains some environment information that helps us troubleshoot the issue (feel free to open it in a text editor to verify).

    In order to export the publication logs, you should first change these plugin settings (under Advanced):

    Logging: Extensive Logging
    HTTP Concurrency: 1

    Then start a new publication and once it has finished, go to the publication details and click the Logs tab. Then click the Export button at the top of the page.

    Both files may be sent to contact@staatic.com. Looking forward to your feedback.

    Plugin Author Team Staatic

    (@staatic)

    Hi @benleow, in order to generate the static version of your site, Staatic needs to be able to access your dynamic WordPress site over http/https. This error indicates that it got a 403 permission denied error preventing it from crawling.

    Could it be that you have restricted access to the site based on IP address? In that case the server IP should be accepted as well, since HTTP requests from the plugin originate from the server.

Viewing 15 replies - 91 through 105 (of 112 total)