Last modified: 2009-12-01 15:12:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T23720, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21720 - Inline queries do not update if caching is used
Inline queries do not update if caching is used
Status: RESOLVED DUPLICATE of bug 9738
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Markus Krötzsch
Depends on:
  Show dependency treegraph
Reported: 2009-12-01 10:14 UTC by Neill Mitchell
Modified: 2009-12-01 15:12 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Neill Mitchell 2009-12-01 10:14:41 UTC
Inline queries do not update after a user submits a form if you have caching enabled. I received two suggestions to solve this. Either turn off caching or get users to manually trigger a purge by adding ?action=purge onto the URL and refreshing their browser.

Neither of these are practical. Without caching performance drops significantly. Expecting users to manually muck about with URL's is not going to be accepted.

A workaround I've found for this is to use the MagicNoCache extension. I then
put __NOCACHE__ into my templates, so that when the form is submitted
and it then displays the template the update seems to be triggered and
subsequent inline queries show the updated data.

However, this is not ideal as a large site is going to suffer from
effectively disabling the cache for many pages. The MagicNoCache code
looks quite simple. It makes one MW call. Could it not be incorporated
into the SemanticForms Save page functionality? Would this work? It
would be great if it did. Naturally, wiki's tend to be read much more often than
written, so obviously it would be good if the cache loss penalty was
taken at write time rather than every read.

I posted this on the mailing list, but did not receive a reply. However, it is a fundamental issue (especially for larger sites) that won't go away by itself!
Comment 1 Markus Krötzsch 2009-12-01 15:12:20 UTC
This is a duplicate of an existing feature request. I don't think that Semantic Forms are in charge of fixing this, but a separate request could be created for SF if considered apropriate.

*** This bug has been marked as a duplicate of bug 9738 ***

Note You need to log in before you can comment on or make changes to this bug.