Please make sure to update to WPML 4.3.5 and check our list of Known Issues before reporting

Hi, Amit here, I am the WPML Support Manager, our current ticket queue is high, update your WPML plugins and make sure you meet the minimal requirements for running WPML before reporting an issue please - many tickets are resolved doing that

Please look at our updated list of Known Issues and you can also use our support search to find helpful information and of course review our documentation before opening a ticket.

If you do need to open a ticket please make sure to provide us with all the needed information as described in this page

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 34 replies, has 3 voices.

Last updated by Bruno Kos 6 months, 3 weeks ago.

Assigned support staff: Bruno Kos.

Author Posts
April 15, 2019 at 9:38 am #3611657

Mr. Ghost

6) Read the change log of your ACF helper plugin please. We will use options pages and those has to be multilingual, not translate the cms backend with string translation but to manage options page as a normal page translations as in. If I'm on the Spanish version it should give the Spanish value and not the English value. I asking since this video: hidden link

April 15, 2019 at 12:02 pm #3613223

Bruno Kos
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

Thank you for contacting WPML support!

Can you please check my next private message?

Regards,
Bruno Kos

April 16, 2019 at 6:08 am #3618335

Mr. Ghost

Let me know why this would be needed?

I have not yet received a confirmation from you how it would work. I'm not telling it is not working, and you have not said it should work.

Can I translate options page just as normal post/pages? So that each fields get a unique database value and dont cause this issue: hidden link

Let me know how WPML is intended to work with options pages.

If you make all my replies private I can share a video. When changing to another language WPML don't understand the options page is another page so it still show the other language value. Meaning you don't seem to support options pages??

The meta fields value is the same even if I change language. How to make it multilingual and make it work with WPML? Options page is a core thing of ACF and wordpress that I can not be without.

Options pages does not even appear in: /wp-admin/admin.php?page=wpml-translation-management/menu/settings

Are you supporting options pages? This is another key thing I have to have, which polylang support etc.

April 16, 2019 at 7:57 am #3619375

Bruno Kos
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

Can you tell me the following - does it work if you try to translate them using String Translation? Based on this - https://wpml.org/download/acfml/?section=changelog - Advanced Custom Fields Multilingual 1.2. which was published few days ago includes this:
- Fixed the translating ACF Options page (it can now be done using WPML String Translation).

There is also another approach that might work and is mentioned here, so have a look:
https://wpml.org/forums/topic/acf-option-page-fields-translate-field-values/#post-2969819

However, here is some explanation what is behind all of this:
https://wpml.org/forums/topic/force-synch-of-some-custom-fields-between-languages/#post-1455772

Regards,
Bruno Kos

April 16, 2019 at 4:30 pm #3624041

Mr. Ghost
Can you tell me the following - does it work if you try to translate them using String Translation? Based on this - https://wpml.org/download/acfml/?section=changelog - Advanced Custom Fields Multilingual 1.2. which was published few days ago includes this:
- Fixed the translating ACF Options page (it can now be done using WPML String Translation).

I saw that one which si why I asked. String translation should not handle such translations. Content managers will not have access to string translations and they will be the one handle some of these settings. It should be treated just as normal post/page. Translate it trough string translation is very poor experience and not at all good UX/UI. Another reason why I preferred refund.

There is also another approach that might work and is mentioned here, so have a look:
https://wpml.org/forums/topic/acf-option-page-fields-translate-field-values/#post-2969819

However, here is some explanation what is behind all of this:
https://wpml.org/forums/topic/force-synch-of-some-custom-fields-between-languages/#post-1455772

I do not see any work around. Why can't you support ACF options pages. It's not on ACF's side its on your side and multilingual. I'm fairly sure you can make it work if you just speak with Elliot at ACF. This is poor that WPML don't support or have a good solution and still 2019 don't support it I'm surprised and still disappointed we could nto refund since WPML do not support the basic things and serves the needs.

Neither have any good work around...?

April 17, 2019 at 6:34 am #3627501

Bruno Kos
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

Translate it trough string translation is very poor experience and not at all good UX/UI.

I guess I can give the same answer as I did on the other thread - I encourage you to suggest any feature you think WPML users may benefit from - this includes UX/UI suggestions:
https://wpml.org/suggest-a-new-feature-for-wpml/

Needless to say - WPML can't include all the options imaginable, hence there is this also:
https://wpml.org/purchase/support-policy/

Another reason why I preferred refund.

You were entitled for refund within 30 days. This not only our policy - most software and service providers have the same or similar policy, assuming that 30 days is enough to to through possibilities/limitations of any software.

I know that you were on this page, but have you filled in this form as well and gotten a response?
https://wpml.org/purchase/refunds-policy/

Regards,
Bruno Kos

April 21, 2019 at 1:43 pm #3652543

Mr. Ghost

I guess I can give the same answer as I did on the other thread - I encourage you to suggest any feature you think WPML users may benefit from - this includes UX/UI suggestions:
https://wpml.org/suggest-a-new-feature-for-wpml/

Needless to say - WPML can't include all the options imaginable, hence there is this also:
https://wpml.org/purchase/support-policy/

Already done! And sent how polylang sort it, they will release a major update to it soon.

You were entitled for refund within 30 days. This not only our policy - most software and service providers have the same or similar policy, assuming that 30 days is enough to to through possibilities/limitations of any software.

I know that you were on this page, but have you filled in this form as well and gotten a response?
https://wpml.org/purchase/refunds-policy/

