What's new

usairways.com

OTslave

Advanced
Joined
May 24, 2005
Messages
201
Reaction score
1
Looks like they felt confident enough in the beta site to have it go live. There's no longer a choice.
It's the new site or nothing from my ip address. Unless they're breaking it in slowly by ip ranges.
 
I still get the old with an option to try the new one.
 
They will doing that in 5 hour intervals for a while before they fully launch it. They hide the current site and force everyone to try to use the Beta site. They record data, and relaunch both all the while continuing to improve the Beta.

-Kinglobjaw
 
They will doing that in 5 hour intervals for a while before they fully launch it. They hide the current site and force everyone to try to use the Beta site. They record data, and relaunch both all the while continuing to improve the Beta.

-Kinglobjaw

Any organization that enjoys making money on the web is looking at that technique as a case study in what not to do.

Any organization worth it's salt does not need nor require their customers to be regression test-monkeys.
 
Any organization that enjoys making money on the web is looking at that technique as a case study in what not to do.

Any organization worth it's salt does not need nor require their customers to be regression test-monkeys.



"Surely" you aren't mocking US's "crack IT team".....Or is it "IT team on crack"?
 
i get this when i go to the web page:

Server Error in '/awa' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
 
i get this when i go to the web page:

Server Error in '/awa' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Count your blessings.
 
Any organization that enjoys making money on the web is looking at that technique as a case study in what not to do.

Any organization worth it's salt does not need nor require their customers to be regression test-monkeys.
I would have to disagree. I think it's a good idea to test the functionality of the main method of tickets sales before completely switching over. Work out most of the kinks that are found or reported that way our customers are not left hanging when they would like to purchase a ticket.

Maybe they have learned a lesson from previous IT short comings?
 
i get this when i go to the web page:

Server Error in '/awa' Application.
--------------------------------------------------------------------------------

"Server error in awa application" Oh my, that is just too funny. Pretty much describes IT since the merger, doesn't. Has anything gone right in that area? QIK/SHARES, Nettracer, SCEPTRE, you name it.


"Server Error in '/awa' Application" Oh my, oh, oh my, oh my! :lol:
 
I just checked out the new site for the first time. Same s***. Different furniture. For example:

You still cannot search by fare class, and it's still showing random flights in February as being "sold out." And while I did not go through an entire booking, it appears as if you still cannot request mileage upgrades during the booking process.

VERY unimpressive. :down:
 

Latest posts

Back
Top