Object cache causing issue with ACF WYSIWYG editior tag

Loops & Logic
1

Hello,

There might be a problem with the new object cache feature and the ACF WYSIWYG editor tag.

On my sites, when the cache is on, it removes the <p> tags from the frontend output.

I thought it was just a temporary issue, so I left the cache on, but the <p> tags went missing again.

Turning off the object cache and clearing the cache in Litespeed resolves the issue.

This could be a conflict between L&L and Litespeed, but I did a fair amount of testing with Litespeed disabled.

I use the Advanced preset in Litespeed with object cache disabled.

image
image450×1116 55.9 KB

Cheers.

2

Thank you for the issue description.

I’ll see if I can reproduce the issue. It’s hard to imagine how it could be caused by L&L’s cache, since it does not change the content. It only performs the same processing logic on page save instead of during page render. So if <p> tags are being removed, it must be happening during page render, which has the exact same processed data, with or without cache.

Well, I’ll see what I can find out. If the issue doesn’t happen on my end, then it’s likely related to Litespeed. Otherwise, maybe something to do with how ACF’s WYSIWYG field works.

1 Like
3

Hi Eliot,

I just did a little test by turning the Tangible object cache back on, and the issue came straight back. Litespeed was also running, and disabling the LiteSpeed plugin did not resolve the issue.

It’s noticeable because my CSS can’t target the <p> tag anymore:

image
image446×777 72 KB

It is a strange bug, it’s almost like the ACF editor tag reverts to a standard field tag:
<Field acf_editor=sim_services_description />