There are some issues with the update.

Home Forums Jevelin Theme There are some issues with the update.

Home Forums Jevelin Theme There are some issues with the update.

Viewing 8 posts - 21 through 28 (of 28 total)
  • Author
    RESOLVED Posts
  • Sorry…

    I have updated all the content in the production environment to the latest.

    So, I tried to change the “Custom Code” of “Jevelin Setting”, but it did not complete successfully.

    As shown in the attachment, the modal will be white.

    Attachments:
    You must be logged in to view attached files.

    I logged into your website to test it and it worked fine for me as shown in the attached screenshot.

     

    Could you please test it by clearing your browser cache and using a different browser?

    Attachments:
    You must be logged in to view attached files.

    Would you please log in to this page and try it out?

    I can not access the shared page as I am getting a “403 Forbidden” error.

    It has improved. Would you please try again?

    Now I am getting “500 Internal Server Error”.

    I made a mistake…(:-\

    Would you please try again?

    I could log into your website and confirmed the issue.

     

    The issue occurs because of the below javascript code that you have added in the theme settings.

     

    (function(d) {
            var config= {
                kitId: 'hlc8zvz',
                scriptTimeout: 3000,
                async: true
            }
    
            ,
            h=d.documentElement, t=setTimeout(function() {
                    h.className=h.className.replace(/\bwf-loading\b/g, "")+" wf-inactive";
                }
    
                , config.scriptTimeout), tk=d.createElement("script"), f=false, s=d.getElementsByTagName("script")[0], a; h.className+=" wf-loading"; tk.src='https://use.typekit.net/'+config.kitId+'.js'; tk.async=true; tk.onload=tk.onreadystatechange=function() {
                a=this.readyState; if(f||a&&a !="complete"&&a !="loaded")return; f=true; clearTimeout(t); try {
                    Typekit.load(config)
                }
    
                catch(e) {}
            }
    
            ; s.parentNode.insertBefore(tk, s)
        }
    
    )(document);
    
    

    There can be an issue in the above javascript code so please resolve it as other javascript code works fine there.

Viewing 8 posts - 21 through 28 (of 28 total)