Skip to content
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

Term page with build options not handled correctory #12058

Closed
jmooring opened this issue Feb 18, 2024 · 1 comment · Fixed by #12060
Closed

Term page with build options not handled correctory #12058

jmooring opened this issue Feb 18, 2024 · 1 comment · Fixed by #12060

Comments

@jmooring
Copy link
Member

This is essentially the same as #12055, but with build options instead of the draft flag.

This test (the file content part) fails:

func TestFoo(t *testing.T) {
	t.Parallel()

	files := `
-- layouts/index.html --
|{{ len site.Taxonomies.tags }}|
-- content/p1.md --
---
title: p1
tags: [a]
---
-- content/tags/a/_index.md --
---
title: tag-a-title-override
build:
  render: never
  list: never
---

  `

	b := hugolib.Test(t, files)

	b.AssertFileContent("public/index.html", "|0|")
	b.AssertFileExists("public/tags/a/index.html", false)
}

To me, these should be equivalent:

content/tags/tag-a/_index.md

+++
title = 'My Tag A'
draft = true
+++
+++
title = 'My Tag A'
[build]
render = 'never'
list = 'never'
+++

In both cases (a) the page should not be published, and (b) the term should not be a member of the "tags" taxonomy object.

bep added a commit to bep/hugo that referenced this issue Feb 18, 2024
@bep bep removed the NeedsTriage label Feb 18, 2024
@bep bep added this to the v0.123.0 milestone Feb 18, 2024
bep added a commit to bep/hugo that referenced this issue Feb 18, 2024
bep added a commit to bep/hugo that referenced this issue Feb 18, 2024
bep added a commit to bep/hugo that referenced this issue Feb 18, 2024
bep added a commit that referenced this issue Feb 18, 2024
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants