• Resolved vicso

    (@vicso)


    I am reaching out regarding a technical issue my client’s website is currently facing. The website utilizes the W3 Total Cache plugin in conjunction with an AWS (Amazon Web Services) configuration for enhanced performance.

    Up until recently, everything had been running smoothly. However, we encountered an issue after adding a new page to the website. It appears that the styles for this new page are not being properly updated. Despite attempting to clear the cache through the admin panel, there have been no noticeable changes in the appearance of the styles.

    In an attempt to troubleshoot, I inspected the files within the AWS bucket associated with the website. Strangely, even after confirming that the styles have been updated on the server, the cached styles continue to be served.

    I am left wondering if there might be a step or detail that I am overlooking in the cache-clearing process through the admin panel. I am open to any guidance you can provide to help us resolve this issue. It’s crucial for us to ensure that the new page’s styles are accurately displayed to our visitors.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vicso

    Thank you for reaching out and I am happy to assist you with this.

    Just to confirm, have you made any changes in any CSS file? Also, have you purged the CDN also once you have made the changes and can you please share the URL of the newly created page so I can check this?

    Thanks!

    Thread Starter vicso

    (@vicso)

    Hello?@vmarko
    Thank you for the quick answer. Yes, the styles have been changed, and a new page has been created. Additionally, new styles have been added to the AWS bucket. When you mention updating the CDN, could you please provide more details, what do you mean? Unfortunately, due to the nature of this large corporate project, I am unable to share a link here.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vicso

    Thank you for your feedback.
    to confirm, the existing CSS files have been updated and uploaded to the AWS, however, the style was not changed accordingly.
    if this is the case, the reason is that the fact that the css file is cached in the browser. If you have enabled the cache-control header in the Browser Cache settings and expires header, the value is set to 1 year by default. To remedy this, in Performance>General settings, enable the Prevent caching of objects after the settings change option under the CSS&JS section, save all settings purge the cache, and also purge the CDN cache. This will add a random query string to the static files ?xNNNNN which will force the browser to fetch a new, updated file. Because the browser thinks that since the file name remains the same, it does not need to fetch a new file from the CDN/server.

    You ca always drop us a direct email via the plugin in Performance>Support.

    Let me know if this helps!

    Thanks!

    Thread Starter vicso

    (@vicso)

    Hello @vmarko
    Thank you for your message. Yesterday, I conducted some tests, and it appears that the issue has been resolved. However, one question remains. Previously, I overlooked this aspect. Yet, during testing, I observed that there are attempts to retrieve addresses for pagination styles from the following bucket: “d3w5782fermyc3.cloudfront.net/wp-content/plugins/simple-share-buttons-adder/”, “d3w5782fermyc3.cloudfront.net/wp-content/plugins/contact-form-7/”, and so on. It is worth noting that I do not require these plugins to be cached in the bucket, as there isn’t even a designated folder for plugins. Could you kindly advise me on how to prevent the caching of plugins?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vicso

    Thank you for your feedback and I am glad that the issue is resolved.
    You can exclude any file from being cached in Performance>CDN>Advanced>Rejected files.
    You can add all the files in the plugin by adding the path to the file, for example: /wp-content/plugins/contact-form-7/*

    We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users.
    Thanks!

    Thread Starter vicso

    (@vicso)

    Hello @vmarko
    Thanks for your willingness to help. But something really strange is happening. I go to the Performance>CDN>Advanced>Rejected files and added there:

    {wp_content_dir}/plugins/contact-form-7/.*
    {wp_content_dir}/plugins/simple-share-buttons-adder/.*
    {wp_content_dir}/plugins/cf7-conditional-fields/.*
    {wp_content_dir}/plugins/wp-mail-smtp/.*

    https://prnt.sc/PltrQ88a0l3m here link to screen for example

    By the way there were already: {wp_content_dir}/plugins/.* line but it does not work. I saved settings, and Empty All Caches but nothing the error with https://d3w5782fermyc3.cloudfront.net/wp-content/plugins/cf7-conditional-fields/ etc. steal there. And again the error with the cache is reproduced. Bucket style is not updated again( So far I’ve tried everything. I tried resetting the settings to default. But still nothing worked.

    Please, can you give some advice or documentation – a checklist for setting up, maybe somewhere you can import the basic – correct plugin settings?


    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @vicso

    Thank you for your feedback.

    Have you also purged the CDN. You can do this in the top admin bar Performance>Purge Modules>CDN.
    Please reach out directly via the plugin in Performance>Support or clicking on the support button, and provide the URL of the website so I can check this.
    Thanks!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Resolving Styling Issue with W3 Total Cache and AWS Integration’ is closed to new replies.