= Description =
RecentChanges doesn't produce complete infomation, and seems not working

== Steps to reproduce ==
## Describe the steps needed to reproduce the bug. If we can't reproduce it, we  probably can't fix it.
 1. Do nothing. When I noticed, the bug was there. Weird.
== Example ==
##Add URL that show the bug, screenshot or test wiki markup that fail...
URL:http://www.mamedalove.com/cgi-bin/moin.cgi/RecentChanges

{{attachment:bug.jpg}}

##{{{
##Example wiki markup that fail
##}}}
== Component selection ==
## Where you think is this bug happening ? (general, plugin [plugin name], theme [theme name], ...
 * general: Somebody (maybe spamer) wanted to edit some page with spaming URL. I guess.
== Details ==
## If you got a traceback, please save the traceback page as html and attach here:
[[attachment:traceback.html]]

## if the bug is in this wiki, just kill the table and write: This Wiki.
## If a traceback is not available, please fill in the details here:
|| '''!MoinMoin Version 1.5.7''' || ||
|| '''OS and Version''' || ||
|| '''Python Version 2.4.3''' || ||
|| '''Server Setup''' || ||
|| '''Server Details''' || ||
|| '''Language you are using the wiki in''' (set in the browser/UserPreferences) || ||
== Workaround ==
How to deal with the bug until it is fixed: Don't use any macros, using RecentChange functions.

= Discussion =
Please look into data/edit-log, it could be broken. ever line in there must begin with a number.

From 1.5.8 docs/CHANGES:

{{{
    * Fixed cleaning of edit comments (control chars in there could damage
      edit-log).
}}}
If it is not caused by a broken edit-log, please re-open this bug and provide more details.

・Danke. I think I could fix it.

Actually I found two data/edit-logs so that I was not sure which one is ; I bet you are talking about /share/moin/mywiki/data/edit-log, though. You are not talking about /share/moin/data/edit-log, that contains 0kb, are you? Then, I replaced 0kb stuff (actually copy and paste) onto the first messy-numbers one. Actually, I think that must be just plain text with my poor knowledge about programming; however, against the possible worst case, I did not make and upload a new file containing nothing from the scratch, on my desktop to the server. It looks and works fine now.

Additionally, with this chance, I tried to upgrade to 1.5.8. Eventhough the explanation looks messy for the windows guys, I think My moin was successfully upgraded to 1.5.8. Unfortunately, it is difficult to figure out what version I use now easily. Yeah, I just guess and believe I am using 1.5.8. now. Maybe, Perhaps, Yes ( lyrics by Kraftwerk).

Anyway, thanks a lot to your help. Auf Wiedersehen!

= Plan =
## This part is for Moin``Moin developers:
 * Priority:
 * Assigned to:
 * Status: fixed in 1.5.8
----
## If you are a moin core developer, replace the category to Category* in these cases:
## Category MoinMoinNoBug - if this is not a bug.
## Category MoinMoinBugConfirmed - if you can confirm the bug on current code.
## Category MoinMoinBugFixed - after the bug is fixed in current code.
CategoryMoinMoinBugFixed