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.
Comments by Jan Dembowski
New Life for old 3D Printers
I'm a little late in replying but that print surface? ...
This is not a Gutenberg Review, It’s a Blog Post
Oh, as someone who supports WordPress users in the forums ...
This is not a Gutenberg Review, It’s a Blog Post
That's fantastic. ;) The Classic Editor and at least one ...
This is not a Gutenberg Review, It’s a Blog Post
The blockquote tag works in the HTML comments here if ...
This is not a Gutenberg Review, It’s a Blog Post
It's not about popular belief. And WordPress is 100% open-source ...