Sounds like you have a javascript error caused by another plugin or by your theme.
To check for javascript errors go to the screen you are having the issue with and follow this these steps http://docs.inboundnow.com/guide/debugging-javascript-errors/ and this video:
VIDEO
Report back what you see.
Thanks for your quick response, basically the error is on Advance Custom Field Plugin javascript:
"Uncaught ReferenceError: acf is not defined"
I’ve tried deactivating the rest of plugins and themes, and the conflict only show up with CTA plugin, and after plugin update.
I’ve tried commenting this line https://github.com/inboundnow/cta/blob/master/classes/class.enqueues.php#L229
Where is the ‘acf’ variable reference being called? somewhere in the head tag?
View page source and ctrl + f to find ‘acf’
It shouldn’t be getting called so early
The acf is called in js inserted right on admin page.
You are awesome! thanks a lot!
No problem.
If you like the plugin (or the support), we would love a quick review from you on the WordPress Plugin Repository , it would really help us out!
You can leave a review here .
Thanks and let me know if you have any questions about the plugin.
I just fixed the issue on ACF 4.4.1 version
acf not defined…
The problem was in loading the scripts in the correct order.
What I’ve done is:
open “wp-content/plugins/advanced-custom-fields/acf.php” and go and comment the lines from 524 to 528 the init of the input.min.js then open “wp-admin/admin-header.php” and right after the <title></title> include these 2 scripts:
<script type="text/javascript" src="https://code.jquery.com/jquery-2.1.3.min.js"></script>
<script type='text/javascript' src='http://yourdomain.com/wp-content/plugins/advanced-custom-fields/js/js/input.min.js'></script>*move the input.min.js into new js folder into js to not get conflicts:)
save all the changes and you will see you wouldn’t encounter this issue just reload the CPT add new/edit page and there you go.
Hope this will solve everybody’s issue, it’s only temporary once we get an update from @elliot 🙂 hope the 4.4.2 will fix this issue.
Cheers mates.
