As I said, I have another live site which is my test one, hosted by the same provider on a different server (so server configuration should be the same), but on such site I’m not having that issue…
In the next few days I’ll try to copy the live site over once more, in order to try replicating the issue
Has there been any update on this?
We’re experiencing the exact same error.
ReferenceError: wp is not defined
Advanced Custom Fields – 4.3.2
Advanced Custom Fields: Repeater Field – 1.1.1
WordPress – 3.7.1
Don’t know if this helps but the full error from my console is:
Uncaught ReferenceError: wp is not defined input.js?ver=4.3.2:339
(anonymous function) input.js?ver=4.3.2:822
I can send you log in details, I’ll do that shortly.
No, the edit page half loads but the wysiwyg doesn’t along with any media buttons then it looks like it gets stuck in an endless loop of loading. I’ve come across this on two completely separate sites now.
Just to confirm, the page is not compltetly loading, but being cut off?
It sounds like you have a PHP error / MEMORY limit issue going on which would explain why the wp object doesn’t exist. The wp object is a JS object added by WP – most likely in the footer scripts. If the footer is never rendered, the perhaps your browser is firing the document.ready action without realizing the page is broken!
Can other confirm this is the same issue?
As I said before, it does look like a memory limit issue, however I’m not seeing any debug message with the usual “Allowed memory size of xxx bytes exhausted”.
I tried increasing memory limit via php.ini, htaccess, wp-config.php with no joy.
Funny thing is that if I use a relationship field instead of post object or page link, it works fine (and that’s how I solved the issue for the time being…).
Thanks again Elliot for your support
I am experiencing this problem too w/ ACF 4.3.2 on a 3.4.2 WP site I am adding some enhancements to. The problem seems related to image upload, my repeater fields work fine.
I was able to solve locally 2 ways:
1. Upgrading to 3.8
2. Leaving WP at 3.4.2 but installing the ACF 4.1.8 from Github page.
Not sure if that helps. Hoping I can get the orig. developer to upgrade the live site to 3.8 and that will solve it in my case…
@elliot Ok we’ve figured out what the problem is – our site contains 10’s of thousands of posts. When when you have a page link field within a repeater and have it set to all posts (as we have thousands of posts over various post types) it simply times out having to loop through so many posts. This then causes the havoc.
We’ve limited the page links to only show pages and this solved the problem. It is ideal but at least we’re functional again.
Is there any other way to stop this happening?
We are having this issue on one of our websites. It seems to happen on only one page and only for users that are not administrators. We do not use the repeater fields.
Elliot if you would like to take a look I’d be more than willing to give you access to our website.
I just updated to 4.3.3 this morning too and the problem still exists.
Can you please turn on DEBUG_MODE in your wp-config.php file and reload the edit page? Is there are PHP errors on the page? If not, also check the source code.
Your edit page is breaking after the theme options metabox, which explains why the wp_footer action is never run and the wp JS object is never included (WO includes many JS files in the footer)
The topic ‘ReferenceError: wp is not defined in input.min.js’ is closed to new replies.
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!