MORE BUGS - You drive me mad.

[vBET]

Please note that vBET 3.5.0 is in BETA STAGE and it is clearly described in download section:

Download Latest BETA (unstable) Version for vBulletin 3.x - vBET 3.5.0

It is clearly described that this version is unstable - everyone uses BETA version on it's own risk and he is aware that it is unstable.

BETA version is normal part of each software development - vBulletin and other mods also are released in beta version.

In case of issues - just notify it to us so we can solve it and if it is critical go back to latest stable version which is still available in download section

[basketmen]

Its a waste of time anyway, the MS limit is 4m chars a month.

When i enabled v2 google i used 4m chars in about 15 mins.

Even if i wanted to pay $1000 for 50m chars (max per month) from Google, id use them in days.

This MOD is dead, unless VBET can find a free way for it to continue.

As I said we are working on ideas that could help us improve our product every day, Is the problem still existing?

Here's what I think.

MS limit has been reached already.

So...

What solution is there now? I have no way to translate do i!

If you are sure you are blocked by google (if not you can do tet from here: http://www.vbenterprisetranslator.co....html#post1728) you can write to them to reaccess your IP(it is also said in post i gave you), if you will be using not " only google" so mainly microsoft API you will reach your limits slower

Also, please remember that vbet cannot change google/MS limits, right now we provide also google api v2 for comercial users, but we are searching for other way of translating

So what happens when Google turn off v1 API?

Then what is the solution?

This is not a long term fix, is it.

I want to share my alternative solution

I think this mod will never be dead, and will be go forward because of its basic potential : larger our forum, traffic and revenue, and as long vbulletin still used as first choice for forum software. There will be always solution, and you always not be alone

i am suggesting again my feature request here :

Manual editing other language translation result/cache, by admin

its no need engine translation out there at all (so not breaking anyone tos or limitation), just manually translation by human, unlimited, safe, and the best translation result, depending on how much the person translating abillity. Admin/staff/moderators/members can participating to help manual translation







actually since still not giving this feature requested last year yet in above thread, me and one of my staff already done this for some post, about 20.000 post in few months are added manual translate, its works together with the google translate in the post. Its not perfect methode, but i am satisfied enough with it, and everyone understand the translation result, until the feature request above are given


So i am just edit the post, by admin/staff, because they can edit anyone post, and add this below the original post, (remove the space after /notranslate, and /quote) to make it work in your own post


[quote]
This is manual translate text (or manual translate information image)
[notranslate]
Your manual translate text here
[/notranslate ]
[/quote ]



the result are like this










because the experiment and experience until now, my staff got little tricks too, to make the manual translation a lot faster, even i am not realized it before, so no problem for manual translation speed for me, if this feature request can given

[vBET]

Hi. I just read whole thread from the beginning and also got some more info about the issue.

Google Translation API v1 is preparing to be closed, so they put more restrictions what is not surprising - this was announced months ago.

Deleting whole your cache was not smart idea. You can complain now that it will be expensive for you to gor translations (which you already had for free) but it is pointless - it is Google Translation API v2 who charges you not us. Please point your complains to Google. Here we can only tell you that we noticed your opinion and we have no impact in this area.

Please use Microsoft tester to determine what is it something wrong with your Microsoft connection. If not then please send access details just as Radek asked you before so we will be able to check what is going on.

We will gladly add any other translation API which Terms Of Service allows for that. vBET is already prepared to easily add new translation providers. Please point any one which you want to be supported in vBET

Please tell do you steel need any help in this area? If the product is already uninstalled then I assume that there is no more need help in this area - right?

[Snake]

So how do you plan to service NEW customers Michael?

How are they ment to translate BIG new forums from scratch.

Your software is now useless, unless you wake up and find a way for people to use it.

Honestly i dont care, i can take it or leave it.

It is you that no longer has a business.

[vBET]

Same way as until now. vBET from very beginning provides translations from external translation provider. Now we can support many providers - so we service our customers even better than before.
Anyone using vBET is aware about external translation providers and he knows that he has to be able to use those services. It is included in vBET License - we are clear about it.

Who are they? And why are you asking me about others decisions? If you are asking me about hints for such forums here are some:
1. Add to vBET ignored pages as many content as you think is not important for translations
2. Use free translation services first
3. To avoid reaching free translations limit too fast - limit supported languages. Add new ones from time to time when your cache is full.
4. Even if you are using paid translations - limit supported languages to those which you think are most important for your forum. And even then limit it more - after time you can add more languages if you find that costs are OK for you.
5. If you are not using Google Translation API v1 - do not clear your database cache and disable automatic cleaning, or at least change cache time to live to much longer (avoid paying for same translations)
6. Avoid translation of SPAM, by verifying posts until those are published.
7. Look for other translation services which Terms Of Service allows to add it into vBET and let us know about those - we will gladly support as many translation APIs as possible
Those are several hints which came to me right now.

Our software does still the same thing as before (and even better) so it is very useful. It can be more expensive, but it is as useful as it was before and even more, because we add new features

Do you need more help in this thread?

[vBET]

No answer - assumed that no more help is needed here. In case if it is - please write here, we will change status to Open again.