java script error and no shipping fields after turning on the plugin

  • Resolved Medran

    (@medran)


    5 years, 8 months ago

    Hi guys,

    When translatepress is active the following java error shows up in my chrome console:

    VM4617:1 Uncaught SyntaxError: Unexpected token F in JSON at position 16745
    at JSON.parse (<anonymous>)
    at Function.n.parseJSON (jquery.js:4)
    at HTMLDocument.<anonymous> (country-select.min.js:1)
    at i (jquery.js:2)
    at Object.fireWith [as resolveWith] (jquery.js:2)
    at Function.ready (jquery.js:2)
    at HTMLDocument.J (jquery.js:2)
    n.parseJSON @ jquery.js:4
    (anonymous) @ country-select.min.js:1
    i @ jquery.js:2
    fireWith @ jquery.js:2
    ready @ jquery.js:2
    J @ jquery.js:2

    The impact of this is that customers can no longer choose a ship to address instead of their billing address and it’s happening for the base language (German) there as the extra language English is working fine.

    Thanks,

    Marc

Viewing 3 replies - 1 through 3 (of 3 total)
  • Denis

    (@sdenis)

    5 years, 8 months ago

    Hello Marc,

    I tried to replicate the problem you encounter but it is not replicable.

    But since thi looks a lot like a conflict with some other code, the first/next recommended step is the conflict test (ideally in a staging environment):

    ​​*Briefly* disable all other plugins and enable the default Twenty Twenty theme. Please also disable all add-ons. If this fixes the problem, as it probably will, enable everything one by one, checking each time to see when the problem returns.

    Also, please see if you have enabled “Fix broken HTML” in the plugin settings (If you have enabled it try to see if disabling it will change anything)
    And enable “Disable dynamic translation” temporarily to see if is doing something in your case.
    You can find those option going to:
    WordPress → Translatepress → Advanced Tab.

    P.S — When you do the conflict test do it with caching plugins disabled to be sure that it does not interfere with the test.

    Please let us know when you find the conflict so that we can take a look and see what we can do about it.

    Kind regards,

    Thread Starter Medran

    (@medran)

    5 years, 8 months ago

    Ok, the incompatibility comes from flatsome! Are you able to fix it to work with flatsome’s checkout method?

    Thread Starter Medran

    (@medran)

    5 years, 8 months ago

    Ok further narrowed it down. It works with all plugins active if on a default theme.

    if flatsome is active the specific conflict only occurs if flatsome and YITH WooCommerce Wishlist Premium are active at the same time!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘java script error and no shipping fields after turning on the plugin’ is closed to new replies.