Quote:
Originally Posted by Adam B.
iRex's lead developer is out of town, and did not have access to debug this. He was notified by tech support of the problem. Since I was able to find out what the problem was, he could easily fix it on their server. I guess that's one of the perils of being a small company....
|
I think that simply ignoring a problem one cannot immediately fix is incorrect behaviour.
Posting a simple "We are aware of a problem with Shell Access, and will fix it ASAP" would have been professional and courteous, and would have saved many people's time.
Thanks once again to Adam B for the debugging.