Dennis Ploetner

Hi,

Short answer: no, multilingual is not a confirmed feature for 7.2. As far as I can see, it is still where you found it, Phase 4 without a timeline. Also keep in mind that the roadmap is only partly delivered. Real-time collaboration was deferred again and did not make it into 7.1. So I would not expect much from Phase 4 based on dates.

My own view: Core will come with a solution at some point, and I expect it to be a foundation (data model, language and translation relations, routing) and not a finished translation product. That would complement MSLS rather than replace it, because MSLS could then build on a standard instead of inventing its own. Long term I still see Multisite in a good position, since one site per language already gives you clean separation of content, users, plugins and caching.

This is my reading, not inside knowledge. I have not seen any signs yet that Phase 4 work has started. I would be interested in that discussion, also because I am involved as a maintainer of the Multisite component in Core.

Yes, it looks a bit misaligned. The idea here is to show that this is a sub of a submenu. I’look for a better way to emphasize this. Thanks for pointing it out.

MSLS uses lots of the WordPress API functions. So this bug has its roots in WordPress core:

If you look into the WordPress core -> http://github.com/WordPress/wordpress-develop/blob/6.9/src/wp-admin/includes/ms.php#L633-L673, it just prints English in case it is different from American or British English. But this not the whole problem. It creates an array with keys (en_US, en_GB, and en). To visualize what I mean:

$output = array(
    'en_US' => 'American English',
    'en_GB' => 'British English',
    'en'    => 'English',
);

This means it would work for 3 English websites but fails from with 4. The connections should work in any other case. I had similar setups with lots of languages.

• This reply was modified 7 months, 2 weeks ago by Dennis Ploetner.

Great news! Thanks.

Thank you so much! 🙂

Yes, indeed. Seems my screenshot is not going up. This markup here seems not to come from MSLS:

<div class="ast-builder-language-switcher-wrapper ast-builder-language-switcher-layout-horizontal">
    <div class="ast-builder-language-switcher-element">
        <nav class="ast-builder-language-switcher" aria-label="Language Switcher">
            <ul class="ast-builder-language-switcher-menu">
                <li class="ast-builder-language-switcher-menu-item-header">
                    <a href="/" aria-label="English" role="link" class="ast-builder-language-switcher-item">
                        <span class="ast-lswitcher-item-header">
                            <span class="ahfb-svg-iconset ast-inline-flex svg-baseline">
                                <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 60 30">
                                    <clipPath id="a"><path d="M0 0v30h60V0z" /></clipPath>
                                    <clipPath id="b"><path d="M30 15h30v15zv15H0zH0V0zV0h30z" /></clipPath>
                                    <g clip-path="url(#a)"><path d="M0 0v30h60V0z" fill="#012169" />
                                        <path d="M0 0l60 30m0-30L0 30" stroke="#fff" stroke-width="6" />
                                        <path d="M0 0l60 30m0-30L0 30" clip-path="url(#b)" stroke="#C8102E" stroke-width="4" />
                                        <path d="M30 0v30M0 15h60" stroke="#fff" stroke-width="10" />
                                        <path d="M30 0v30M0 15h60" stroke="#C8102E" stroke-width="6" />
                                    </g>
                                </svg>
                            </span>													
                        </span>
                    </a>
                </li>
                <li class="ast-builder-language-switcher-menu-item-header">
                    <a href="" aria-label="German" role="button" class="ast-builder-language-switcher-item">
                        <span class="ast-lswitcher-item-header">
                            <span class="ahfb-svg-iconset ast-inline-flex svg-baseline">
                                <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 5 3">
                                    Flag of Germany
                                    <rect id="black_stripe" width="5" height="3" y="0" x="0" fill="#000" />
                                    <rect id="red_stripe" width="5" height="2" y="1" x="0" fill="#D00" />
                                    <rect id="gold_stripe" width="5" height="1" y="2" x="0" fill="#FFCE00" />
                                </svg>
                            </span>
                        </span>
                    </a>
                </li>
            </ul>
        </nav>
    </div>
</div>

OK, now just use the language-switcher coming from Multisite Language Switcher. The one you have comes from TranslatePress, as far as I can see. 😉

Hi Becki,

thanks a lot for your kind words and for using the plugin!

You’re right — the language flags should not just point to the start page of each site. If the pages (or posts) are correctly connected in the MSLS settings, then the German flag on /contact should indeed lead to /de/kontakt, and so on.

I’ve just moved the demo site msls.co to a new provider and finished setting it up, so now the demo should show the correct behavior. Could you please have another look there?

If your flags still link only to the main site (like /de/), then usually one of these things is happening:

• The pages aren’t actually connected yet in the MSLS meta box.
• Caching (object cache or page cache) is showing outdated links.

Can you double-check if the correct connections show up in the page editor under “Multisite Language Switcher”? If they do, and the problem still persists, please let me know — a link to your site would help me understand better.

Thanks again for reporting this and for your feedback!

Best,
Dennis