I am not at the server or even in the same state, so all I got was a message that Safari cannot find the server.
Safari can’t open the page “http://www.playhousecomedy.com/” because the server where this page is located isn’t responding. On Jun 22, 2010, at 7:51 PM, Chuck Hill wrote: > What error message do you get from the URL that does not work? > > > On Jun 22, 2010, at 4:48 PM, Andrew R. Kinnie wrote: > >> All I did was have her: >> >> 1. copy the existing database (it's Openbase) >> 2. change the name of the existing .woa >> 3. drop the new one into the same place >> 4. bounced the app in Monitor >> It didn't run. >> 5. change one table from the old name to the new name (user to person) . . . >> I had forgotten to do that. >> It claimed that it ran, then threw an exception (still looking for "user") >> then quit. >> 6. bounced the database in Openbase. >> Still didn't run. >> I then deleted the new .woa and the zipped version, and renamed the old ones >> to the correct name. >> The old app ran and she could access it via the link. No one can from the >> outside. >> >> The url on the server is >> http://her-computer-name.local/cgi-bin/WebObjects/PlayhouseComedy.woa/1 >> >> This works on her machine. It points to (via dynamic dns) a zoneedit >> domain. playhousecomedy.com is the domain. >> >> This machine has been serving this site in this configuration for years, and >> I didn't create it and have never had to touch it. I did at one point >> update WO to 5.4.3 and previously dropped in updated .woas (but not since >> I've gone to eclipse and WOLips) >> >> She's running Tiger client, and would be willing to have me SSH in . . . if >> I knew how to open that up. >> >> >> On Jun 22, 2010, at 7:18 PM, Chuck Hill wrote: >> >>> >>> On Jun 22, 2010, at 4:03 PM, Andrew R. Kinnie wrote: >>> >>>> So I made the terrible mistake of trying to deploy the new version of my >>>> site, complete with migrations and D2W and it failed to do anything (not >>>> quite true, it actually runs but immediately threw a JDBC exception). I >>>> then tried to redeploy the old version while I figured this out. >>>> (basically, I re-named the old .woa then renamed it back after the failed >>>> deploy, then bounced the app in Monitor.) >>>> >>>> The old app runs on the server. She can click the link to load it, run >>>> it, do what she needs to do, etc. However, the outside world can't access >>>> it. No configuration files whatsoever were changed. >>>> >>>> Anyone have any ideas what could cause the app to run and be usable on the >>>> server, by a user of the server, but not by the outside world? With no >>>> changes to the apache files or anything else? >>> >>> >>> Something changed. Did you upgrade OS X? What URL works? What URL does >>> not? What error message do you get from the one that does not work? >>> >>> >>> Chuck >>> >>> -- >>> Chuck Hill Senior Consultant / VP Development >>> >>> Practical WebObjects - for developers who want to increase their overall >>> knowledge of WebObjects or who are trying to solve specific problems. >>> http://www.global-village.net/products/practical_webobjects >>> >>> >>> >>> >>> >>> >>> >> > > -- > Chuck Hill Senior Consultant / VP Development > > Practical WebObjects - for developers who want to increase their overall > knowledge of WebObjects or who are trying to solve specific problems. > http://www.global-village.net/products/practical_webobjects > > > > > > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
