Redmine API doesn't work after 2.0.3 upgrade
Replies (7)
RE: Redmine API doesn't work after 2.0.3 upgrade
-
Added by Jon Lumpkin over 12 years ago
Well, it looks like the way it parses JSON has changed quite a bit. As in, a bit more strict. I can now submit an issue, but what would be the right way to encode something like a stack trace, where one would have new lines?
RE: Redmine API doesn't work after 2.0.3 upgrade
-
Added by William Roush over 12 years ago
Jon Lumpkin wrote:
Well, it looks like the way it parses JSON has changed quite a bit. As in, a bit more strict. I can now submit an issue, but what would be the right way to encode something like a stack trace, where one would have new lines?
Can you post your current JSON request and the more strict one that works?
I'm curious if the strictness is a bug or if it enforcing proper JSON was a bug fix before you go posting it to the issue tracker.
RE: Redmine API doesn't work after 2.0.3 upgrade
-
Added by Jon Lumpkin over 12 years ago
Sorry about the late reply. It used to look like:
"'issue': { " +
"'project_id': 'system', " +
"'subject': '" + message + "'," +
"'description': '" + theDescription + "'" +
"}"
What I changed it too now looks like this:
"{\"issue\": { " +
"\"project_id\": \"" + redmineProjectID + "\"," +
"\"subject\": \"" + message + "\"," +
"\"description\": \"" + theDescription + "\"" +
"}}"- wrap the whole request in {}
- " versus '
So, it looks like over the time of our setup (from 1.0.1 to 2.0.3), something really changed with the way JSON is parsed, and perhaps became more strict (my previous one doesn't verify I do not think).
So, by making those changes, the only thing that doesn't work now is my theDescription. This is a multiline string (http://www.redmine.org/boards/2/topics/30999), but I was using Microsoft's .net Server.HTMLEncode() (http://msdn.microsoft.com/en-us/library/w3te6wfz.aspx) method to encode this. I don't think that's placing the new lines correctly, but it worked in previous iterations. If I just put a random string (or literally pass the string 'theDescription'), the new way works.
theDescription is something like this:
Stack Trace: at System.Windows.Window.OnClosing(CancelEventArgs e) at System.Windows.Window.WmClose() at System.Windows.Window.WindowFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) Report Number: Report Key: 0 User: randomuser Machine: amachine Server:
I am just wondering what changed with the way it handles this formatted text (basically just need newlines), and how I should handle that, especially in a .net world.
RE: Redmine API doesn't work after 2.0.3 upgrade
-
Added by Alexey Filatov over 12 years ago
I have the same problem when I try to send multistring. It works in 1.3 and I don't know what to do now. My perl example:
my $str = sprintf('{"issue": {"notes": "%s", "custom_field_values":{"4":"%u"}}}', join("\n", @changed), $rev);
How to send the text with several strings?
RE: Redmine API doesn't work after 2.0.3 upgrade
-
Added by Etienne Massip over 12 years ago
GIYF:
With .Net, use HttpUtility JavaScriptStringEncode() methods.
With Perl, you can try e.g. JavaScript-Value-Escape.
RE: Redmine API doesn't work after 2.0.3 upgrade
-
Added by Alexey Filatov over 12 years ago
I've changed "\n" to "\r" and how it works.
$files = join("", @changed);
$files =~ s/\n/\\r/g;
$files =~ s/\'/\\'/g;
RE: Redmine API doesn't work after 2.0.3 upgrade
-
Added by Jon Lumpkin over 12 years ago
Changing mine to use HttpUtilityJavaScriptStringEncode, as well as changing my \n to \r fixed the issue. Now to figure out why JavaScriptSerializer.Deserialize gives me back a different object. It now looks like the JSON returned has an extra level deep.