Important: This page is using cookies (cookies). Using this website without turning off cookies in browser, means that you agree for using it.
Buy Now! Features Downloads

Earn with us!

If you would like to start earning money with vBET join to Affiliate Program.
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: All translations stopped working - all threads are blank when a flag is clicked

  1. #11
    Junior Member
    Join Date
    Jul 2010
    Posts
    27

    Default

    Ok. It would appear to me this is probably why: My adminfunctions_options.php does not have save_settings because I am on vBulletin 3.6.8. vBulletin 3.8.x would have it.

    vBET worked for me before when I was on vBET 3.4.1 which does not use save_settings.

    Now that I upgraded to vBET 3.5.2 and I am running into the problem with save_settings.

    So what do you think we should do?

  2. #12
    Retired ;)
    Join Date
    Aug 2011
    Posts
    441

    Default

    Updating vBulletin to latest version (3.8.7) would solve it

  3. #13
    Junior Member
    Join Date
    Jul 2010
    Posts
    27

    Default

    My vBulletin is highly customized and integrated with other software. Upgrading vBulletin is not an option.

    Is there any other way to make vBET work for me?

  4. #14
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    3,037

    Default

    Yes. You need to made code changes and change calling of save_settings to other function/code which will save the setting. vBulletin 3.6 is not officially supported, but we can do it official in next release (one if checking does function exists). So we will check how in this old version vBulletin saves settings and we will give you hints about code changes. Until then - just please disable vBET.

  5. #15
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    3,037

    Default

    This is NOT TESTED solution. Please check it and confirm does it help. If yes then we will include it in next release. We cannot test because we do not support officially so old version of vBulletin and we do not have testing forum for this one.

    Quick fix:
    1. Open file /includes/vbenterprisetranslator_class_translator.php
    2. Find:
    Code:
    save_settings(array ('vbet_provider_availability_'.$provider => $availability));
    3. Replace by:
    Code:
    if (function_exists('save_settings')) {
    save_settings(array ('vbet_provider_availability_'.$provider => $availability));	
    } else {
    global $vbulletin;
    $vbulletin->db->query_write("
    UPDATE " . TABLE_PREFIX . "setting
    SET value = '" . $vbulletin->db->escape_string($availability) . "'
    WHERE varname = '" . $vbulletin->db->escape_string('vbet_provider_availability_'.$provider) . "'
    ");
    build_options();
    }

  6. #16
    Junior Member
    Join Date
    Jul 2010
    Posts
    27

    Default

    Thanks. With the change the error is gone but it does not translate anymore. Whatever language flag I click it still displays English

  7. #17
    Michał Podbielski (vBET Staff) vBET's Avatar
    Join Date
    Oct 2009
    Posts
    3,037

    Default

    It is not because of the change. This is because you reach your limits in translation providers.
    Please read this for more info: http://www.vbenterprisetranslator.co...html#post10876

  8. #18
    Junior Member
    Join Date
    Jul 2010
    Posts
    27

    Default

    Ok, in which case I will just wait for Google or Microsoft miraculously become available again? Or purchase Google Translate API 2?

  9. #19
    Retired ;)
    Join Date
    Aug 2011
    Posts
    441

    Default

    vBET will automaticaly checked which API is available in every 10 minutes, and switch it on, also if you are sure you didn't reach your limits - f.e. you've translated only one page and nobody else was on forum you could write to microsoft - mtcont@microsoft.com, maybe it appears becouse of Microsoft internal error, but most probably you've just normaly reached your limits
    Also please note that vBET supports Google (paid) translation v2 API and tests new api: Apertium (click for more info)
    Last edited by r.dziadusz; 07-11-11 at 10:15.

  10. #20
    Retired ;)
    Join Date
    Aug 2011
    Posts
    441

    Default

    Do you still need help with this issue? If not I will marked it solved, for any other issue please open new thread

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •