jimlongo

Okay.

Then the setting Locale at front-end does not do what I need it to?

I need the URL to be https://local.dev/en-us/foo/ NOT https://local.dev/us/foo/

How can I accomplish that?

Thank you.

Following your last direction on my local install, I was able to change the Locale at front-end settings to en-us, etc.,

This outputs the following to the browser . . .
<link hreflang=”en-us” href=”https://local.dev/us/&#8221; rel=”alternate” />
<link hreflang=”en-ca” href=”https://local.dev/ca/&#8221; rel=”alternate” />
<link hreflang=”fr-ca” href=”https://local.dev/fr/&#8221; rel=”alternate” />
<link hreflang=”en-au” href=”https://local.dev/au/&#8221; rel=”alternate” />
<link hreflang=”x-default” href=”https://local.dev/us/&#8221; rel=”alternate” />

However the URLs are still like this
https://local.dev/us/foo/

I can’t post it here at this time, can you email jimlongo56 at gmail and I’ll send it to you.

Yes thank you.

I also had tried that, but again any settings I put there get lost when I navigate away from that page and come back to it

Do you mean that you wish to have
<option value=”taste” >[:en]To Taste[:fr]French text[:]</option>
and LSB will show one of the texts? This is “‘encode’:’display'” in the new integration capabilities: https://qtranslatexteam.wordpress.com/integration/ (latest version on GitHub).

Thanks, I found that putting [:en]To Taste[:fr]French text[:] in the post-type array used for the select was all that was required to have the proper translations show up on the front end.
In this custom case the backend is only required in one language so there was really no need to integrate any further.

What I meant by switching, was in the admin screen. My original thought was to supply both the English and the French options in the select. In that scenario I would want to be able to choose different options on the English admin post page as opposed to when I switch to French.

However I’m going to try to use the custom-config.json file approach described in the custom integration guide to integrating cmb2 into my theme. I’ll need to review those docs further as the structure of the json file is not totally clear to me yet.

I just realized that to add configuration files I need to use the “Configuration Files” not “Custom Configuration” option.

Thanks John,

cmb2 (and other custom field methods like ACF) allow you to create a select (dropdown) as a way to describe a meta value.

Currently if I switch the selection on English, it also switches it on other languages, I’m trying to find a way to keep them separate, as they are for text inputs and textareas (when used in conjunction with their ids).

These selects all have ids. And would look something like this.

<select class="cmb2_select" name="drink_ingredients[0][units]" id="drink_ingredients_0_units">
        <option value="taste" >To Taste</option>
	<option value="shot" >Shot</option>
	<option value="shots" >Shots</option>
	<option value="pint" >Pint</option>
	<option value="pints" >Pints</option>
	<option value="floz" >Ounces</option>
	<option value="Lt" >Liter</option>
	<option value="" >No Unit</option>
</select>

a + symbol in each LSB

What is it?

I was thinking a link with an onclick that triggers the duplicate action.

https://rdiv.com/screenshots/DuplicateAsNewLanguage.png

Control-click, or maybe a + symbol link in each LSB.
I think you should copy all multilingual fields, empty or not.
If not empty then just copy the existing content, the user can then change what’s required.

As for contributing, let me give it some thought and see if I can devote the time.

Thanks.

I think it is if you have many meta boxes as you might in a custom post type.

Or maybe I’m just lazy, but I found myself missing this feature.

Thanks.

An example of a plugin that does this is WPML.

The problem of course is they have way too many options, but simply described what I’m suggesting is as follows.

Let’s say you’ve created a post in your primary language (English) https://mysite.com/en/foo/, and you have French enabled as an additional language.

In your English post there will be a button that allows you to make a duplicate copy of that post as https://mysite.com/fr/foo/

Now you can edit the French page. This saves a lot of time in creating the alternate language version of the post.

Thanks.

added this to the necessary theme template files

<div class="at-above-post addthis-toolbox" data-url="<?php the_permalink(); echo '?utm_campaign=blog-social-share&utm_medium=social'; ?>" data-title="<?php the_title_attribute(); ?>"></div>

This caused the buttons to display twice, the new url with query string in one set of buttons, and the plain url in the second set.

Needed to disable the buttons in the AddThis website interface, so the only ones to display are the ones from the template.

Thanks.

Thanks! works great.

Sure https://wanlesstennis.com

1. In the sidebar widget
2. In the event itself (2 places) https://wanlesstennis.com/event/january-social-mayfair/
3. In the popup over each calendar event.