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
It looks like in the cleanup work the entirely of the _data/path.yml file was wiped out—it now contains just a single reference to the site root '/'. That actually works a lot of places but I noticed it broke some footer links:
in this instance, the "Schedule" link is fine since it gets redirected to the directory index but "attend.html" doesn't exist anymore and breaks. I'll send a PR referencing this & fixing the footer links but I wanted to point out the larger issue because ``{{site.data.path}}` references are littered throughout the code base and probably nonfunctional in a some other places.
The text was updated successfully, but these errors were encountered:
@phette23 If we're always going to have an updated cname, there is no reason to keep {{site.data.path}}, it was a stop-gap while we didn't have the 2016 subdomain last year
It looks like in the cleanup work the entirely of the _data/path.yml file was wiped out—it now contains just a single reference to the site root
'/'
. That actually works a lot of places but I noticed it broke some footer links:in this instance, the "Schedule" link is fine since it gets redirected to the directory index but "attend.html" doesn't exist anymore and breaks. I'll send a PR referencing this & fixing the footer links but I wanted to point out the larger issue because ``{{site.data.path}}` references are littered throughout the code base and probably nonfunctional in a some other places.
The text was updated successfully, but these errors were encountered: