Hi guys
Thanks for the reply.
Yes, the 3rd party add-on has used a class name matching ACF’s internal naming convention. This has led to the conflict.
Furthermore, where ACF wraps it’s classes in an if statement to avoid duplicate classes, this 3rd parry add-on has not. Because the 3rd party add-on is loaded after ACF, it causes the duplicate class issue.
A simple if statement will fix the problem for now, and the values previously saved should load correctly through the new core date time picker field
