New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symbolic link error shown but link as root folder is followed and works #1855

Closed
seffw opened this Issue Feb 13, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@seffw

seffw commented Feb 13, 2016

In Windows 7 x64, created symlink content in Hugo source folder to content_src which contained content to be generated.

Hugo throws error on build: 'Symbolic links not supported'. However the content from content_src is generated as normal (so in this case, symobilic links work).

Solution: remove error when symbolic link is a root folder, leave it as-is for all other cas

@bep

This comment has been minimized.

Show comment
Hide comment
@bep

bep Feb 14, 2016

Member

Just tested this on OS X, and I get the error ... but I also don't get the content created. I believe we could make this work, but I cannot see how it could right now, even on Windows ....

Member

bep commented Feb 14, 2016

Just tested this on OS X, and I get the error ... but I also don't get the content created. I believe we could make this work, but I cannot see how it could right now, even on Windows ....

@seffw

This comment has been minimized.

Show comment
Hide comment
@seffw

seffw Feb 14, 2016

I was pretty carefult in testing. I put the word symlink in the content of a content_src folder, and then created a symlink content to that folder. This was built by Hugo, with the error shown, and with the content generated.

Unless Hugo took the content from content_src ? Is this possible? Using the word 'content' in this folder name was probably not the best idea.

I'll test again with the content_src with a different name and location.

seffw commented Feb 14, 2016

I was pretty carefult in testing. I put the word symlink in the content of a content_src folder, and then created a symlink content to that folder. This was built by Hugo, with the error shown, and with the content generated.

Unless Hugo took the content from content_src ? Is this possible? Using the word 'content' in this folder name was probably not the best idea.

I'll test again with the content_src with a different name and location.

@bep

This comment has been minimized.

Show comment
Hide comment
@bep

bep Feb 14, 2016

Member

It doesn't really matter -- the pull request that is referenced to this issue should fix this issue for both you and me.

Member

bep commented Feb 14, 2016

It doesn't really matter -- the pull request that is referenced to this issue should fix this issue for both you and me.

bep added a commit to bep/hugo that referenced this issue Feb 14, 2016

Add support for symbolic links for content, layout, static, theme
Note: This is for the content roots only, but that should satisfy most needs.

Fixes gohugoio#1855

@spf13 spf13 closed this in e5aa477 Mar 21, 2016

tychoish added a commit to tychoish/hugo that referenced this issue Aug 13, 2017

Add support for symbolic links for content, layout, static, theme
Note: This is for the content roots only, but that should satisfy most needs.

Fixes gohugoio#1855
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment