Difference between revisions of "Issue:Firstrevisionsince excludes too many pages"

Revision as of 09:21, 12 June 2009

Problem

I updated from DPL 1.7.4 to 1.8.0 and recognized that "firstrevisionsince" excludes too many pages on my query in http://www.thomas-krenn.com/de/wiki/Benutzer:Wfischer#Neueste_Artikel_von_Werner_Fischer_seit_1.12.2008 I tried to downgrade back to 1.7.4 but this does not fix the problem. I'm not 100% sure whether the page still worked correctly before the update to 1.8.0, but the Google Cache entry from "26. Mai 2009 03:43:42 GMT" still showed the complete list: http://209.85.129.132/search?q=cache:vxO-r7k8Uf4J:www.thomas-krenn.com/de/wiki/Benutzer:Wfischer+http://www.thomas-krenn.com/de/wiki/Benutzer:Wfischer&cd=1&hl=de&ct=clnk&gl=at&client=firefox-a

I created two pages in our wiki to document the issue. The first page Benutzer:Wfischer/Test1 includes firstrevisionsince=2008-12-01 and shows 20 results. The second page Benutzer:Wfischer/Test2 does not include the firstrevisionsince=2008-12-01 statement and shows 69 results back to the date 1st december 2008.

• http://www.thomas-krenn.com/de/wiki/Benutzer:Wfischer/Test1
• http://www.thomas-krenn.com/de/wiki/Benutzer:Wfischer/Test2

(I included "debug=3" in these examples)

Reply

There have been major changes in this part of the code (some of them before 1.7.4), so it is likely to be an error that was involuntarily introduced. I will look after it. Gero 21:35, 8 June 2009 (UTC)

Thanks for this fast reply. After adding two new articles in our Wiki I just noticed that now it is also necessary to add an ?action=purge to the URL, otherwise the new articles are not included in the results. Switching back to 1.7.4 does not fix this (so I'm still a little bit confused, because this has once worked in the past). Perhaps you can keep this in mind when you look after the original reported bug. PS: thank you very much for this extremely valuable mediawiki extension! --Wfischer 08:55, 9 June 2009 (UTC)

Update: I have tried once again to switch back to 1.7.4 and executed ?action=purge on the relevant pages afterwards - this way both the original issue with "firstrevisionsince" and the issue that is necessary to add ?action=purge as described above are gone. So if you are having the same issues you can revert back to your former DPL version (and execute ?action=purge once on your relevant sites) until a fix for 1.8.0 is available. --Wfischer 13:31, 9 June 2009 (UTC)

'firstrevisionsince' and 'allrevisionssince' should now work correctly. The fitst statement always delivers only one revision whereas the second one should return all article revision that were created after the given timestamp.Gero 15:48, 9 June 2009 (UTC)

I updated to 1.8.1 and now 'firstrevisionsince' works again also for me. Thank you very much! --Wfischer 09:05, 10 June 2009 (UTC)

The caching problem is not so easy to identify. Did you change the base version of MW software? Can you observe the same behaviour here in this wiki? You may want to add $wgEnableParserCache = false; to your LocalSettings.php. Gero 15:48, 9 June 2009 (UTC)

I did not change the base version of MW software. With DPL 1.8.1 the problem still exists (with 1.7.4 I had no problem). I was able to reproduce this in this wiki. I created a small page User:Wfischer with a DPL query with ordermethod=firstedit. Afterwards I created a new testpage here: Test5555. This new testpage Test5555 does not show up in User:Wfischer. If I would attach a '?action=purge' then it would work again. I also discovered when I go now to my userpage User:Wfischer and I click on 'Edit' and then on 'Preview' then the new testpage Test5555 is shown in the preview (because there the cache is not used as far as it seems to me). I think that $wgEnableParserCache = false; would work, but if possible I would still like to use the cache for normal pages so if it would be possible that DPL 1.8.1 can handle it again as DPL 1.7.4 did it would be great. Let me know if I can assist you in fixing it somehow. --Wfischer 09:05, 10 June 2009 (UTC)

In fact there has been a change in the DPL code some time ago. I will revert to the orginal version although I will have to keep the new bahaviour for those cases where DPL is used in downward-compatibility mode with "intersection". But that should not bother you and others. My tests also showed that in PREVIEW mode MW does not use its ParserCache. The strange thing is that MW sometimes uses its ParserCache although it is explicitly told not to do so by parser->disableCache(). This gives me some head-ache with my own cache mechanism. But that's another story. Please wait for 1.8.2 and then try again then. Gero 12:36, 11 June 2009 (UTC)

Thank's a lot for this update. I'll wait for 1.8.2 and tell you then whether it works then for me. Again, thanks for this great MW extenstion! --Wfischer 08:21, 12 June 2009 (UTC)