Member Avatar for djnzak

Hi,

I am editing the css code of an existing script, Docebo.

The problem is all the browsers I have tried do no give me a quick updated view on the css style. That is it still shows me the old css sheet and so I cannot see the changes quickly. I was wondering if this is client side or server side issue and would like to know the best way to overcome it.

Thanks

  • 3 Contributors
  • 2 Replies
  • 119 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Member #120589

Dani AI

Generated

Both client- and server-side caching can make stylesheet edits invisible. and correctly identified caching as the issue; what follows is a compact, practical diagnostic and a few reliable fixes to determine exactly where the cache lives and how to force fresh CSS during development.

First, identify the exact stylesheet request and inspect its HTTP headers. The Network panel in browser devtools or a quick curl will show whether the server is instructing a long cache life, returning 304 Not Modified, or whether an intermediate cache/CDN is involved. Example check:

curl -I https://example.com/path/to/style.css

HTTP/1.1 200 OK
Cache-Control: max-age=86400
ETag: "abc123"
Last-Modified: Tue, 06 Jul 2010 12:00:00 GMT

A long max-age, Expires far in the future, or frequent 304 responses points to server-side or proxy/CDN caching. Intermediate caches often add headers like Via or X-Cache.

Two practical fixes: (1) cache-busting by versioning the file name or query string so the browser requests a fresh file:

<link rel="stylesheet" href="/css/style.css?v=20100704">

(2) adjust server headers during development (temporary). Example Apache snippet (requires mod_headers):

<FilesMatch "\.(css|js)$">
  Header set Cache-Control "no-cache, no-store, must-revalidate"
</FilesMatch>

Docebo installations can also have asset aggregation or platform caches; check the LMS admin/tools for cache or asset settings and purge them after changes. Never leave aggressive no-cache settings in production—use fingerprinted filenames (or query-versioning) as the long-term solution so end users receive updates only when assets change.

Recommended Answers

All 2 Replies

Member Avatar for gaurang4

Hi Friend,

You are getting this problem because of cashed copy of webpage.

Try to refresh the page with F5 button or refresh button in browser.

Personally I would like to suggest you to use Firebug add-on in Firefox, or if you are using chrome then right click on page and select Inspect element.

This will let you change the css and see the effect on page in browser.

I hope this would be helpful.

Regards,
Gaurang

commented: well worded & helpful :) +1
Member Avatar for Member #120589

Are all your pages being cached? Some apps have a cache folder. In order for changes to templates and styles to appear, the cache needs to be purged (delete cache files).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.