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
This may be a non-goal of this (excellent) project, but for documentation's sake: the use of URLs relative to the root directory for the CSS and JS files break any fork that is not serving from the root directory. By default with Github, a fork of this repo would live at USERNAME.github.io/njyoon.github.io, and those links will look for e.g. the javascript files at USERNAME.github.io/js/ instead of USERNAME.github.io/njyoon.github.io/js/.
The quick fix I found is removing the leading slash from the src attributes in index.html, nyt.html, and pdf.html. I don't know if there are other knock-on effects but that seemed to work for me.
Incidentally, I forked this to comment out the puz checksum check because some upstream bug produces a checksum mismatch in certain files with lots of circled squares, but I can't figure out exactly what the issue is. I'm going to try to track it down and report it upstream, but in the meantime, I think you could plausibly skip the checksum check or change the error it throws to a console warning.
The text was updated successfully, but these errors were encountered:
This may be a non-goal of this (excellent) project, but for documentation's sake: the use of URLs relative to the root directory for the CSS and JS files break any fork that is not serving from the root directory. By default with Github, a fork of this repo would live at USERNAME.github.io/njyoon.github.io, and those links will look for e.g. the javascript files at
USERNAME.github.io/js/
instead ofUSERNAME.github.io/njyoon.github.io/js/
.The quick fix I found is removing the leading slash from the
src
attributes inindex.html
,nyt.html
, andpdf.html
. I don't know if there are other knock-on effects but that seemed to work for me.Incidentally, I forked this to comment out the puz checksum check because some upstream bug produces a checksum mismatch in certain files with lots of circled squares, but I can't figure out exactly what the issue is. I'm going to try to track it down and report it upstream, but in the meantime, I think you could plausibly skip the checksum check or change the error it throws to a console warning.
The text was updated successfully, but these errors were encountered: