Aaaah... I understand now. When I was starting the day before, I was starting it from the directory where I unzipped the files, which made the modules directory correct, relative to where I ran the file from.
The config says the directories are "relative to this config file", but that's not really true. They are actually relative to wherever the script is run from. It only worked the night before because I happened to still be in the original unzipped file folder :) Now that I've solved that, and also set modules/conf/javascript.js path relative to where it is getting run from, everything is working again. Yay me! On Thu, Jul 21, 2011 at 4:08 PM, Michael "Kato" Wulf <[email protected]>wrote: > Ah, no, sorry, the output has in fact changed now: > > Running test : Init > Running test : Loading Client > Running test : Loading config > Config values are : > identifier : ape > init : true > frequency : 0 > scripts : > http://wordspot.org/tests/ape/Source/mootools-core.js,http://wordspot.org/tests/ape/Source/Core/APE.js,http://wordspot.org/tests/ape/Source/Core/Events.js,http://wordspot.org/tests/ape/Source/Core/Core.js,http://wordspot.org/tests/ape/Source/Pipe/Pipe.js,http://wordspot.org/tests/ape/Source/Pipe/PipeProxy.js,http://wordspot.org/tests/ape/Source/Pipe/PipeMulti.js,http://wordspot.org/tests/ape/Source/Pipe/PipeSingle.js,http://wordspot.org/tests/ape/Source/Request/Request.js,http://wordspot.org/tests/ape/Source/Request/Request.Stack.js,http://wordspot.org/tests/ape/Source/Request/Request.CycledStack.js,http://wordspot.org/tests/ape/Source/Transport/Transport.longPolling.js,http://wordspot.org/tests/ape/Source/Transport/Transport.SSE.js,http://wordspot.org/tests/ape/Source/Transport/Transport.XHRStreaming.js,http://wordspot.org/tests/ape/Source/Transport/Transport.JSONP.js,http://wordspot.org/tests/ape/Source/Transport/Transport.WebSocket.js,http://wordspot.org/tests/ape/Source/Core/Utility.js,http://wordspot.org/tests/ape/Source/Core/JSON.js > baseUrl : http://wordspot.org/tests/ape > domain : auto > server : ape.wordspot.org:80 > Running test : Setting document.domain > Running test : Checking APE.Config.baseUrl > APE JSF Version 1.0 > Running test : Contacting APE Server > Connection etablished but something went wrong. Server response is > * > [{"time":"1311289590","raw":"ERR","data":{"code":"003","value":"BAD_CMD"}}] > * > Something went wrong. If you can't fix it by yourself post a message on the > newsgroups <http://groups.google.com/group/ape-project/> with the output > below or join our IRC channel > > > > On Thu, Jul 21, 2011 at 3:58 PM, Michael "Kato" Wulf > <[email protected]>wrote: > >> However, today I've come back and can't even get it to work on the server >> : ( No change in settings, same error. The only thing that's happened since >> then is I stopped the process and restarted it again today. >> >> -- Michael Wulf 775-235-8398 web site <http://www.michaelwulf.com> | contact<http://www.michaelwulf.com/blog/chat-with-wulf> -- You received this message because you are subscribed to the Google Groups "APE Project" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ape-project?hl=en --- APE Project (Ajax Push Engine) Official website : http://www.ape-project.org/ Git Hub : http://github.com/APE-Project/
