Open ghost opened 4 years ago
I also applied these changes to a clone of the git repo locally, I have made a branch from r7. If you want these changes I can upload them.
Thank you kindly - I have already fixed this in my working tree (I noticed it myself) which will be released sometime soon. I must be honest I am glad someone is using the export functions at all - not many do :) Please keep bug reports and fixes coming they are highly appreciated.
On Fri, Dec 6, 2019 at 12:19 AM A. Masimba Walker notifications@github.com wrote:
I also applied these changes to a clone of the git repo locally, I have made a branch from r7. If you want these changes I can upload them.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kahluamods/konfersk/issues/2?email_source=notifications&email_token=AAC33GJ23U7U3ZZJJ26ZGD3QXF46BA5CNFSM4JWC7I7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGCLDHA#issuecomment-562344348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC33GO3GTN4RDYWTTW5BATQXF46BANCNFSM4JWC7I7A .
My guild have found a few more bugs, however I haven't been able to debug them. I can raise them as git issues if you feel that is appropriate?
Here is fine. I am not used to looking on GitHub.
On Friday, December 13, 2019, A. Masimba Walker notifications@github.com wrote:
My guild have found a few more bugs, however I haven't been able to debug them. I can raise them as git issues if you feel that is appropriate?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kahluamods/konfersk/issues/2?email_source=notifications&email_token=AAC33GNLVHWDO4DGPSTGE23QYORORA5CNFSM4JWC7I7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG2IJCQ#issuecomment-565478538, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC33GLIC7AOE2VG2YPM3YLQYORORANCNFSM4JWC7I7A .
Whenever I try to export the item history on KSK, I get the following error:
I looked in the code and realised that this issue was prevalent wherever the lists are exported, or where the item history is exported. After searching the code for a while with a friend we found references to a different function for accesing date, we've applied those everywhere we saw calls to 'CalenderGetDate()' just as a temporary fix. The solution seems to allow me to export a valid XML string for the list and item history exporting.