Problems with upgrade to Pro 7.1/Cornerstone 7.7 and loopers on acf repeaters

Support
#1

When I updated a client site today to the latest release it broke a number of items that were looping ACF repeaters. I switched back to 6.10 and it solved the problems for now. I didn’t go through the entire site before reverting but two examples I saw were on this page: https://nwwheelandtire.com/services/powder-coating/

  • if you scroll down to the color picker tool that is in the right sidebar, the update caused the color swatches to not show up. It seemed as if they were still looping and controlling the wheel graphic correctly but there was no color so they were invisible. They are pulling in a hex value from a ACF repeater. When I added a text box with the same field it would display the hex value correctly.

  • On the same page just below that are three large images. The theme update caused those imaged to not appear. Again, they are pulled from an ACF repeater.

#2

Do you have a staging we could look at? Were you using Twig here in the Advanced Background controls? Does it work when you utilize standard Dynamic Content? Great looking site by the way.

#3

I do have twig enabled, my color looper is {{ looper.field({“key”:“color_thumbnail”}) }} and returns a hex value. I don’t have a staging site that is up to date, but I can clone that site onto the staging environment for you if you like.

I just encountered a similar problem with another client site when I updated to 6.7 (now reverted to 6.6.10). The page I noticed it on was here: https://crookedtails.com/team/ and with the update the large photo of each staff member was not showing up. Twig notation is used again here but it doesn’t seem to cause an issue with the other images being looped on the page.

#4

I cloned the site for you here and updated to 6.7: https://nwwt.new-unknown.com/

Left a secure note for you to login, feel free to do anything you need to that site.

#5

Hi @Travis_Holman,

We have tried to check through the WordPress admin dashboard, but unfortunately, login requires another level of authentication through the registered email ID. Can you please temporarily disable it and let us know for further investigation?

image
image508×566 95.1 KB

Thanks

#6

Oh sorry, Wordfence is disabled now so you should be able to get in.

#7

I see the issue now thanks. It has to do with our background breakpoint changes and Twig specifically. Standard Dynamic Content is working fine. We’ll try to get that fixed in 6.7.2 on Monday. Have a great day.

#8

Great, thanks!

#9

You are most welcome, @Travis_Holman