Extension talk:SemanticUpdateOnPurge/Flow

Previous page history was archived for backup purposes at Extension talk:SemanticUpdateOnPurge/LQT Archive 1 on 2015-07-10.

This is really a great extension. I was wondering if there is a way to trigger the semantic update without having the user to purge the page manually? Something like purgeAfterSave...

Story: A wiki to manage tasks. Each task has an estimated effort. Ability to add comments. With each comment (added as Semantic Internal Object) 'hours worked' can be added. Now I need to summarize the hours worked for each task and assign the total to a property 'Hours Worked' for reuse on a dashboard. With SemanticUpdateOnPurge and a manually triggered purge, the Hours Worked get updated. It would be nice to have data updated without user interaction.

Which version of SMW do you have in use? I think in some newer version, Jeroen added the feature that the articles cache will be invalidated right after the first rendering after the save, which basically triggers an immediate purge. So far I was not able to confirm that behavior though. If that doesn't work for you, it shouldn't be much of a problem to write an extension that invalidates the cache after a save. See Title::invalidateCache(). Alternatively, this sounds like you could also use my extension Extension:Variables to calculate the hours worked right throughout the template calls and then simply display them wherever you want with #var or even #var_final (in case you want to display it in an info box on top for example). This would probably take some good load from the server.

In MW 1.18 action=purge requests will be split into two requests, one doing the purge and then a redirect which will lead to the actual page rendering. Therefore, in the first request where 'ArticlePurge' is called, 'ParserAfterTidy' won't be called apparently. That will happen during the second instance of the wiki where the rendering takes place. So when that happens, we can't know the purge was done. I'll look into this soon and take SMW 1.7 under consideration as well.

I really love this extension as I sometimes rely on ExternalData as values for SMW properties. I was wondering if there was any update with fixes for MW 1.18+ and/or SMW 1.7+.

Not that easy to make it compatible again but I got some ideas, so If I find the time I will try getting it to work. Hasn't been a high priority to me though since I am pretty busy with other projects currently. Would be nice though having this feature again on some of my Wikis so I will give it another try.

After some testing rounds (SUoP 0.3.1.1 on MW 1.17/SMW 1.5.7) we found that categories assigned to an article disappear when refreshing the page. Only after the page is saved again, categories are appear again.

SMW 1.5.7?? I thought 1.5.6 was the last in the 1.5 branch?! Also, SMW < 1.6 is not fully supported, the extension seems to work differently from version to version, there were too many internal changes and it doesn't work very well with 1.5.6 for sure, perhaps with 1.5.2 or earlier. Also it seems to work in SMW 1.6.2, can't confirm the category bug there.

Hi - I just tried this extension, and it doesn't work for me - when I purged the page, it simply removed all semantic data for the page. I'm using MW 1.18 alpha and SMW 1.5.5. Has anyone tried this extension recently? Yaron Koren 18:31, 10 February 2011 (UTC)

try to use this too since it came out but it never work on my mediawiki installation.--Msevero 02:28, 12 February 2011 (UTC)

Indeed, it looks like it stopped working with MW 1.16 or some late SMW, just tested it in my Wiki. I will look into this, didn't recognize it stopped working... --Danwe 03:06, 14 February 2011 (UTC)

I was wrong before, had the extension disabled for some reason in my test wiki... It works fine here: MW 1.16 and SMW 1.5.5 as well as 1.5.4. How did you guys test this? Did you use some external data import or something? I simply use [[Test::{{CURRENTTIMESTAMP}}]], purge it and see whether the property value is updated at the Special:Browse page after the purge. --Danwe 08:48, 14 February 2011 (UTC)

Hi, sorry for the delay. I just picked a normal page that has some semantic properties, hit "refresh" (after installing the extension), and then, in the "Special:Browse" page, I saw that all the properties were gone. After uninstalling the extension and resaving the page, they were back. Yaron Koren 23:25, 17 February 2011 (UTC)

Doesn't work for me in 1.5.6 anymore... So I am about to find a solution for the problem. Any ideas for a new fix? --Danwe 20:21, 6 June 2011 (UTC)

Currently they are applying a lot of changes to SMW in preparation for the 1.6.0 release. Whilst looking for a solution I recommend to have a look at the version in trunk too. Cheers --[[kgh]] 20:37, 6 June 2011 (UTC)

Works with SMW 1.6.1, haven't tested it on 1.6, but even version 0.2.1 of my extension was working there without any changes. So I guess there was something 'broken' in some SMW version around 1.5.4+ Nevertheless, I made an update to 0.3. Please report if you have any problem with SMW 1.6, 1.6.1 or perhaps a different MW version than 1.17 (there might be a small chance the extension was broken due to MW, not SMW) --Danwe 15:48, 20 September 2011 (UTC)

We are testing 0.3.1 on MW 1.17/SMW 1.5.7 right now, and for the moment it looks good in connection with our SIO objects. Maybe you could consider the put the ExtensionCredits so it would appear in the Special:Version under Semantic extensions as the other SMW related extensions.

Thanks for the feedback, I have adjusted the code so the extension will appear as semantic extension as suggested above.