-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to parse server JSON message #12
Comments
Win 7 Pro x64, FF 3.5.6, Xrefresh 1.3, Add-on 1.3, e Text Editor I am having this issue as well. Refresh works fine with other tested file types (RoR, HTML, PHP, JS). |
Getting the same problem here in a RoR project. Example: http://imgur.com/UfD6v.png Vista 32, Firefox 3.6 beta 5, Firebug 1.5X.0b8, XRefresh 1.3 |
I have the same problem here, the server generates invalid JSON as not all the backslashes in the file paths are escaped. This is the output generated for my project by XRefresh Monitor 1.3 (parsed by Firefox plugin 1.4) on Windows Vista x64: { The "contents" JSON element is where it seems to go wrong. Otherwise excellent project! |
Same here. And as hongaar said, the problem lies in "contents" field not escaping backslashes in css file paths (if that file was deeper inside configured Path in XRefresh) |
I'm using this fix already, thanks! But, it would be so much cooler to have it natively :) |
Unfortunately I'm not going to fix it anytime soon, because I've switched to Mac. And I pour all my spare cycles in TotalFinder these days. One day I will get rid of WinMonitor and implement all in pure ruby. So also win people may run a ruby version. But it is quite a work ... |
Great. So in the meantime maybe you can include this fix temporarily in source. This is not perfect solution, I know. But in contrast to error message it is at least a solution. BTW, thanks for this great program. I'm using this all the time now. |
I have xrefresh server 1.3 and firefox extension 1.3.
On css file modification it prints "Unable to parse server JSON message:" following by a JSON message but doesn't refresh.
The text was updated successfully, but these errors were encountered: