Comments on: WordPress Plugins NOT To Install

By: John Burton

John Burton — Mon, 08 Dec 2008 11:09:18 +0000

Angsuman’s Translator Plugin pro is such a mess. The whole plugin is down now as Google and Yahoo as started banning this plugin and don’t allow translations any more. Huge server overload and much translational errors. I filed support requests for more than a month but not yet got any response. The total company is a fraud and just taking money for bluff. No organization here, only some blogs and cheat plugins. If you see their forums you will find hundreds of people are unsatisfied and still unattended.

Don’t buy it to get yourself fooled.

For your Information, Google is banning blogs using this Angsuman’s Translator Plugin, since it sends automated queries to Google at a huge rate and thats a violation to Google’s webmasters guidelines.

By: John Burton

John Burton — Mon, 08 Dec 2008 11:09:00 +0000

Don’t buy it to get yourself fooled.

By: Everton

Everton — Tue, 20 Mar 2007 09:07:59 +0000

the problems with angsuman’s plugin seem to be quite common. Although I’ve got my version running a bit better, it’s the first plugin I turn off when my server gets busy.
It also suffers from Google blocking sites that do a lot of translations, although that’s not Angsuman’s fault but it is annoying when it happens to something you’ve paid for.

By: Raymond.CC

Raymond.CC — Tue, 20 Mar 2007 06:34:05 +0000

Angsumanâ€™s Translator Plugin Pro has caused my webserver to crash few times a day. I’ve emailed Angsuman and still waiting for respond. Hopefully will fix the high load problem so I can continue to use this plugin.

By: Ajay

Ajay — Tue, 13 Mar 2007 14:24:27 +0000

I’ve had a similar experience ferenc. It increased the load on my server and I was forced to put WP-Cache. I’ve been informed that they are working on 5.0. I don’t think I will be enabling it before that.

By: ferenc

ferenc — Tue, 13 Mar 2007 12:09:00 +0000

