• Resolved La Ziviani

    (@mymeitai)


    Hi! This error occoured today, maybe before, I don’t know exactly after which update it beginned… I’ve checked similar errors in google, everyone has a string to find where error is, in my case there is nothing after this. I’ve tried to deactivate plugins but problem has not been solved. I’m really worried and I cannot find a solution. Somebody can help me?
    I’m sorry for my bad english…

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support slash1andy

    (@slash1andy)

    Automattic Happiness Engineer

    Hey there!

    I went to look at your site, but I am not seeing where you are seeing this error, do you have a link that I can see it on, or a screenshot of the issue?

    Thanks.

    Thread Starter La Ziviani

    (@mymeitai)

    Thanks Andrew!
    there are non problems until you check the shopping cart, then clicking on “proceed to order” you shoul’d find the chekout page (“cassa” in Italy) but this error occurs. https://www.mymeitai.com/shop/cassa/
    I don’t know how to attach a screenshot… but you shoul’d find same error as my customer and me. Thanks again 🙂

    Thread Starter La Ziviani

    (@mymeitai)

    No solutions/help for me? Some suggestion? Otherwise next step is to restore previous backup, made two months ago before installing update of my theme hopping this will solve problem. And then update theme again, hopping that will not create same problem or new one! Thanks

    Thanks for your additional info.

    I can see the error by following the steps you mentioned:


    Link to image: https://cld.wthms.co/YXg6TI

    This kind of problem is usually caused by either a conflict with your theme or with another plugin.
     
    The best way to determine this is to:
     

    • Temporarily switch your theme to Storefront
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    Mike M. a11n

    (@mikedmoore)

    Automattic Happiness Engineer

    Hi,

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

    Thread Starter La Ziviani

    (@mymeitai)

    It’s not a short procedure, I need time and cannot do it during the day, when usually people visit my blog. I think I will try to do it tomorrow in the night and let you know. Anyway thanks a lot for suggestions!

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

The topic ‘PARSEERROR THROWN syntax error, unexpected ‘wc_kses_notice’ (T_STRING)’ is closed to new replies.