• Resolved kim.oj

    (@kimoj)


    Hi
    Love this plugin it does exactly what I need, but I also need Advance custom builder and if I have both plugin activated I can’t use the tags… Tried switching to another custom field plugin (Custom Field Suite) but got the same problem. I have also tried switching to Twenty Sixteen to se if it was something with the theme I’m using (Newspaper) but that didn’t solve things…

    Here is the error frome chromeconsole.

    The language of WP is Swedish.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter kim.oj

    (@kimoj)

    Hi again!
    Have had some contact with the ACF support and they have helped me allot!

    Here are two of their comments that can help you fix this conflict in this plugin.
    And hopefully help others until this is fixed!

    I’ve just done some testing with the free version and found that the ‘WP Post Expires’ plugin is registering a custom jQuery date picker library.
    WP includes the jquery date picker library in it’s core, which is what ACF enqueues.
    It seems that any plugin that enqueues the WP date picker library will trigger this issue.

    The only solution for now is to edit the ACF plugin file ‘acf.php’ on line 551 and remove ‘jquery-ui-datepicker’ from the deps array.

    Please contact the developers of ‘WP Post Expires’ and notify them that the datetime picker fails when the WP ‘jquery-ui-datepicker’ library is enqueued.
    There is nothing I can do about this bug from my end, it must be fixed from ‘WP Post Expires’

    I’ve just done some testing and found that the issue comes from a line of JS within the ‘WP Post Expires’ Plugin.
    It’s not necessarily a ‘bug’ in their code, but when ACF PRO is active, this conflict is caused.

    The line of code that causes the issue can be found in the file ‘wp-post-expires/assets/js/plugins-scripts.js’ on line 18.
    The issue is that the ‘langs’ variable does not contain the expected object key because ACF PRO has included the datetime picker JS without including the ‘en’ translation – becuase the default language is already english.

    Simply comment out line 18 and the page will work again as expected.

    Hope this helps

    Thread Starter kim.oj

    (@kimoj)

    Marking as resolved

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with ACF’ is closed to new replies.