Changes Not Being Sent to Server on Mac OS X 10.7.3 about chrome-devtools-autosave HOT 18 CLOSED

I'm having a similar issue. Server was working fine. Functioning well on both file:// and localhost schemes (loading config files when working on localhost sites); nothing has been changed, yet suddenly no more changes are being committed while the server is running.

from chrome-devtools-autosave.

Do you use Chrome 17 (stable)? If so, there was a glitch that has been fixed recently. Please update the extension to version 1.1.1 (open chrome://extensions/ and press "Update extensions now" button).

from chrome-devtools-autosave.

This fixed the issue for me. Thanks NV.

from chrome-devtools-autosave.

I'm running into this same issue. I'm using Chrome 17 (stable) and have extension 1.1.2 installed. No changes are saved and nothing shows up in the terminal except: DevTools Autosave 0.3.1 is running on http://127.0.0.1:9104.

from chrome-devtools-autosave.

Same for me since I upgraded, it doesn't work anymore :(

from chrome-devtools-autosave.

Do you see any errors in the following?

1. Background page’s console (how to open)
2. DevTools (how to open)

Which version of Node.js do you use (to see, run node --version in the terminal)?

from chrome-devtools-autosave.

Thanks Nikita. I added /save after the URL and upgraded to Chrome 17 and it works now :)

from chrome-devtools-autosave.

Oh, that explains everything. Since NV/chrome-devtools-autosave-server@96f91b5 the server URL must end with /save.

from chrome-devtools-autosave.

@kyro does it work for you now?

from chrome-devtools-autosave.

Hello! I'm getting a pop up error on the DevTools autosave window that says http://127.0.0.1:9104/save does not responding

from chrome-devtools-autosave.

It means the server is not running. You have to install and run it.

from chrome-devtools-autosave.

I believe I already installed the server. The terminal says DevTools Autosave 0.3.1 is running on http://127.0.0.1:9104

from chrome-devtools-autosave.

What do you seen when you open http://127.0.0.1:9104 in the browser?

from chrome-devtools-autosave.

ok, so I just realized that I have to open up the terminal and run autosave before it can save any changes. If I close the terminal then autosave turns off and its no longer listening. Is this something I'm going to have to do every time or am I missing something?

from chrome-devtools-autosave.

You can do it once; just don’t close it.

Well, you can run autosave as a daemon on system launch using launchd on Mac OS X or /etc/init.d/ on Linux. I don’t do that, I just keep one tab in the terminal dedicated to Autosave.

from chrome-devtools-autosave.

Actually, it’s a good idea to start the server on OS launch. I’ve created NV/chrome-devtools-autosave-server#9.

from chrome-devtools-autosave.

Thanks! You rock!!

from chrome-devtools-autosave.

Closing. Please reopen if something still doesn’t work.

from chrome-devtools-autosave.