A TRULY NEGATIVE EXPERIENCE!!! WORST $30 EVER SPENT!!! … some languages do not work at all.
in my case ( http://ferenc.biz ) Arabic and Norwegian does not work – so they were removed.

so much trouble with Google translation that I had to switch over to BabelFish due to getting a 403 Forbidden error for all translated pages from Google.
Google viewed my frequent translation requests as spam but setting the Translator Cache to 12 hrs still has not fixed the issue.

the plugin is $30 per blog!!!! PER BLOG!!! BE AWARE!!!!
additional plugins are $25.

the next version will include up to 32 languages per the manufacturer – http://blog.taragana.com – but that just sounds like more headache.

I think they are pushing a product which is NOT finished and NOT ready to be released yet.

a japanese friend of mine laughed her ass off at the translation. it is not even close to conversational level not to mention professional.

I have been feeling like a spammer generating this sea of garbage content just to increase the size of my blog.
for now I am removing it completely from my site until it becomes more reliable … not holding my breath.

By: Everton

Everton — Mon, 01 Jan 2007 14:31:38 +0000

Angsuman – just spotted you’ve registered.

Be careful enabling Object cache. Matthew turned it off at the weekend as it wasn’t working well with APC:

http://www.connectedinternet.co.uk/2006/12/31/1260/

Good luck!

By: Everton Blair

Everton Blair — Sat, 30 Dec 2006 19:14:58 +0000

Angsuman – register on my blog and my blog and I’ll give you temporary admin access. If you get it working can you put it in the sidebar where the current translator is please.

By: Angsuman Chakraborty

Angsuman Chakraborty — Sat, 30 Dec 2006 17:27:57 +0000

We used low end Intel Pentium (1.8 Ghz) running Fedora Core 4 and the Translator plugin in cache mode. The pages were not cached initially. If that is not good performance I don’t know what is.

That’s why we are assured that we can make it work for you (free support). If we cannot I would happily and immediately refund you.

By: Angsuman Chakraborty

Angsuman Chakraborty — Sat, 30 Dec 2006 17:26:50 +0000

In our tests we could repeatedly run 50 simultaneous full site crawl on a big website with over 20,000 pages (copy of my blog) without delay with only 512 MB RAM. Cont…

By: Everton Blair

Everton Blair — Sat, 30 Dec 2006 16:27:33 +0000

Given that I did have problems literally the second I installed your plugin, can you explain why you won’t refund my $30 even though I’ve asked on numerous occasions?

By: Angsuman Chakraborty

Angsuman Chakraborty — Sat, 30 Dec 2006 16:20:00 +0000

Global translator, which is based on my original translator plugin, doesn’t provide any caching and doesn’t support 14 languages which we do, not to mention our quality. Also it doesn’t provide even a fraction of the features we provide. We also fully support our product and ensure that it works perfectly on every site. Unfortunately you didn’t give us any opportunity to do so for you so far as I also stated before.

I accept that you faced problems. However you didn’t respond to my email suggesting you how you can solve the problem. Nor did you give us any chance to debug and solve it for you. Even now we are looking forward to make it working for you as we have done it for several hundreds of other sites. Please give us the opportunity to make it a success for you.

By: Angsuman Chakraborty

Angsuman Chakraborty — Sat, 30 Dec 2006 16:18:00 +0000

We did extensive testing with the WordPress object cache to identify performance bottlenecks, if any. We couldn’t find any inherent problem.
It can cause performance penalty only when the memory is low and too many Apache processes are allowed. With caching enabled each Apache process (or Thread), serving a WordPress page request, caches at most 125 php objects (we only contribute one of them) which can increase memory consumption.
As a result kswapd (swap manager) comes into play and at high loads it tends to swap too often and ends up consuming most of the CPU cycles itself instead of allowing actual processing.
So if you are on a low end machine with low RAM or if you are sharing the machine with lots of other users then you can experience performance issues. However you can easily solve it by either increasing the memory or reducing the maximum number of Apache processes you serve.

By: Angsuman Chakraborty

Angsuman Chakraborty — Sat, 30 Dec 2006 16:14:00 +0000

Translator plugin Pro uses dual caching to speed up your access time. The first level cache doesn’t use the WordPress object cache and will improve your performance even with standard caching disabled. The second level cache uses WordPress Object cache. This allows us to serve your translated pages much much faster.

By: Jerry

Jerry — Mon, 04 Dec 2006 16:55:00 +0000

software and scripts from Angsuman are what i personally call “crapware”. it was no big surprise that one of his plugins was on your list of troubled plugins.

By: Everton Blair

Everton Blair — Mon, 04 Dec 2006 13:00:00 +0000

What’s the link for the ajax version?

By: Stefan

Stefan — Mon, 04 Dec 2006 10:39:00 +0000

@Everton Blair: If your are singing the praises of my plugin try my ajax-version and we both will be happy
Sincerely Stefan

By: Everton Blair

Everton Blair — Sat, 02 Dec 2006 18:46:26 +0000

I can’t account for the pingbacks Stefan, but the problem wasn’t my caching. The problem was that because each page load was unique when my site was busy because of the readers post plugin, it was neutralising the caches.

If you read my other posts I was recently singing the praises of your plugin. the problem is that is doesn’t work will with sites that are getting a lot of traffic, where caching is essential.

By: Everton Blair

Everton Blair — Sat, 02 Dec 2006 18:46:00 +0000

If you read my other posts I was recently singing the praises of your plugin. the problem is that is doesn’t work will with sites that are getting a lot of traffic, where caching is essential.

By: Stefan

Stefan — Sat, 02 Dec 2006 16:38:17 +0000

Hello,

I think it is a little unfair to set Readers_Post on this list. First your problems have something to do with your kind of caching and not with the plugin. Second you could mail with my to solve the problem. It’s not the best thing to get to know about your marking my plugin by pingbacks from other foreign blogs, but not from you. Third have a try with my ajax version of showing the latest read post and your caching problem is solved at all.

Best regards
Stefan

By: Stefan

Stefan — Sat, 02 Dec 2006 16:38:00 +0000

Hello,

Best regards
Stefan

By: Viper007Bond

Viper007Bond — Fri, 01 Dec 2006 15:54:11 +0000

Nothing wrong with Gravatars, if you use the right plugin. The ones the locally cache the Gravatars and check daily or so give your users (and gravatar.com) a break.

Or if you don’t like your server doing the work, use the official plugin and make it purely a user/gravatar.com issue (simple tag on your site).

By: Viper007Bond

Viper007Bond — Fri, 01 Dec 2006 15:54:00 +0000

Nothing wrong with Gravatars, if you use the right plugin. The ones the locally cache the Gravatars and check daily or so give your users (and gravatar.com) a break.

Or if you don’t like your server doing the work, use the official plugin and make it purely a user/gravatar.com issue (simple tag on your site).

By: Everton Blair

Everton Blair — Fri, 01 Dec 2006 14:05:24 +0000

I use the addicted to live search plugin which doesn't cause a problem on my blog, but you're right the Ajaxy stuff usually causes problems.

By: Hans

Hans — Fri, 01 Dec 2006 13:49:30 +0000

I would say things like Live stuffs that use much AJAX like on most K2 installation, the Live search. Now it even comes like a plugins that would allow you to have a LiveSearchBox.

By: Everton Blair

Everton Blair — Fri, 01 Dec 2006 07:15:06 +0000

whatdoyaknow – which ones have you had problems with? I’m hoping this thread will become a ‘Name&Shame’ list

By: whatdoyaknow

whatdoyaknow — Fri, 01 Dec 2006 01:17:22 +0000

I run a couple of blogs (some alone, some with friends) and I’ve had some WordPress plug-ins screw things up big time. One time it resent all of the user accounts, to the point where I had to go into the database and re-enter the info. Good job with the info, hopefully it can save some headaches.