vBET 4.2.1 does not translate vBSEO Javascript messages

[StarBuG]

Hi

I noticed that with vBET 4.2.1 and vBulletin 4.0.2 PL4 and vBSEO 3.5 RC3 Notices get not translated.

Please advice

StarBuG

[vBET]

You have to turn on those translations - it is disabled by default for performance reasons (not every one is using it). You will find appropriate option in vBET -> Misc options

[StarBuG]

Sorry but I am not stupid.

It is on otherwise I would not have reported it as bug!

See Patientenfragen.net - we have the answers

[vBET]

No one assumes that any of our users is stupid It is standard procedure to inform first about configuration possibilities, because user could simply miss some configuration or even not look for such. I'm opening issue again and going there

[vBET]

Indeed it is some bug, because it is even not re-encoded. We will take care about it soon

By the way - did you notice that you have broken layout on top of page for translated view and your flags disappear (are not even in output code)?... I see that you made some manual template changes - please check does it is because of your changes (copy actual template body somewhere; revert; check; put it back).

[StarBuG]

The layout is not broken.

You saw a cached version during a troubleshooting of the APC Cache optimisation plugin

Try now and see if you still see a broken layout plz

ps: The "stupid" part I just said because you simply closed the bug report and moved it without waiting for my reply.
You should wait for the customers response first before declaring active problems solved.
It is impolite otherwise

[StarBuG]

One more note

I would like to disallow: *.js in the robots.txt file

I had that included but removed it for now just in case this was causing the translation problem (which it is not).

However, would that cause troubles with the fixed new version or can I include it into my robots.txt?

[vBET]

One more note

I would like to disallow: *.js in the robots.txt file

I had that included but removed it for now just in case this was causing the translation problem (which it is not).

However, would that cause troubles with the fixed new version or can I include it into my robots.txt?

Are you sure that robots.txt is using * notation...

Anyway content of robots.txt have no impact on vBET.

[StarBuG]

It is not officially supported in the original protocoll but google bot can handle it.
And that is what counts

[vBET]

The layout is not broken.

You saw a cached version during a troubleshooting of the APC Cache optimisation plugin

Try now and see if you still see a broken layout plz

ps: The "stupid" part I just said because you simply closed the bug report and moved it without waiting for my reply.
You should wait for the customers response first before declaring active problems solved.
It is impolite otherwise

Right - now layout is OK.

Also thanks for your suggestion about handling issues. Please note that we always reopen issues if it appears that it is not really solved and that 'closed' is only prefix - thread is not closed - you can still write and tell that issue is not corrected yet. Sorry if you felt uncomfortable because of that.

About not translated vBSEO notices. I have trouble with finding it on your forum. Can you please give me URL to page on which exist such comment (not translated one) and quote me exact original text of this comment. You have different layout and on main page for me it looks that all is translated, so please point me right direction