Persistent Caching Issues Due to Reused Shape Names in EverWeb - Forum

  1. Portal Home
  2. Forum
  3. EverWeb
  4. Bug Reports

This discussion started in August 2025. EverWeb has changed a lot since then, so some answers may no longer apply.

These current help articles may help:

Find up-to-date answers in the EverWeb help articles. Still stuck? Start a new thread or contact support.

Persistent Caching Issues Due to Reused Shape Names in EverWeb



User: Andreas H. one year ago
Dear EverWeb Support,

I'm writing to report an ongoing and critical issue related to shape management and caching behavior within EverWeb.

Whenever I remove a shape (such as a symbol or image) and later create a new shape that is internally assigned the same name as the previous one, the browser continues to display the outdated, cached version. This occurs even after publishing changes and clearing local assets within EverWeb. The issue stems from the fact that the software appears to reuse internal shape names, which causes conflicts with browser-side caching.

As a result, I am forced to implement various workarounds—such as renaming elements manually or instructing end users to clear their browser cache—both of which are impractical and unsustainable, especially when managing a professional website or frequent updates.

A long-term and reliable solution would be for EverWeb to ensure that internal shape names are never reused, even if a shape has been deleted. A simple mechanism that assigns a unique ID to each new shape would completely eliminate this issue and greatly improve the reliability of published websites.

This problem has a significant negative impact on my workflow and the consistency of the user experience on my site. I kindly ask that this issue be escalated and considered as a development priority.

Thank you for your attention, and I look forward to your response.

Best regards,
AH

Last edit one year ago
User: Paul-RAGESW one year ago
Hi Andreas,

Sorry to hear about these issues.

By default, a web browser will cache certain code for up to 10 minutes. Your web hosting provider could be setting cache instructions for your website for longer. You can ask them about this.

If they are not using a CDN like cloudeflare and you are on an Apache Server, you can set the caching rules manually using EverWeb 4.3 or later.

Go to File-> Edit Publishing Settings and scroll down until you see 'Edit robots.txt & .htaccess'

Then in the .htaccess field (the bottom field) enter this code segment. This tells web browsers not to cache the content on your html pages.

<IfModule mod_headers.c>
<FilesMatch ".(html|htm)$">
Header set Cache-Control "no-cache, no-store, must-revalidate"
</FilesMatch>
</IfModule>


However, you need to ask your web hosting provider if they have CDN that is caching pages for longer and if they are using Apache for their server software, which is the most common server software.

-------------------------------
Paul
EverWeb Developer


Post Reply
You must login or signup to post.