Kiwitrees on Twitter

    json, seo, locked out, getClientIp, bug reporting, Php 7.1, kiwitrees, dropbox. token, tags, css, users, spam, nickname, Administration, footer, privacy, reports, media_links, white screen, drag, add missing death, custom text, person, edit, administration pages, Fancy imagebar, roadmap, .mo, BAPM, contacts, button, .po, login, timeout, FAQ, latest version, shared note, IE problem, prefix, Require visitor authentication, 1939 Register, Google Maps, danish, upgrade, 3.0.0, server, 2.0, kiwitrees 2.0.2, performance, simpl_grey, 2.0.2, 3.2.3, CHR, add_asso_facts, 3.3.3, release, not married, contact links, IE11, HTML variables


    1679 posts

    But for pages, gallery, and menus I still think the best answer is to create two versions of each item (in the same module), one in Danish and one in American. Then there is no further translation required, and your Google translate on those pages will no longer be needed. But again, your choice. Perhaps I could change one of your “pages” as an example for you?

    Hopefully, when you “thanked” me for that post you meant that I should create the example 🙂 Anyway, I have done that. I used a small one: “Why the best man?”.

    If you visit the “Historic blogs” page, select “Why the best man?” and switch between the two languages. You will see a complete translation for each. (Note – I only used google for the initial translation. The words are not perfect, but much the same as your google translate code would give).
    Now if you visit the admin page for the pages module, you will see there are two “pages” for this item, one in Danish, one in English. If you do the same for the other pages (lots of copy/paste, and some help from google required) then the only user-defined translation you will need is for the page title “Historic blogs”.

    My personal kiwitrees site is