Good translation but awkward usability

  • Various settings (like Regex changes) don’t take effect until you fiddle about with other settings. e.g. adding or removing languages.

    Positioning the language choosing menu is fiddly if you use their recommended ?<div id=”weglot_here”></div> to place the weglot menu. Previously in v3.9.2, doing this disabled the default menu (glued to the edge of the viewport). But now you have to hide that manually using css or you end up with two language menus. So that means the awkwardness of adding a separate class to any page using <div id=”weglot_here”></div>.

    Update: turns out that there was a glitch in my visual editor account causing the strange menu behaviour. My very patient support person eventually sorted that out once we figured out the cause.

    Nevertheless, these (and other awkwardnesses) still mean you should allow much time to mess around. There seem to be two remaining bugs, so 4 stars seem reasonable.

  • The topic ‘Good translation but awkward usability’ is closed to new replies.