WPIntell

Source evidence

JS Error

Sticky Block for Gutenberg Editor · support · 2023-07-26T17:27:00+00:00

mixedsentiment
mediumseverity
0.78relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Kevin Bickel resolved
I am seeing a JS error that causes other JS on the page to not render. Here is the error: Uncaught ReferenceError: o is not defined Screenshot with context of the error: May be of note: I am using Autoptimize to combine and minify JS Hey @kevin-b Autoptimize (and other optimizers/combiners) are sometimes a bit too aggressive when it comes to reducing code, which can result in errors (for example, when a variable from one function is renamed and that new name already exists in another function). Do you see any similar errors with the Sticky Block plugin when you don’t have Autoptimize enabled? Also, would you mind try and see if replacing the content from /dist/sticky-block.min.js with the contents from this slightly modified file helps? This reply was modified 2 years, 10 months ago by Senff - a11n . This reply was modified 2 years, 10 months ago by Senff - a11n . This reply was modified 2 years, 10 months ago by Senff - a11n . pro-tip; you can disable Autoptimize on a per-request basis by adding ?ao_noptimize=1 to the URL. if the problem is not there at that point, some autoptimize (re-)configuration might be needed to fix this. there are troubleshooting tips and info on how to exclude in the AO FAQ . hope this helps debugging, frank (ao dev) Thank you both for the timely responses! @senff I replaced the JS with your modified code. That did get rid of the original error, but two others appeared: @optimizingmatters I added that parameter to the URL and that did indeed make the page work properly, so I’ll dive into excluding this file from optimizing. Thanks again!

Comments

3 shown
Senff – a11n 2023-07-27T12:40:00+00:00

Hey @kevin-b Autoptimize (and other optimizers/combiners) are sometimes a bit too aggressive when it comes to reducing code, which can result in errors (for example, when a variable from one function is renamed and that new name already exists in another function). Do you see any similar errors with the Sticky Block plugin when you don’t have Autoptimize enabled? Also, would you mind try and see if replacing the content from /dist/sticky-block.min.js with the contents from this slightly modified file helps? This reply was modified 2 years, 10 months ago by Senff - a11n . This reply was modified 2 years, 10 months ago by Senff - a11n . This reply was modified 2 years, 10 months ago by Senff - a11n .

Optimizing Matters 2023-07-27T13:11:00+00:00

pro-tip; you can disable Autoptimize on a per-request basis by adding ?ao_noptimize=1 to the URL. if the problem is not there at that point, some autoptimize (re-)configuration might be needed to fix this. there are troubleshooting tips and info on how to exclude in the AO FAQ . hope this helps debugging, frank (ao dev)

Kevin Bickel 2023-07-31T18:08:00+00:00

Thank you both for the timely responses! @senff I replaced the JS with your modified code. That did get rid of the original error, but two others appeared: @optimizingmatters I added that parameter to the URL and that did indeed make the page work properly, so I’ll dive into excluding this file from optimizing. Thanks again!