You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for creating this awesome project, I can't wait to (hopefully) switch from ACF Builder as this looks like a much easier and cleaner way of using ACF with version control support 😃
Unfortunately it appears that ACF Windsors can't currently work with dependency based WordPress structures such as Roots Bedrock, as add_action is called before the function exists.
Other projects such as Timber get around this by having the user initialise it via functions.php.
Hopefully this is something you'd be willing to change as I'd love to use ACF Windsor moving forward.
Any questions or what not just let me know.
Cheers,
Tom 🙂
The text was updated successfully, but these errors were encountered:
This is definitely something I am going to address, thanks for bringing it up!
At the moment the library is set to auto-initialize as a means of convenience. I am thinking of giving the flexibility for developers to defer this initialization, and leave it to developers to decide when to initialize the library. Which I think will solve the issue if you are using Bedrock.
I will play around with it using Bedrock, stay tuned.
Hi @jofrysutanto,
First of all, thanks for creating this awesome project, I can't wait to (hopefully) switch from ACF Builder as this looks like a much easier and cleaner way of using ACF with version control support 😃
Unfortunately it appears that ACF Windsors can't currently work with dependency based WordPress structures such as Roots Bedrock, as add_action is called before the function exists.
Other projects such as Timber get around this by having the user initialise it via functions.php.
Hopefully this is something you'd be willing to change as I'd love to use ACF Windsor moving forward.
Any questions or what not just let me know.
Cheers,
Tom 🙂
The text was updated successfully, but these errors were encountered: