Extension:SemanticUpdateOnPurge
 Release status: stable |
|||
|---|---|---|---|
| Implementation | Parser extension | ||
| Description | Updates Semantic MediaWikis attributes on a purged article. | ||
| Author(s) | Daniel Werner (Danwetalk) | ||
| Last version | 0.4.1 (2011-12-05) | ||
| MediaWiki | Tested on MW 1.17 and SMW 1.6.2 | ||
| Database changes | no | ||
| License | ISC license | ||
| Download |
README CHANGELOG |
||
|
|||
| Check usage and version matrix | |||
Contents |
Description [edit]
SemanticUpdateOnPurge updates all semantic data created with Semantic MediaWiki when purging a page. This extension is motivated by bug 22751 which actually isn't considered a real bug. Anyway, with this extension "dynamic attributes" are more comfortable and efficient to use if you have to use them. However, as you can see in the bug report, it is not recommended or supported by the SMW developers to use inline query results in attributes.
Another scenario where this extension can be useful is if you use Extension:External Data. If your external data sources change their values you can simply update the semantics on the MW article by pressing purge.
Installation [edit]
- Download the files from SVN or download a snapshot (select your version of MediaWiki)
- Create a directory
SemanticUpdateOnPurgein your$IP/extensionsdirectory - Extract the files to this
$IP/extensions/SemanticUpdateOnPurgedirectory - Add to the end of LocalSettings.php:
require_once("$IP/extensions/SemanticUpdateOnPurge/SemanticUpdateOnPurge.php");
- Installation can now be verified through Special:Version on your wiki
Compatibility [edit]
The extension works with Semantic-MediaWiki 1.6.x (and probably 1.6). It does not work with MediaWiki 1.18 currently. There were reports that the functionality was broken somewhere around the 1.5.x branch of SMW, though, it has been reported working with some older SMW versions than 1.6 as well (current version should at least work with some old SMW versions).
Version history [edit]
The full version history can be found within the RELEASE-NOTES.
