Ok, this one's had me scratching my head for a couple of days.
Basically I have a content type that relates to a flash file on my server, and this flash loads an xml file for it's variables. The xml is created within the node type's template file using fwrite and $_GET variables from the url. This definatley works the first time that the page is loaded (with the correct data taken from the URL), but when I reload with different variables, the first loaded data is loaded again. I've checked the xml file, and this is re-written correctly, so it seems that the xml file is being cached locally by the user's browser.
I've tried a couple of common methods to bypass this (i.e. adding a random number to end of the .xml when loading it in flash to con it into thinking it's a new file) but they don't seem to work. So I'm wondering if this might be to do with the way Drupal Caches data.
Any ideas?
Comments
Yeah, most likely caching.
Yeah, most likely caching. If you are requesting the page as a node, then the node will normally be cached. Passing it extra unknown parameters via GET will not influence the caching rules.
Either consider passing your required parameters as part of the normal URL, or look at bypassing the cache. I can't recall how to do that, but it should be documented nearby...
You can test/prove it by flushing the cache_content DB table
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
.dan. is the New Zealand Drupal Developer working on Government Web Standards
You could set some cache
You could set some cache header information.
For our site, this is enough:
-----------------------------------------
Joep
CompuBase, Drupal, websites and webdesign