Well be careful what you wish for. The new version of the translator plugin has a load balancing/fail over option so that if the primary translator is unavailable and does not respond in time then the request gets sent to the next translation engine.
That is a very cool option. It also means your webserver gets hit massively by the translation engines. My web traffic went from 5,000 hits (900 visits) last week to 21,000 hits yesterday.
In terms of network traffic that’s not even 100kbs. In terms of application hits (Apache web server) that’s huge. I’ve rolled back the version from 5.01 back to 4.0. I had to load up phpmyadmin and zap the options from the plugin to get 4.0 working again.
The new version has some very cool options. If I can turn off the load balancing and set the error page that comes up to my own page then I’d be set.
I’ll e-mail the author and get it sorted out.
Update: I’ve found the problem. It had nothing to do with ATPP, it was how I configured my logging software.