I've received 15 database errors within the last hour or so...
Needless to say...I've just uninstalled the whole thing...including the database.
I contacted the host...and they said there is no issue with either the forum or the translator database.
Since I cannot modify the file you're referring to...to me...there's no need to further waste your time trying to correct it. Since it's timing out...and I cannot make any changes to the file in question...I can't use this mod.
Thanks, anyway, for the help...
You only get those emails as the first time you translate a BIG page it times mysql out, no error actually occurs, mysql just sends an email warning.
Your forum users notice nothing, at all, it's just an email and once your site is fully translated they go away to a point.
I put up with a few emails in trade of 10k daily uniques. :up:
Yes, things should get interesting in a few more weeks.
I hope you win MOTM. You deserve it. The other nominations are good, but this mod give real results.
Thanks for the great work.
Please add the capability to process Google Translate tags for notranslate in the next release. Thanks so much! We need to add this to our code tags. Cheers.
I've been on holiday and am going here and there again over the next few months, but will work on a new release asap. If anyone has any suggestions leave them here please.
It doesn't make any difference, since my host states this setting cannot be changed on a shared server. It's set by the host admin. Which means this mod is useless on a shared server.
Thanks for the help though, cyc...much appreciated.
Guess I'll have to uninstall this...
What a waste...
Stop! It's working fine. This error is harmless! You can use this mod and it will work fine. After most pages will translate those errors will stop occures.
This error is not of this mod, but vbulettin. At the very end of request vbulletin just want to update date of last session activity - and it cannot because session is timeout. It doesn't affect in any way vbulletin or this mod. So you can just ignore it. Dave was working on this, but it looks that he abandon this issue since it is harmless - still annoying of course
Stop! It's working fine. This error is harmless! You can use this mod and it will work fine. After most pages will translate you those errors will stop occures.
This error is not of this mod, but vbulettin. At the very end of request vbulletin just want to update date of last session activity - and it cannot because session is timeout. It doesn't affect in any way vbulletin or this mod. So you can just ignore it. Dave was working on this, but it looks that he abandon this issue since it is harmless - still annoying of course
I didnt abandon it, it cannot be fixed, BIG fresh pages take time to translate the first time round and mysql gets bored waiting, unless you set the php wait timeout to minutes it cannot be avoided (wgich is bad for security). I dont cmind anyway, it is just a stupid email warning, no error coccus at all and it does not effect the running of the site at all. I just send them to mysql@domain.com and forward them to their own folder in outlook. They can be ignored. As i said i can put up with them for 10k uniques a day, others reported 20k new uniques a day, so i guess they can put up with them also.
I didnt abandon it, it cannot be fixed, BIG fresh pages take time to translate the first time round and mysql gets bored waiting, unless you set the php wait timeout to minutes it cannot be avoided (wgich is bad for security). I dont cmind anyway, it is just a stupid email warning, no error coccus at all and it does not effect the running of the site at all. I just send them to mysql@domain.com and forward them to their own folder in outlook. They can be ignored. As i said i can put up with them for 10k uniques a day, others reported 20k new uniques a day, so i guess they can put up with them also.
I'm not so sure does it cannot be avoided. Just speculate. But if look into vBulletin source code you can find where exactly session is updated and check does there is a hook which can work after it.
Another possible solution (potentially easier) you already have in your mod - I was working on cache in this mod and have to fight with same problem. If translation takes too long then also connection to vBGT DB was lost. So I just reconnect. Did you try to reestablish connection to vBulletin database at the end of translation?...