I have a hunch that the issue reported by @bhargavy is due to a different problem. This error though is being generated in the current 5.2.4 release of ACF Pro and as soon as I reverted back to 5.2.3 it went away. So for me at least I have found a temp solution to the problem.
I have reported the issue to Elliot about this occurring in 5.2.4 and am waiting feedback.
I’ve just got this with the latest 5.2.4 as well 🙁
@randomlines I just had a thought though; how specific are googles geocode entries… would they always locate to the correct house number?
@randomlines Ah brilliant thanks so much, that second idea is just what I was after. I didn’t realise the google API was quite so helpful and easy to use.
Thanks so much
Hi @nycdev I thought this would be possible as well although from experimenting with floats and other bits I haven’t been able to do this so far.
Does anyone have confirmed css that can cause such float/wrapping?