Ignore me. This was a caching issue.
I’m getting a different error when using flexible content in conjunction with the WYSIWYG.
Uncaught TypeError: Cannot read property 'canvas' of undefined
in the quicktags functionality.
Enabling/disabling SCRIPT_DEBUG fixes the issue which is strange.
Hey Elliot,
More than happy to provide you access and show where we’re seeing the issue even though it appears we have a work-around.
Hi Elliot,
Sorry for the confusion. I was trying to say that I think the the wp object error was related to the fact that the field (in our case) never finished processing. I concluded this based on the fact that we were seeing the same result before and after the wp object fix you implemented. Once I limited the scope of the posts that field was trying to query against I wasn’t getting the wp object error and the rest of the edit page was being processed appropriately.
Hey Elliot,
We’re experiencing this issue as well on a site we’re developing. The new version on github has resolved the error with the wp object, but the issue still persists. The issue being the fact that no fields are being displayed on the page beneath the field that’s having issues.
In our case it’s a filter & search field that’s looking through 10k+ posts. It seems like this query is hitting some kind of limit (probably time) that’s causing everything to go downhill from there.
We’re doing our best to limit the scope of the posts it’s pulling in, but it’s still buggy.
Let me know if you want access so you can poke around.
Seriously. You’re a life saver.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.