On chrome for linux and windows all of a sudden users are getting this error. This has been verified by several staff as well.
Access to script at 'https://unpkg.com/lodash-es@4.17.21/debounce.js' from origin (my website) has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Chrome AI's suggeted fix:
Configure CORS on the server (if you control it): If you have control over the server hosting the Lodash library (which is unlikely in this case since it's a public CDN), you could configure it to include the Access-Control-Allow-Origin header in its responses. For example, setting it to Access-Control-Allow-Origin: * would allow access from any origin, though for security reasons it's better to specify your origin explicitly (e.g. Access-Control-Allow-Origin: https://admin.humanesources.com). Since you do not control unpkg.com this solution does not apply to your situation.
On chrome for linux and windows all of a sudden users are getting this error. This has been verified by several staff as well.
Access to script at 'https://unpkg.com/lodash-es@4.17.21/debounce.js' from origin (my website) has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Chrome AI's suggeted fix:
Configure CORS on the server (if you control it): If you have control over the server hosting the Lodash library (which is unlikely in this case since it's a public CDN), you could configure it to include the Access-Control-Allow-Origin header in its responses. For example, setting it to Access-Control-Allow-Origin: * would allow access from any origin, though for security reasons it's better to specify your origin explicitly (e.g. Access-Control-Allow-Origin: https://admin.humanesources.com). Since you do not control unpkg.com this solution does not apply to your situation.