JS-errors after Core Update in developer console

This topic has 7 replies, 2 voices, and was last updated 2 years, 2 months ago ago by Shark

  • Avatar: Shark
    Shark
    Participant
    March 8, 2022 at 10:43

    Hi folks,

    after core update I get a view JS- Errors in developer tool. Can you help me with that?

    Regards

    Andreas

    Please, contact administrator
    for this information.
    6 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    March 8, 2022 at 11:14

    Hello,

    We do not see this error in the console on your Home page. Please provide URL of page with the problem.

    Regards

    Avatar: Shark
    Shark
    Participant
    March 8, 2022 at 11:34

    You have to enter some product and go back to home then you see a view errors like that https://prnt.sc/V0JBf5qOkCph

    Regards

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    March 8, 2022 at 12:00

    Strange, but we can’t see the problem. Please record a video, upload it here – https://dropmefiles.com/ and provide URL via the Private content area.

    Regards

    Avatar: Shark
    Shark
    Participant
    March 9, 2022 at 10:37

    Hi, I can’t see the error anymore either. If I know when this occurs exactly I will send the video.

    But I have a new problem on the start page – can you tell me where this error comes from? Looks like some icons are incorrectly linked

    Thx

    Andreas

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    March 9, 2022 at 13:35

    Hello,

    It was a problem in your LayerSlider -> https://gyazo.com/8828029e3f8b8b757ed062fd8fbd88fc
    There was an image set but without any data and it caused and error in console

    Regards

    Avatar: Shark
    Shark
    Participant
    March 9, 2022 at 15:52

    OK, perfect – thx very much!

    Best regards

    Andreas

  • Viewing 7 results - 1 through 7 (of 7 total)

The issue related to '‘JS-errors after Core Update in developer console’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.