https://bugzilla.wikimedia.org/show_bug.cgi?id=20601





--- Comment #2 from [email protected]  2009-09-13 01:03:55 UTC ---
Created an attachment (id=6546)
 --> (https://bugzilla.wikimedia.org/attachment.cgi?id=6546)
turn off damaging debugging comments in production environment

You don't understand how serious the problem is.
For rapidly changing wikis, users won't notice the problem.
But for small wikis, you will be doubling the users RSS stored articles each
time he browses... and he will wonder why they have reappeared again as
new.

Let's see the difference in the same HTTP GET of
index.php?title=Special:RecentChanges&feed=rss
before and after doing
TRUNCATE TABLE objectcache:
>@@ -24 +24 @@
>-              <lastBuildDate>Sun, 13 Sep 2009 00:09:25 GMT</lastBuildDate>
>+              <lastBuildDate>Sun, 13 Sep 2009 00:12:10 GMT</lastBuildDate>
>@@ -87 +87 @@
>-&lt;!-- diff generator: internal 2009-09-13 00:09:26 --&gt;
>+&lt;!-- diff generator: internal 2009-09-13 00:12:10 --&gt;
Well, we see the lastBuildDate holds the same information, so the
attached patch to remove the superfluous diff generator comment will not
remove any information, and at the same time not confuse RSS readers
into thinking the article has changed!

The better maintained a wiki is (the more often it is updated), the more
frustrated the user becomes, as each update truncates the objectcache,
causing the comments you are putting into the bodies to change.

Keep your debugging comments off in production environments please.


-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to