How do I solve old content displayed in browser?

Post reply

❤Follow Topic(2)

0 favourites

5 posts

From the Asset Store

Building "Collapsing Blocks" Browser Games

$9.99 USD

This is a single chapter from the Construct Starter Kit Collection and the Student Workbook from the Workshop.

PBMCube

- mumu64
- - Joined 8 Feb, 2009
  - 248 topics • 881 posts
- 1
- 23 Jun, 2015
- Quote
I know this was mentioned somewhere else on the forum, but I cannot find it anymore.

Whenever I change content, for example an image (sprite), my Chrome browser keeps showing the old content, unless I go into incognito mode. Even after reloading.

Is there a way to solve this?

For example: on start of layout: clear browser cache. (but not the whole browser, of that poor user that came across my HTML 5 game ^^)

Or something like this?
- linkman2004
- - Joined 15 Jan, 2008
  - 98 topics • 1,576 posts
- 1
- 23 Jun, 2015
- Quote
Try refreshing the page with ctrl + F5 -- this should reload the page while ignoring cache.
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- mumu64
- - Joined 8 Feb, 2009
  - 248 topics • 881 posts
- 1
- 24 Jun, 2015
- Quote
hello linkman2004! I have tried that and while I might solve this with some shortcut combination for my own browser, what about the unknowing visitors?

What if I upload a new picture on my html5 site and old visitors see the old picture and would not know they are seeing old content.
- mumu64
- - Joined 8 Feb, 2009
  - 248 topics • 881 posts
- 1
- 24 Jun, 2015
- Quote
A website explained the following:

[quote:2jtnnal4]The cache manifest file is a simple text file that lists the resources the browser should cache for offline access.
Referencing a manifest file

To enable the application cache for an app, include the manifest attribute on the document's html tag:

<html manifest="example.appcache">

...

</html>

The manifest attribute should be included on every page of your web application that you want cached. The browser does not cache a page if it does not contain the manifest attribute (unless it is explicitly listed in the manifest file itself. This means that any page the user navigates to that includes a manifest will be implicitly added to the application cache. Thus, there's no need to list every page in your manifest. If a page points to a manifest, there's no way to prevent this page being cached.

So I should perhaps remove this, manifest-part out of the index.html site?

Is there already an option in C2 that can do this for me?
- mumu64
- - Joined 8 Feb, 2009
  - 248 topics • 881 posts
- 1
- 26 Jun, 2015
- Quote
Although I cannot test it out right now, this tutorial from Ashley answers my question. Case closed. ^_^

https://www.scirra.com/tutorials/70/off ... onstruct-2