Skip to content
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

Open
rahbari opened this issue Dec 7, 2009 · 8 comments
Open

Unable to parse server JSON message #12

rahbari opened this issue Dec 7, 2009 · 8 comments

Comments

@rahbari
Copy link

rahbari commented Dec 7, 2009

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.

@achilles283
Copy link

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).

@charlesroper
Copy link

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

@hongaar
Copy link

hongaar commented Feb 18, 2010

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:

{
"date": "18-2-2010",
"time": "9:04:18",
"root": "M:\Webdev\belshof",
"name": "Belshof",
"type": null,
"files": [
{
"action": "changed",
"path1": "styles\pirobox\style.css",
"path2": null
}
],
"contents": {
"styles\pirobox\style.css": "..."
},
"command": "DoRefresh"
}

The "contents" JSON element is where it seems to go wrong.

Otherwise excellent project!

@yoyek
Copy link

yoyek commented Feb 28, 2010

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)

@darwin
Copy link
Member

darwin commented Mar 4, 2010

@yoyek
Copy link

yoyek commented Mar 5, 2010

I'm using this fix already, thanks!

But, it would be so much cooler to have it natively :)

@darwin
Copy link
Member

darwin commented Mar 5, 2010

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 ...

@yoyek
Copy link

yoyek commented Mar 5, 2010

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants