Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter AlbertGn

    (@albertgn)

    To prevend an error when updating polylang, change the code above into:

    if (function_exists('pll_register_string')) {
      foreach ($bfa_ata as $key=>$str){
        if (in_array($key, $pll_ata_strings)) {
    	if (is_admin())
    	    pll_register_string('atahualpa', stripslashes($str));
    	else
                $bfa_ata[$key] = pll__($str);
        }
      }
    }

    Thanks to Chouby 🙂

    Thread Starter AlbertGn

    (@albertgn)

    Ahhh, briljant…
    My line counter showed a different number from yours (probably because of the $default_option line half way the function), so I put the code just below the $result line instead of above.

    Now my site is showing up the correct bilangual wording for newer and older posts!

    Thanx! Now my Atahualpa site is fully multilingual! (Except that the archive widget is not working in 0.6 )

    BTW one tip: in my first attempt to use your code, the string translation didn’t work – I could not save the changed language values. It turned out that the value in atahualpa contained the “%rarr” value (as string). So change your atahualpa settings first to something without special characters!

    Thread Starter AlbertGn

    (@albertgn)

    Hi Chouby, thanks for the swift reply…

    I entered the code and see the parameters popping up in the string translations tabular, but no impact in the user interface: the string appears and not its translation.

    Am I missing something?

    Thread Starter AlbertGn

    (@albertgn)

    I already thought so (for the hardcoded strings)

    WP 3.3 check, Polylang 0.6 check
    Modifications in theme – I already made a few small ones…

    I know the Atahualpa theme made an addon for WPML – so if we can convince them Polylang is a better option 🙂 So far, I’m impressed.

    I’m ready!

Viewing 4 replies - 1 through 4 (of 4 total)