I tried to Install the 2.0 version and I was able to show the flags on the site without crashing. Also the db tables are being filled correctly ( both source and translation ) but after I click on 1 flag I still get the message below
--------------------------------------------------------------------------------------
Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
* Please contact the website owners to inform them of this problem.
--------------------------------------------------------
Im not sure whether to bother, is there any harm in adding it Dave? Thanks :up:
I've been using scripts like this one years. Google will not ban your site, de-index you, penalize you or anything else.
At worst they may block your IP from the translate APi for 24hrs, they used to do this on their translate website but I have NEVER had it happen with the API, that may change.
Seriously, Google bans scraper sites, sites using only rss feeds and other autogenerated shit. It does not ban quality sites with good content be it in english or auto translated.
You certainly can't be hurting anything by including an API key.
Here's another question... How about displaying flags based on where the IP is from? I understand this would involve a small index of IP's, but perhaps it could be an exclusion. For example, 'if not from US, display flags'
edit - nevermind - that would be a very large index either way that would have to be referenced on every visit, which sounds very expensive
ok i left it installed overnight and i checked the mysql tables and this is what it looks like
still not loading anything in the cache table. and when i click any flags, nothing is loading for me. any ideas?
The wt_cache hold very long phrases, so if your pages are all full of short words it wont fill up. Try translating a thread with an article or something in it.
Either way if some of them are filling up then caching is working as far as i can see, is there an actual problem you are having?
Well I installed the new version 2.0 script yesterday.
My forum currently has 4,745 threads and 17,052 posts and today my DB looks like this:
34.7MB in 24 hours ?!!?!? I'll let you know how big this DB gets after a week.....
Cheers, and thanks for the great script!
Regards,
Gerald.
Skeptical and no reply needed as it is strictly IMO however a friendly warning... large databases equal more hassle to restore (tell me your backing up people ) and some host have limits on DB sizes so be sure to check and see if your host does (including the fine print) otherwise good concept but tagged for now until I see more .