Last modified: 2014-02-01 10:19:16 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 T26979, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 24979 - Support query result refresh with an update button provided for inline-queries
Support query result refresh with an update button provided for inline-queries
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Markus Krötzsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-29 16:47 UTC by skew
Modified: 2014-02-01 10:19 UTC (History)
2 users (show)

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


Attachments

Description skew 2010-08-29 16:47:58 UTC
This is actually a repeat of an enhancement listed for Halo here, 

   http://smwforum.ontoprise.com/smwbugs/show_bug.cgi?id=12336

but I'd like to see it in SMW instead.  It's explained well there, but in short, it would be useful to have a button associated with an inline query (or perhaps associated with a page that has one or more inline queries) that, when pressed, updates inline query results.  My choices for updating query results now: edit and save the page, wait, or include __NOCACHE__.  I've been using the latter for the sake of the users, but I'd much rather improve performance by using the cache and letting users hit a refresh button when they know a change exists, when they're not finding what they want, or for whatever reason.
Comment 1 MWJames 2014-02-01 10:19:16 UTC
Using a page's action=purge together with the $smwgAutoRefreshOnPurge=true in SMW 1.9 should solve the problem.

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


Navigation
Links