Closed (won't fix)
Project:
Recent Changes
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Aug 2007 at 17:35 UTC
Updated:
3 Feb 2013 at 18:37 UTC
Jump to comment: Most recent file
Comments
Comment #1
toemaz commentedI had the same problem. So, I modified the module. Find the patch attached to this comment.
If the module maintainer thinks this is a good idea and you were successful testing it, I guess this patch can be applied.
Comment #2
dwarner commentedWhat version was this patch created from? I'm using 1.1 of Recent Changes and the patch wouldn't apply.
Comment #3
toemaz commentedThe patch was made against the 5 branch which was the HEAD by that time. You can see this in the header of the patch.
So checkout the 1.5 revision and apply the patch. Let me know if it works for you because if we are with 2, we might push this patch easier into this module.
Comment #4
toemaz commented@silfreed
Were you able to apply the patch and if so, is it working for you. When you reply positively, set the issue status on patch (RTBC).
Thx
Comment #5
duaelfrThis version of Recent Changes is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.