my siteUrl is https://foo.gitlab.io, my assetsPref...
# chatd
d1onys1us
09/07/2022, 1:46 AMmy siteUrl is https://foo.gitlab.io, my assetsPrefix is /some/path/indeed . when i publish, the images are correctly resolved from foo.gitlab.io/some/path/indeed/ , but on my local published site, the assets are not available from that path, they are only available from localhost:3000/ .
should i make my siteUrl https://foo.gitlab.io/some/path/indeed ?
also, on the local site the favicon resolves, but the logo does not. the reverse is true for the published site (no favicon, but logo resolves). the paths are the siteFaviconPath is set to notes/assets/images/favicon.ico and the logoPath is set to notes/assets/images/logo.svg
they resolve to 404 -> localhost:3000/some/path/indeed/assets/logo.svg (weird that it doesnt include /images), and 404 -> https://foo.gitlab.io/favicon.ico (weird that it neither respects siteFaviconPath nor assetsPrefix, but maybe it just never found it in the first place to place it here in the next.js bundle).
k
kevins8
09/07/2022, 2:14 AMi think this is on our end. will look into this
kevins8
09/12/2022, 3:54 AMokay, reporting back on this - these are all issues on our end.
us showing the local image with asset prefix is a bug on our end - have created an item for it to be fixed in an upcoming release.
for the logo, it doesn't resolve for the same bug as above.
for the favicon, we don't handle the asset prefix case. have also created an item for this. will fix all of this before end of the month!
d
d1onys1us
09/12/2022, 5:22 AMso great to hear, big thanks!
2 Views