WPGlobus & Parallax One

  • Resolved diego.caccavo

    (@diegocaccavo)


    9 years, 5 months ago

    Hi,
    I have installed this great plugin in my WP site – which uses the free theme “Parallax One” (https://themeisle.com/themes/parallax-one/)- and with the aid of WPGlobus Translate Options I managed to translate most of it.

    I have run into two problems:
    1. The dropdown menu did not work in the mobile browsers (i.e. on smartphones, tablets and so forth).

      I solved this manually editing the class-wpglobus.php (in plugins\wpglobus\includes\) setting $parent_item_ID = 0; on line 1811. This excludes the dropdown menu and shows the flags on the same line.

    However a “developers side” solution would be much appreciated

    2. The tags {:lang}Text{:} do not work in the boxes of “Service Section”, “Team Section” and so forth. If they are included the boxes disappear from the website. Is there any solution?

    Thanks.
    Diego

    https://www.ads-software.com/plugins/wpglobus/

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

  • @diego.caccavo

    Hi Diego,

    The one-line menu and some other useful options appear in the WPGlobus Plus premium extension.

    As for the Service Section – we do not know this theme. If you find the reason and it lies in WPGlobus code, please let us know, and we’ll be happy to fix. You can send a pull request on Github: https://github.com/WPGlobus

    Thank you!

    P.S. Have you tried the configuration file?
    https://www.wpglobus.com/documentation/wpglobus-configuration-file/

    Thread Starter diego.caccavo

    (@diegocaccavo)

    Hi Gregory,

    1. I didn’t mind the dropdown menu, I had to go for the one-line menu just to make it work on all the devices.
    I guess that this is a bug and not a whim and, as bug, it should be fixed.

    2. I had a look in the “WPGlobus Configuration File”: It seems that I don’t need it since the culprit fields are already present in the “WPGlobus Translate Options”. What I noted is that they are imported in this way in “theme_mods_Parallax-One[parallax_one_services_content]”:

    ?

    [{"icon_value":"No Icon","text":"{:it}Ita Text{:}{:en}En Text{:}","link":"\/hydrogel","image_url":"http:\/\/mysite.it\/wp-content\/uploads\/2015\/10\/picture.jpg","choice":"parallax_image","title":"{:it}Ita Title{:}{:en}En Title{:}","id":"parallax_one_560bb6b329de4"},{"icon_value":"icon-social-blogger","text":"test2","link":"test2","image_url":"","choice":"parallax_icon","title":"Test2","id":"parallax_one_5618acbc79bd2"}]
    ?

    Could this generate the problem?

    Thanks you.
    Diego

    Hello Diego,

    We know about the mobile inconvenience (need to hold and then choose) and already have a solution suggested by another WPGlobus user. Working on that (takes time to check on all devices).

    The piece of JSON from Parallax looks valid – but if they keep it this exact way in the options table then yes, WPGlobus won’t know what to do and probably will keep only the first pair of {:} brackets discovered.

    There is a solution, of course – do not tell WPGlobus to process this as a regular “option” and then add filters in the code before outputting.

    Thank you!
    Gregory

    P.S. It’s Thanksgiving long weekend in Canada. I will be back on Tuesday.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WPGlobus & Parallax One’ is closed to new replies.