benbranyon

Thanks! Yes, that’s possible. I’d rather not have to use a composer patch if possible, so I’ll give that a try. We are using the acf/init hook elsewhere in the custom code quite a few times without any defined priority.

Yes, I’m already debugging on my local copy of the website with all of the other plugins turned off except ACF Pro and ACF Extended. We do have a pretty custom version of WordPress built on Sage10, so it may be that your plugin just has some issues with that setup. I’ve isolated the settings page issue down to that line of code I mentioned previously, so I might just patch it myself with a composer patch. Otherwise the ACF path shows up correctly in our theme and everywhere else. I will keep investigating and update this thread if I find anything else.

2. When I make the update to fix the settings page I see that the Json is enabled and the custom path for our acf-json folder is correct. Still whenever I try to save or sync a field group the file gets deleted instead of updated. When I turn off acf-extended it works as expected. Is there anything in the plugin that would modify this functionality?

• This reply was modified 4 months, 1 week ago by benbranyon.

1. I’ve been doing some more debugging and found something interesting. When I change the priority to anything below 10 for the acf/init action on line 22 in acf-extendend/includes/admin/settings.php this error goes away and the correct path is shown. It seems acf_post_init() wasn’t firing at all with the priority value set to 100 for our setup. So add_action('acf/init', array($this, 'acf_post_init'), 9); works on our setup, but add_action('acf/init', array($this, 'acf_post_init'), 100); doesn’t work. I’m not sure exactly what would cause that in our code base. We are using the acf/init hook elsewhere in the codebase, but I’m not seeing any other priorities that should interfere.

Thanks for the reply.

1. It is quite strange. The path setting seems to be set correctly in ACF Pro, but when I try to debug it in ACF Extended it’s empty. We do have ACF Pro installed as an mu-plugin which is a little bit different of a setup, but I don’t think it would cause this issue? Currently on version 6.3.11. We are also using Advanced Custom Fields?Multilingual, but turning that plugin off doesn’t seem to fix the issue.

2. Interesting, I don’t seem to have that Advanced Settings metabox on my field group edit screen. We do have some custom code for ACF json loading, so I might have to dig deeper into that.