public static function iterate( $fields, $transformField, $transformLayout, $fieldBasePattern = '' ) {<br /> foreach ( $fields as &$field ) {
To:
public static function iterate( $fields, $transformField, $transformLayout, $fieldBasePattern = '' ) {<br /> foreach ( $fields as &$field ) {<br /> if ($field["value"] == NULL ){<br /> continue;<br /> }
NOTE: Always ensure you have a recent and working backup before making any changes.
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket at WPML support forum for further assistance.
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.
In the past we were able to manually edit the plugin files to work around the issue while we waited for an official resolution. However the old workaround is no longer valid.
Symptoms:
Average server side response time in the two weeks before our most recent updates of the WPML plugins was 1117.6 ms. After updating the WPML plugins, the average server side response time increased to 1956.31 ms.
Looking at the top most time consuming WordPress hooks before and after this update. There is a huge spike in the amount of time spent on the acf/load_field hook. It used to account for 12.58% of call time, but after the update it accounts for 56.25%. It went from around 90 million calls over 2 weeks, to over 61 billion calls. (see screenshots)
Questions:
What changes can I make to get us back to a more sustainable performance level with these plugins.
I've gone ahead and implemented the potential workaround outlined above. It will take a little time before there is enough performance monitoring data accumulated to know if it made a difference or not. I will be keeping an eye on the monitors over the next 24 hours and I'll report back here with what I find.
That workaround is doing good things for us. It looks like performance is returning to approximately previous values since we've enabled it. (screenshot attached)
The next big thing I'd really love your support on is moving this from a workaround we are manually applying, to something more permanent. We've been manually apply one fix or another to every ACFML update since March of 2023 to keep performance normal. Is this fix something that will be applied to the ACFML plugin for all users?
I am going to close this for now, our issue is at least temporarily resolved pending a further future update to ACFML that will more permanently fix this. Thank you.