Hello, I just discovered weird anomalies in the articles SMW properties in one of my wikis. I can not say for sure since when this is happening since the content of my wiki was growing over the last days and for some time before there was nobody working on it.
Some weeks ago I updated to SMW 1.5, no 1.5.1 yet. So perhaps this is a bug of 1.5 or it is something else but I am not sure if this ever happened with SMW 1.4 or earlier. At least I never discovered something like that in earlier versions. So the problem is that article pages have properties of OTHER articles. I discovered that this has something to do with the job queue. When a article A updates its semantic data and then calls the job queue and updates another page B, some (but not all) of the pages A properties get passed over to page B! This is really weird and makes a lot of trouble in my wiki. Also it doesn’t happen every time the wiki processes a page from the job queue but I can not say under which exact circumstances this happens. One more thing is, I have the "SemanticUpdateOnPurge" extension installed (I wrote this extension by my own) which updates a pages attributes on a page purge. This bug happens a lot on page purge. I can not even say for sure that it happens when saving the page, too. So perhaps one of you more experienced developers could take a look into the extensions code, perhaps there is something wrong with that but in my opinion it should be save: http://www.mediawiki.org/wiki/Extension:SemanticUpdateOnPurge it is not much code, the most important part is: $title = $parser->getTitle (); $output = $parser->getOutput(); SMWParseData::storeData($output, $title, true); Which is called onParserAfterTidy and only when action=purge && the $title is the title of the page which got purged. So the job queue job shouldn’t know any of this, right? I have a bugtracker for my wiki, you can find some more information on this in German language at http://mantisbt.rpgdev.stejau.de/view.php?id=7 My wiki is http://gom.rpgdev.stejau.de (I am Player140 there) Would be very happy if we could solve this problem soon. I wonder if it's a SMW bug or something else. Hope you can help me out with this. Thanks a lot for any suggestions! Daniel ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
