Disabling cache for tiddlyspot

Ed

unread,

Oct 1, 2007, 1:20:21 PM10/1/07

to TiddlyWiki

I have a wiki that is accessed by 5 other people. I noticed that when
I accessed it after I knew someone else had made an edit, the page
showed me an old copy of the site. I assume this is because the
browser loaded the cached version instead of the most recent one.

Is there code you can include in the tiddlywiki that disables the
browser cache for that page, or otherwise forces it to reload and read
the most recent wiki?

Message has been deleted

Ed

unread,

Oct 1, 2007, 4:39:29 PM10/1/07

to TiddlyWiki

Arg! sorry google didn't respond the first two times I tried to
submit this. Guess it went through. . .

FND

unread,

Oct 1, 2007, 4:42:33 PM10/1/07

to Tiddl...@googlegroups.com

> Is there code you can include in the tiddlywiki that disables the
> browser cache for that page, or otherwise forces it to reload and read
> the most recent wiki?

No, that's not possible (at least I can't think of anything).
Have you tried force-reloading the page by using CTRL+R or SHIFT+R?

-- F.

Eric Shulman

unread,

Oct 1, 2007, 5:01:57 PM10/1/07

to TiddlyWiki

> Is there code you can include in the tiddlywiki that disables the
> browser cache for that page, or otherwise forces it to reload and read
> the most recent wiki?

Try adding the following in [[MarkupPostBody]]:

HTH,

-e
Eric Shulman
TiddlyTools / ELS Design Studios

FND

unread,

Oct 1, 2007, 5:14:51 PM10/1/07

to Tiddl...@googlegroups.com

> Try adding the following in [[MarkupPostBody]]:
>
> <head>
> <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
> <META HTTP-EQUIV="Expires" CONTENT="-1">
> </head>

I didn't know about those meta tags until now - thanks Eric!
But shouldn't that code go into [[MarkupPostHead]], without the
additional <head>...</head> tags?

-- F.

Eric Shulman

unread,

Oct 1, 2007, 5:27:21 PM10/1/07

to TiddlyWiki

Actually, no. Because of the way InternetExplorer implements their
cache, these meta statements have to occur toward the *end* of the
document, so that at least 64K of the file has been loaded into the
browser's buffer before the "Pragma" and "Expires" statements are
processed. In addition, in order for them to work at the end of the
file, they have to be enclosed in a seemingly misplaced <head>...</
head> block.

-e

FND

unread,

Oct 1, 2007, 6:10:51 PM10/1/07

to Tiddl...@googlegroups.com

> Because of the way InternetExplorer implements their cache [...]

Of course, IE requires special treatment again - I should have guessed
that...
Thanks for the insight.

-- F.

Peter Merel

unread,

Nov 6, 2015, 8:04:47 PM11/6/15

to TiddlyWiki, Tiddl...@googlegroups.com

What's the recommended way to do no-cache in TW 5? I'm finding I'm having to tell people all about shift-command-R and I'd rather not ...

Cheers,

Pete.

Tobias Beer

unread,

Nov 7, 2015, 4:49:46 AM11/7/15

to TiddlyWiki, Tiddl...@googlegroups.com

Hi Pete,

What's the recommended way to do no-cache in TW 5? I'm finding I'm having to tell people all about shift-command-R and I'd rather not ...

The thing is, the problem you're experiencing is not one of TW5 but rather of the server serving it. Sometimes you can add ?something to the end of the url to force the browser to clear the cache, e.g.:

http://tobibeer.github.io/tb5?clear-cache

Notice how any tiddler-title slug / permalink is added after that pseudo-url-parameter.