Hi guys
After the last update I get a ton of 404 errors in the console especially concerning cs sliders. The site is awfully slow as well.
The sliders do not even load in safari and edge at all.
you cannot connect to cornerstone backend aswell? to edit a page for example?
Well I can, but some javascripts do not work anymore. Otherway it takes ages to load the page, so the js are functional.
Fun fact: when I’m logged in as admin, the cs sliders load and I get jquery migration errors in the console only.
I’m not sure what happened, but it seems to work now, there is a js issue though besides the jquery migration errors in the console. The DOM needs to be completely loaded so the javascript controlling the “konsumenteninfo” close button does work.
it is a off canvas element with a custom attribute, so it loads active/opened and it has to be closed by a click.
OK, I guess I figured out the sluggish response of the “off canvas” element.
This two errors are the reason:
Is there anything I can do about it?
Both errors point to external .js files hosted on google or mailchimp servers?
Pls correct me, if I’m wrong.
It has nothing to do with the google site kit plugin btw. Deactivating this, does not make any difference.
Hey @VRANKOVINA,
Those errors are not coming from Pro and your update issue can’t be replicated. This means that the issue is in your server and/or third-party services.
Kindly test temporarily removing the third-party services in your site and also do a manual update of Pro. That means deleting it and reinstalling a fresh copy.
yes that is what I already figured out. It’s not the theme, but there is still this though:
Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: <div.x-anchor x-anchor-toggle e2-e4 m2-18 m2-19 m2-1a m2-1b m2-7#konsumenteninfo-anchor-toggle>
Ancestor with aria-hidden: <div.x-anchor x-anchor-toggle e2-e4 m2-18 m2-19 m2-1a m2-1b m2-7#konsumenteninfo-anchor-toggle> <div class="x-anchor x-anchor-toggle e2-e4 m2-18 m2-19 m2-1a m2-1b m2-7 x-active" tabindex="0" id="konsumenteninfo-anchor-toggle" role="button" data-x-toggle="1" data-x-toggleable="e2-e4" data-x-toggle-overlay="1" aria-controls="konsumenteninfo-off-canvas" aria-expanded="true" aria-haspopup="true" aria-label="Toggle Off Canvas Content" aria-hidden="false">…flexUnderstand this warning
[Violation] Forced reflow while executing JavaScript took 31ms
this error message comes after clicking on “close”.
Hey @VRANKOVINA,
That one, looks like legitimate concern which we are confirming.
Please stay tuned or check future updates for news of this issue.
Thanks.
Hi @christian
I broke the problems down to two plugins: Google Sitekit and Mailchimp connection. If I deactivate those two things (google is a plugin, mailchimp is a js script in the header), the timeout errors in respect to those two disappear. One thing remains though:
[Violation] 'setTimeout' handler took 112ms jquery.js?ver=3.7.1:3555
[Violation] Forced reflow while executing JavaScript took 90ms
[Violation] Forced reflow while executing JavaScript took 32ms
this is connected to jquery.
One plugin uses outdated jquery scripts, which actually according to developer, should not affect the performance of the site.
are there any issues with this : JQMIGRATE: Migrate is installed with logging active, version 3.4.1?
this looks like the root for the most “violation” warnings.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.