404 Error with the Translation Script

**Will.Spencer** · 26 April, 2009, 22:30 PM

It should definitely stay in German.

I've sent this back to development, but Eric's in the middle of a rush project so there may be a delay of up to two weeks.

But on the positive side... pages will get translated and indexed during those two weeks.

**davesnake** · 26 April, 2009, 22:33 PM

No problem, i can still run it and see if there are any traffic benefits in the meantime. Google can still do it's thing.

Getting there, thanks again.

**davesnake** · 26 April, 2009, 22:45 PM

The script is trying to translate my ads, which load in an iframe>php.

php is blocked in htaccess but no luck.

Also the css is not loading on translated pages. Thanks.

**Will.Spencer** · 26 April, 2009, 22:56 PM

Originally Posted by davesnake

The script is trying to translate my ads, which load in an iframe>php.

php is blocked in htaccess but no luck.

Since the ad inclusion is all done server-side, I don't there is a way to stop this.

Originally Posted by davesnake

Also the css is not loading on translated pages.

You also should not be seeing this text on your translated pages:

This page was automatically translated from English. Back to Translate
View original web page or mouse over text to view original language.

**davesnake** · 26 April, 2009, 23:00 PM

Originally Posted by Will.Spencer

You also should not be seeing this text on your translated pages:

This page was automatically translated from English. Back to Translate
View original web page or mouse over text to view original language.

Thats the iframe, in that iframe loads a php file, in that php file is my ad companys JS.

I do it so if their server goes down my page loads dont hang.

The translate script is trying to translate that php page, inside the iframe.

Fixed the css, just told vBulletin not to store them in a file, in Vb options.

Thanks.

**davesnake** · 26 April, 2009, 23:18 PM

Fixed the ads now too, just pointed the iframe to load the php files on another of my domains.

All good to go, nice one! Thanks.

**Will.Spencer** · 26 April, 2009, 23:59 PM

Very smart idea!

**davesnake** · 27 April, 2009, 01:11 AM

Thanks, one other thing, how long is a page cached for, does it get re-cached after x amount of days?

**Will.Spencer** · 27 April, 2009, 01:31 AM

It gets re-cached only if someone -- or something -- accesses it again.

If not updated, cache files are stored forever.

**davesnake** · 27 April, 2009, 13:52 PM

Originally Posted by Will.Spencer

It gets re-cached only if someone -- or something -- accesses it again.

If not updated, cache files are stored forever.

Are you sure? I mean when I had the css and ad errors I had to delete the cache to get the pages to display properly after I fixed the issues.

Also wouldn't that be a huge server/google translate request load, the spider constantly lives on my site, so it would be constantly caching pages on my server and sending translate requests, over and over, even if it just cached the page a few mins ago.

A better option would be to cache on first load (by bot or person) then re-cache on new activity but only if 7 days has passed.

Out of interest how big are the sites you have added this to? I have a site with 20k pages so am a bit concerned adding 200k pages to the domain overnight.

Also did your removed pages ever come back into Google Serps and how long after install did it take to start seeing results?

Thanks, sorry for all the questions.