ftpwp

It’s not working. The child language strings are just ignored.
Have you tested this method for OceanWP?

Is this function correct?

function child_theme_slug_setup() {
    load_child_theme_textdomain( 'parent-theme-slug', get_stylesheet_directory() . '/languages' );
}
add_action( 'after_setup_theme', 'child_theme_slug_setup' );

Thanks, I’ll have a look!

I was close. Was just missing the code in functions.php.
But I still need to find out if we can set .po/.mo files that includes only the modified strings, not all the strings.

If we can include only the modified strings, it’s perfect.
But if it works only with all the strings, then it’s close to pointless.
It would mean that for each update of OceanWP I would have to control its .po/.mo files and update the one of the child theme.
I’m not will to translate a whole theme, but just adjust/improve some few strings.

Ok I’ve opened a ticket.

• This reply was modified 5 years, 5 months ago by ftpwp.

Few additional information. If you take back my 2 examples:

– Cookie Notice
We can find the string to translate in WPML > Theme and plugins localization > ocean-cookie-notice > “By continuing to use this website, you consent to the use of cookies in accordance with our Cookie Policy.” > Translations.

But despite the fact that the translation exists, it’s never displayed. I’m using the French translation and whether the visitor visits the site in French, French is set as default language or the registered user has French set as website language, the notice is always displayed in English (as set in Appearance > Customize > Cookie Notice > Content), never in French!

– Ocean Elementor Widgets
Here the translation strings are not even available.
Try to…
– Create a new page > Edit with Elementor > Add a Section
– Add the Ocean Table widget in the section > Edit the Cell Text of 1 header and 1 content cell
– Save the page
– Go to Menu > Pages > Create a language translation for the new page

You should see all the Table widget strings to translate, edited or not, but there’s nothing!

So all this makes me think that no extension is WPML compliant. OR I ended up right on the ones that are not.

Thanks for the update!

@re_enter_rupok +1. New 3.3.0 version and still nothing ??

And BTW, I ran a quick test regarding the WPML compatibility and found out that there’s still quite a few free widgets not compliant:
– Advance Accordion > OK
– Advance Tab > OK
– Call to Action > OK
– Content Ticker > NOK
– Countdown > NOK
– Creative Button > OK
– Data Table > NOK
– Dual Color Heading > OK
– Fancy Text > OK
– Feature List > OK
– Filterable Gallery > NOK
– Flip Box > NOK
– Image Accordion > OK
– Infobox > OK
– Post Grid > No need
– Post Timeline > No need
– Pricing Table > OK
– Product Grid > No need
– Progress Bar > OK
– Team Member > OK
– Testimonial > OK
– Tooltip > OK
– Twitter Feed > NOK

I did it quickly, I may be wrong on one or two, but it looks like there’s still some work to be done.

Hi,

Guys, the ticket has been closed 10mn ago but the issue is NOT fixed with the last version! (2.0.56)
https://github.com/ultimatemember/ultimatemember/issues/580

Can you give an update and re-open the ticket please?
Thanks!

Hi @bueltge,

Any direction to help me?
Thanks!

Well, we will be releasing a new version today. You can expect something exciting ??

Is it the 3.1.5 that’s supposed to be “exciting”?

3.1.5 – 30/07/2019

Compatibility issue fixed with PHP 5.4 / 5.6
Few minor bugfix and improvements

And the 3.1.4.1 has never existed?

Can you please provide a changelog for the 3.1.4 & 3.1.4.1?

It’s neither on www.ads-software.com…
https://www.ads-software.com/plugins/essential-addons-for-elementor-lite/#developers
…nor on your website…
https://essential-addons.com/elementor/changelog/

Thanks.

Well, once you install the latest version of Essential Addons, translations for the widgets will be automatically available in the WPML Translation form for the pages where you have used EA elements. You won’t have to re-add or re-do anything.

Ok, thanks.

Regarding, most of our elements are now fully compatibility with WPML except for a few such as Data Table which will be added in the coming weeks (2 weeks at most).

Thanks for the time frame.

But you could be a bit more transparent instead of hiding the list of widgets that are not compliant. You’re not helping your users & customers by misleading them, even temporarily.

If it had straight away been written in the 3.1.0 announcement that the Data table widget was not yet WPML compliant but it will be by one month, instead of daring writing “Added : WPML support for all elements”, you would have saved those 2 public support topics!

Hi,

> We are gradually making all our widgets WPML Compatible.

So what’s the list of widgets not WPML compliant yet?

> So, EA Data Table should be added in one of the future updates.
> We are working on it. Don’t worry.

I read this answer since February.
The WPML compliant version was supposed to be released in March.
And mid July the widget I’m looking for is still not available with no information regarding a potential release time frame.

All this mess, lack of accurate information, visibility and support is the reason why I’ve not renewed my subscription to EA Pro last month.

> For how WPML Works with existing pages, the process is that you simply
> go to the Translations page…

You completely missed the point once again.
I’m not asking for a WPML user guide. I use Elementor and WPML for a long time.

I’m asking you if once we will have an EA version that works, once we will have installed it, will the translation entries/fields be automatically available or not, added, in the WP Admin > Pages > Page to translate > WPML page translation form?

Or will we have to edit and save the page first to make those new fields to translate for WPML available?
Or will we even have to remove and re-add the EA widgets to make those new fields to translate for WPML available?
Etc.

The layout is:

Row 1
First name | Last name

Raw 2
Address (parent) | Floor (Custom callback)

Raw3
Username | Password
Email | Password confirmation

Raw 4
Agreement (checkbox)

Here is the screenshot…
https://ibb.co/jwT02d5

I fill in all the fields except didn’t put any password (Mot de passe), submit and the floor (Etage) is lost when the page is reloaded.

And the callback function is:

function getFloors() {
	//Get the value from the 'parent' field, sent via the AJAX post.
	$choice = $_POST['parent_option'];

	//Depending on the value of $choice, return a different array.
	switch($choice) {
		case "18 rue Henry Bordeaux":
		case "20 rue Henry Bordeaux":
			$floors = [
				"RDC" =>"RDC",
				"1er" => "1er",
				"2nd" => "2nd",
				"3ème" => "3ème",
				"4ème" => "4ème",
				"5ème" => "5ème",
				"6ème" => "6ème"
			];
			break;
		case "22 rue Henry Bordeaux":
		case "24 rue Henry Bordeaux":
			$floors = [
				"RDC" =>"RDC",
				"1er" => "1er",
				"2nd" => "2nd",
				"3ème" => "3ème",
				"4ème" => "4ème",
				"5ème" => "5ème",
				"6ème" => "6ème",
				"7ème" => "7ème",
				"8ème" => "8ème"
			];
			break;
		case "44 avenue Gambetta":
			$floors = [
				"RDC" =>"RDC",
				"1er" => "1er",
				"2nd" => "2nd",
				"3ème" => "3ème",
				"4ème" => "4ème",
				"5ème" => "5ème",
				"6ème" => "6ème",
				"7ème" => "7ème",
				"8ème" => "8ème",
				"9ème" => "9ème",
				"10ème" => "10ème"
			];
			break;
		default:
		//code to do something if other options are not selected (throw an error, or set $floors to a default array)
		$floors = ["Sélectionnez une adresse"];

	}
	return $floors;

}

Can you provide an email (I can send you a link)?

I think the $user_id variable is missing in the um_user_after_updating_profile hook :-/

If we take a similar hook like um_after_save_registration_details, it has $submitted AND $user_id! Otherwise, with only $submitted, so far I really don’t know how we can know which profile has just been updated ??