Here’s how I do it: https://gist.github.com/jacobdubail/d5b5e76e6daca8a3258518fe710ed102
I just define my license key in my wp-config. You may want to add/tweak the action hooks this is added to so it runs in your situation.
Hi @Elliot Condon,
Gravity Forms does it like this: define(“GF_LICENSE_KEY”, “YOUR-LICENSE-KEY-HERE”); http://www.gravityhelp.com/documentation/page/Advanced_Configuration_Options
I’m not positive what the underlying code looks like. Do you need me to dig that up?
One last attempt to get a look at your code. Could you at least let me know which filter you’re hooking into? Is it acf/fields/relationship/query?
@elliot, any idea which filter I can use to do a switch_to_blog() just before the relationship query runs?
I’m definitely interested in the easier, more straightforward approach, especially if it is more upgrade proof. I’ll only be dealing with standard posts, but seeing how you handle custom posts would also be useful.
How would you like to share the code? Public dropbox link? email?
edit: Never mind. I’m being dumb… Don’t need Locations any longer. Google Maps is a core field… Duh!
I’ve disabled all of my plugins, except locations and ACF Core, but am still seeing this JS error in the console.
Uncaught TypeError: Cannot read property 'Autocomplete' of undefined
I’m running WP 3.7.1, ACF 4.3.1, Location Field 1.0.0. I’m using Chrome 31 on Mac 10.9.
I forgot to mention that our homepage is non-functional until we get this issue resolved.
I’ve added a new single-depth repeater to this group (above the troublesome repeater field) and it works. I re-created the troublesome multi-depth repeater field and it doesn’t work. It throws the same error as before.
Edit: I’ve narrowed the problem down further. The problem only occurs when I add a “post object” field into the 2nd-level repeater field. If I change the post object field to a text field, everything works. Weird…
This is a JS error. Here’s a quick screencast showing the error and the custom field details: http://quick.as/mqnibpm
As you can see, the error pops up as the fields are loading.
Could you share a screenshot of what you do see in the dropdown? Also, are you familiar with the Developer Tools in your browser? If so, flip over to the Console panel and refresh the page. Do you see any errors?
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!