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

Issue with directory-based archetypes in theme #5318

Closed
gcushen opened this Issue Oct 15, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@gcushen

gcushen commented Oct 15, 2018

I have followed the instructions in the limited documentation on the new dir-based archetypes in order to support it in the Academic theme, however am receiving the error:

Error: stat WEBSITE_FOLDER/themes/academic/archetypes/archetypes/publication/index.md: no such file or directory

when running the following command from WEBSITE_FOLDER with Hugo v0.49/extended darwin/amd64:

hugo new --kind post post/XYZ

For some reason Hugo is looking for archetypes/archetypes/ instead of simply archetypes/.

The code can be found here: https://github.com/gcushen/hugo-academic/tree/master/archetypes/post

Any ideas?

Thanks!

@gcushen gcushen changed the title from Possible bug with dir-based archetypes? to Bug with directory-based archetypes Oct 15, 2018

@bep bep added the Bug label Oct 16, 2018

@bep bep added this to the v0.50 milestone Oct 16, 2018

@bep

This comment has been minimized.

Member

bep commented Oct 16, 2018

I suspect this to be a "theme issue" -- I assume if you put the archetype dir in the project.

@bep bep changed the title from Bug with directory-based archetypes to Issue with directory-based archetypes in theme Oct 16, 2018

@bep bep self-assigned this Oct 26, 2018

bep added a commit to bep/hugo that referenced this issue Oct 26, 2018

bep added a commit to bep/hugo that referenced this issue Oct 26, 2018

bep added a commit to bep/hugo that referenced this issue Oct 26, 2018

@bep bep closed this in #5358 Oct 26, 2018

bep added a commit that referenced this issue Oct 26, 2018

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