Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 -
- - - - - - -

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: 

This topic contains 0 replies, has 0 voices.

Last updated by Waqas Bin Hasan 1 month ago.

Assisted by: Waqas Bin Hasan.

Author Posts
December 31, 2024 at 8:24 am #16555088

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for your patience and cooperation.

Our team recommends the following workaround:

1) Edit \sitepress-multilingual-cms\classes\custom-field-translation\class-wpml-copy-once-custom-field.php

2) Replace following on line 36:

$custom_fields     = get_post_meta( $post_id );

3) With:

$custom_fields     = get_post_meta( $post_id );
$custom_fields_to_copy = array_intersect(array_keys((array) get_post_meta( $source_element_id )), $custom_fields_to_copy);

4) Save.

We've checked this on our side and seems to resolve the issue. Please check in your setup and let us know.

December 31, 2024 at 8:47 am #16555101

Ahliman maelT

Hello,

Thank you so much for your response. I just tested it, and indeed, with this change, the Save button responds almost instantly compared to the 30-40 seconds it used to take before!

Will this fix be included in the next WPML update? In our company, our policy prohibits modifying the files of third-party plugins because any updates in the future would overwrite our changes, and it’s not very practical to implement this on hundreds of sites. (I’m just pointing this out in case it helps, as I’m not sure what your next steps are.)

Also, if this will be included in the next update, have you added unit tests or other safeguards to ensure this doesn’t happen again in the future, whether related to this function or other areas?

Once again, a huge thank you for your help! If you include this fix in the next version, you’ll save hundreds of hours wasted every year with every click of the Save button!

December 31, 2024 at 10:57 am #16555475

Ahliman maelT

I just tested again; at first, it was fast, but over time it becomes slow again (better than before, but still slow).

Does the suggested solution perform any additional operations in the database? Maybe it becomes heavy with each click because of that?

December 31, 2024 at 12:38 pm #16555833

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for your replies and I understand your concerns. I'm checking with my team and 'll get back to you accordingly.

January 3, 2025 at 7:49 am #16560408

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for your patience and cooperation.

Please consider following as answers to your concerns:

We’re unable to provide an ETA for the fix at this moment.

All updates undergo thorough testing before release, including safeguards like unit tests where applicable.

As of the performance, the proposed solution is designed to remain optimized over time. Based on our testing, we haven’t encountered any issues on our end.

We've tested in localhost, as well as, in the CW test site (provided earlier). However, we'd be interested in knowing more details about the slowness (i.e. any detailed steps and/or a screen-recording, or whatever is more suitable to reproduce the issue). And we can then investigate further about it.

Please let us know.

January 7, 2025 at 3:03 pm #16570383

Ahliman maelT

Thank you for your response. This is a very sensitive and important topic. The speed of a website is crucial, both on the back office side and the front end.

Would it be possible to keep this ticket open until we find a solution? On our side, we are also working on this issue to perform a thorough debugging and provide you with more details if possible.

January 8, 2025 at 8:03 am #16572271

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for the updates, we understand your concerns and would love to have more details, so we can try our best to help you resolve the matter.

Yes, you can keep this ticket open as long as there's some activity. Usually a ticket is automatically closed within 2 weeks time. However you may get a notification as ticket approaches the close-time. You can just post a reply.

Please take your time and feel free to share more details.

The topic ‘[Closed] ACFML timeout issue on pattern/post update’ is closed to new replies.