You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, we found a global issue with wrong image paths.
This issue happens even when the extension is installed, but is not enabled because of missing integration for a website:
So the root issue:
the extension adds styles to a page even if an integration for a website is missing
when styles are added, we can see that for each image there are 2 places where its path is defined:
in these added styles, and the issue there is that an image path is relative to the website domain, so, for example, the path looks like https://example.com/assets/images/arrow-light-mode.png. Such paths don't work!
also as inline styles, the path there is correct and references the extension path and this variant works
What does it cause?:
we use LogRocket to capture sessions for users
LogRocket has an internal bot that parses the content of a page, extracts asset URL's from it, and tries to pre-cache them
because this extension always pre-adds styles to a page, the LogRocket bot finds them and tries to fetch these resources, of course, it can't do it, so the bot gets a 404 error and on our side, we're getting the 404 error in our logs.
So what can be done on the extension side?
don't add styles to a page when the extension does not work on a web site, i.e. the integration for a website is missing
fix image URL's in added styles or remove them at all, because anyway URL's from inline styles are used.
The text was updated successfully, but these errors were encountered:
Hello, we found a global issue with wrong image paths.
This issue happens even when the extension is installed, but is not enabled because of missing integration for a website:
So the root issue:
https://example.com/assets/images/arrow-light-mode.png
. Such paths don't work!What does it cause?:
So what can be done on the extension side?
The text was updated successfully, but these errors were encountered: