This repository has been archived by the owner on Feb 19, 2022. It is now read-only.
Fixed blog link #105
Closed
Fixed blog link #105
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
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.
Hello!
This small bug was found during making my gitfolio with blog link.
There was a problem with link from user's info to the blog. If this link hasn't got http/https prefix, your template gives domain prefix and page becomes 404.
For example, my github contains blog link to emdobro.ru without https. After publishing this link became to betchika99.github.io/emdobro.ru, that isn't correct.
My fix isn't very beautiful maybe, but it works and GitHub has the same solving for this problem. I just add prefix
http://to user's blog link. If user's nginx works correctly, domains with https prefix will be caught tooHope to be useful! See you! And thanks for this good theme :)