Rail Freak
Engineer
Is anyone having Amsnag problems?
dittoNeither one is working for me, even after clearing cache and cookies.
Firstly, that page worked when I clicked on it in the first place, but it gave me that 404 when I clicked on it in my post. From there it seemed pretty self explanatory.That worked!!! How did you figure that out??? (Cpotisch,You Amaze Me, Some Times!)
Thanks. I'm not sure how that happened, because the link that appears in my post is different from the one that seemed to be embedded into it. So that explains why it wasn't working, but not how I managed to change the embedded link to be different from the one I typed. Well, whatever be the reason, it's fixed now, and it's working fine.The link to Amsnag 2.0 that niemi24s included in post #8 worked for me, but the link that cpotisch included in post #4 did not. Each appeared the same in the blue, clickable text of the post, but the actual URLs point to different places. It appears that the target included in cpotish's link has some extraneous characters at the end (specifically, "%A0is.%A0The" following "http://biketrain.x10.mx/amsnag2.0/amSnag.php"),and I assume that is what caused a problem in trying to follow the link.
Glad I could help.
As you said, glad I could help.Well, whatever be the reason, I fixed it, so everything seems to be nice and peachy.
Yeah yeah yeah.Glad I could help.
As you said, glad I could help.Well, whatever be the reason, I fixed it, so everything seems to be nice and peachy.
Warning: file_get_contents(https://tickets.amtrak.com/itd/amtrak?requestor=amtrak.presentation.handler.page.rail.AmtrakRaihTlFareFinderPageHandler&xwdf_TripType=%2FsessionWorkflow%2FproductWorkflow[%40product%3D%27Rail%27]%2FtripRequirements%2FtripType&wdf_TripType=OneWay&xwdf_TripType=%2FsessionWorkflow%2FproductWorkflow[%40product%3D%27Rail%27]%2FtripRequirements%2FtripType&xwdf_origin=%2FsessionWorkflow%2FproductWorkflow[%40product%3D%27Rail%27]%2FtravelSelection%2FjourneySelection[1]%2FdepartLocation%2Fsearch&wdf_origin=mia&xwdf_destination=%2FsessionWorkflow%2FproductWorkflow[%40product%3D%27Rail%27]%2FtravelSelection%2FjourneySelection[1]%2FarriveLocation%2Fsearch&wdf_destination=phl&%2FsessionWorkflow%2FproductWorkflow[%40product%3D%27Rail%27]%2FtripRequirements%2FjourneyRequirements[1]%2FdepartDate.usdate=11/07/2018&%2FsessionWorkflow%2FproductWorkflow[%40product%3D%27Rail%27]%2FtripRequirements%2FjourneyRequirements[1]%2FdepartTime.hourmin=&%2FsessionWorkflow%2FproductW in /home/biketra1/public_html/common/amtrakCommon.php on line 105
Maybe after you did those 352 queries and compiled it, AmSnag decided that it had fulfilled its destiny and could now leave this world.I've had problems with the original AmSnag since shortly after making those 352 queries for the "How Far In Advance To Book?" thread, but it worked beautifully then (4 to 6 Oct). I probably busted it! Sorry, Paul. This is what sometimes displays now after a failed query:
AmSnag Error Message 1.jpg
But have had no problems with amSnag version 2.02.
My guess is that it is something at the biketrain.net hosting service. The backup site at http://biketrain.x10.mx/and the server on my own machine work fine. My suggestion is useSame problems for me using 2.02. It took seven minutes to run a 30-day query for ORL-PHL, then the results was missing fares for six of the 30 days. My guess is that something on the Amtrak end is causing Amsnag issues,
Sorry to see you're moving on to other things, but stuff happens and life goes on.With all the downgrades to LD service, I have sort of lost interest in Amtrak and have moved on to other things.
Same here. Thanks Paul!Sorry to see you're moving on to other things, but stuff happens and life goes on.With all the downgrades to LD service, I have sort of lost interest in Amtrak and have moved on to other things.
Thanks for all your work here over the years.
Best wishes from an avid AmSnag user.
Enter your email address to join: