• The thing created database tables to house it’s translations and sucked resources so bad it crashed by server. As a result, my host temporarily closed my account down. It took many hours to delete all the garbage created by this “plugin”. If you are looking for something to hose your website, activate this crud. Whatever you do, do not activate the box which says house data locally.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Your post has no relevance on the Global Translator plugin. There is no “house data locally” option. Perhaps you have this plugin confused for another?

    Thread Starter stephenrblv

    (@stephenrblv)

    There seems to be some confusion as to what exactly crashed my server (Bluehost). The plugin has a default caching feature. What was happening is any type of change on my blog like a new post etc, forced a rebuild of this cache. The old translated pages stayed and a new one built ontop of it. The DB crashed from the overload, and my host and google cpus went haywire. I have a hunch even adsense was causing this thing to rebuild pages. Times all this by 30,40 languages and you can see the problem. Whatever was happening it happened to at least 10 blogs I had it installed on.

    this plugin does not have a DB caching sys
    that feature is only in the pay GT pro plugin

    the free one does desk caching
    now if thats what your talking about i cant see how its GTs fault when some other plugin made GT act like that.

    you may want to list any other plugins you had running when this happened

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: Global Translator] Plugin Crashed My Server’ is closed to new replies.