This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Fix broken link to "Sample Procedure for an agency-wide data call" #246
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
haleyvandyck
pushed a commit
that referenced
this pull request
Jan 28, 2014
Fix broken link to "Sample Procedure for an agency-wide data call"
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The link to the "Sample Procedure for an agency-wide data call" page at the bottom of the policy docs page is currently broken.
With the current configuration, Jekyll is actually generating the page as a non-servable file off at: http://project-open-data.github.io/assets/docs/assets/docs/sample_data_call_procedure To fix this, I added a trailing slash to the permalink and also disabled the global
relative_permalinksoption.Disabling relative permalinks is recommend and will be the default in Jekyll 2.0. Although this is a change to a global setting, I did some diffs, and I'm pretty sure this sample data call page is the only page affected by changing that setting (all the other permalink settings are at the root of the project where absolute and relative permalinks would be the same anyway).