We did not use it until April, but I understand but it's all about how much you value your reputation and consider the user journey and service to be. I'm not impressed byt support or product. But that's all up to you guys.

The things that could have been solved (found out now) was to just disable plugins and only use core WPML and media plugin + string translations in the future when needed. And I did and removed trash WPML adds. Still can not consider why you keep trash in the database when I delete the original fields. And when I need to sue string translations by default it should NOT register anything. Since if it does the first thing I have to do is clean the database from all strings WPML adds. And if if I remove auto register I have to delete all it added to my database. Meaning better you ask me when I install "do you want to auto register" YES/NO.

Which rows and tables in the database is string translations so I know exactly what I can delete without harming how WPML is built?

I might be hard but you have to understand that I'm not happy with the product and it cause me massive issues, support and functions within the plugin or how it performs. And this is feedback you should take and push further int he hierarchy.

April 22, 2019 at 2:58 pm #3656459

Itamar
Supporter

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+02:00)

Hi.

I'm Itamar from WPML Support team. I want to inform you that Bronu is not available, but he will be able to respond here tomorrow.

Thank you for your patience.
Itamar.

April 22, 2019 at 7:34 pm #3658057

Mr. Ghost

Ok noted. thanks!

April 23, 2019 at 8:53 am #3660955

Bruno Kos
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

And when I need to sue string translations by default it should NOT register anything. Since if it does the first thing I have to do is clean the database from all strings WPML adds.

It would make sense for some users and this has been discussed among our developers already, since some of our clients have brought this up. However, we did have much clients requesting this and "fixing" it would cause more headaches for our developers and users than leaving it like that, so it was decided to not implement this.

It is understandable that there will always be some feature not available in any kind software really that some users will need. However, I do not think it would be fair to say that it doesn't make the software useful or makes it bad, especially if any of these featured are not needed or requested by 99.9% of other users.

Regards,
Bruno Kos

April 23, 2019 at 4:28 pm #3666189

Mr. Ghost

It would make sense for some users and this has been discussed among our developers already, since some of our clients have brought this up. However, we did have much clients requesting this and "fixing" it would cause more headaches for our developers and users than leaving it like that, so it was decided to not implement this.

It is understandable that there will always be some feature not available in any kind software really that some users will need. However, I do not think it would be fair to say that it doesn't make the software useful or makes it bad, especially if any of these featured are not needed or requested by 99.9% of other users.

I understand what you mean but I would easily prefer to be able to delete auto register and delete all registered strings from SQL or directly from wpml. Not be needed to click though all pages. A simpel delete all and then wpml will process the action instead of millions of click to delete.

And to my request to be able to translate options page you wont follow the leading polylang? So my work around is creating custom CPT and control global settings like that. Poor work around and dependency on WPML. I'm surprised WPML do not support it, it's a core thing and if you support ACF why can't you support options page as a normally and polylang does? It makes me sad and angry that I have to do work arounds for something that just should work consider the community using ACF and 90% use options pages in one way or another. And polylang listen to their customers and sort it.

April 24, 2019 at 10:42 am #3671713

Bruno Kos
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

page as a normally and polylang does?

I am not familiar with Polylang features or how it works, so I can't comment.

I am not sure if there's anything else I can assist here or answer? Based on your last reply, I can send you this link once again:
https://wpml.org/suggest-a-new-feature-for-wpml/

Because I don't have an answer on why don't we implement something that other plugins may be using. I do not think we (support or developers) can give a straight answer for this nor there is a "correct" answer for this.

Regards,
Bruno Kos

April 27, 2019 at 7:59 am #3694857

Mr. Ghost

I am not familiar with Polylang features or how it works, so I can't comment.

I think you at WPML should be aware of your competitor and see what they do and don't.

I am not sure if there's anything else I can assist here or answer? Based on your last reply, I can send you this link once again:
https://wpml.org/suggest-a-new-feature-for-wpml/

As previously mentioned already requested this as a feature, but god knows if and when it would happened. The guy who answered on the request asked for more information. Provided and then went on vacation and MIA.

Because I don't have an answer on why don't we implement something that other plugins may be using. I do not think we (support or developers) can give a straight answer for this nor there is a "correct" answer for this.

I think they could speak directly to me in the terms of this feature.

April 27, 2019 at 8:59 am #3695027

Bruno Kos
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hi,

Provided and then went on vacation and MIA.

Our request list is huge and regularly discussed among managers, product leads and developers. If they decide that something is worth implementing, it will go into development. It is the same with every software development in fact, otherwise developers would do nothing else but developing custom solutions for a handful of people who might need a specific feature.

If there is a small number of requests for a certain feature, then most likely it will not be considered as relevant or will not be in the top of the queue. Please see our support policy:
https://wpml.org/purchase/support-policy/
-- What’s NOT INCLUDED with WPML’s Support

I think they could speak directly to me in the terms of this feature.

Therefore, if they stopped responding, there is a reason for this and is most likely one of the reasons I mentioned above.

Regards,
Bruno Kos

May 1, 2019 at 7:32 am #3716665

Mr. Ghost

I understand what is being developed but based on what I see in communities of acf and wpml options page should be in the top of the list. Regards top reply in the middle of the conversion I thinks is poor service mind and lack of customer interest. Ask more information about what I mean and then MIA.

I do not agree with that you end the conversion there.

Can you keep on making this forum thread private, please.