# Companion page-bundle HTML files not being copied to subfolder of output directory anymore
**URL:** \
**Category:** support\
**Tags:** v0-123-x\
**Created:** [February 26, 2024, 4:19am UTC](https://discourse.gohugo.io/t/companion-page-bundle-html-files-not-being-copied-to-subfolder-of-output-directory-anymore/48502 "2024-02-26T04:19:10Z")\
**Posts on this page:** 3\
**Page:** 1
in `content/opinions/peribreakpoints`, I have the following files:
```auto
after.html
before.html
index.md
peribreakpoints-after-dark.png
peribreakpoints-after-dark.webp
peribreakpoints-after-light.png
peribreakpoints-after-light.webp
peribreakpoints-before-dark.png
peribreakpoints-before-dark.webp
peribreakpoints-before-light.png
peribreakpoints-before-light.webp
```
Normally, everything shows up on the site, including after.html and before.html. However, after running `hugo` for the first time in a long time, `after.html` and `before.html` aren’t getting copied to the directory where they usually get copied to anymore. This means that people who visit those pages are getting 404s now.
This is what `hugo version` gets me:
```auto
hugo v0.123.3-a75a659f6fc0cb3a52b2b2ba666a81f79a459376+extended darwin/arm64 BuildDate=2024-02-23T17:09:20Z VendorInfo=brew
```
In `index.md`, I’m using the simplest links in my Markdown file that could possibly work — ``. It’s in a ``, so it’s not like I can use a Markdown-style link:
```html
```
I had a look at [Build options | Hugo](https://gohugo.io/content-management/build-options/) and I don’t appear to need any special build settings to reenable this sort of behavior. I don’t have a `build` thing in my YAML front matter, and the default for `publishResources` is `true`, anyway. I also had a look at [Page resources | Hugo](https://gohugo.io/content-management/page-resources/) and it’s not obvious that I’ve missed something.
…does anyone have any idea why `after.html` and `before.html` aren’t getting copied to `public/` like they used to?
Thanks in advance.
---
TLDR: The new behavior is expected/as-designed.
### Example
Let’s use the following example to see the difference between v0.122.0 and v0.123.0.
```plaintext
content/
└── p1/
├── a.jpg
├── b.html
├── c.md
└── index.md
```
#### v0.122.0 (incorrect)
| | Available as a page resource | Published (copied to public) |
| --- | --- | --- |
| content/p1/a.jpg | ✔ | ✔ |
| content/p1/b.html | ✔ | ✔ |
| content/p1/c.md | ✔ | ❌ |
#### v0.123.0 (correct)
| | Available as a page resource | Published (copied to public) |
| --- | --- | --- |
| content/p1/a.jpg | ✔ | ✔ |
| content/p1/b.html | ✔ | ❌ |
| content/p1/c.md | ✔ | ❌ |
### Explanation
In v0.122.0 and earlier we inconsistently handled page resources with [`ResourceType`](https://gohugo.io/methods/resource/resourcetype/) = `page`. As shown in the v0.122.0 example above, we did not copy c.md, but we did copy b.html. That inconsistent behavior was fixed in v0.123.0.
I understand that some site authors took advantage of this inconsistent and undocumented behavior to blindly copy HTML files when building the site. That, obviously, is no longer possible. Here are your options going forward.
#### Option A – Use the static directory
```plaintext
static/
└── p1/
└── b.html
```
#### Option B – Use the Publish method
layouts/\_default/single.html
1) This will publish all page resources with [`ResourceType`](https://gohugo.io/methods/resource/resourcetype/) = `page`.
```plaintext
{{ range .Resources.ByType "page" }}
{{ $publishPath := urls.JoinPath $.RelPermalink .Name }}
{{ (.Content | resources.FromString $publishPath).Publish }}
{{ end }}
```
2) This will publish all page resources with an `html` extension:
```plaintext
{{ range .Resources.Match "**.html" }}
{{ $publishPath := urls.JoinPath $.RelPermalink .Name }}
{{ (.Content | resources.FromString $publishPath).Publish }}
{{ end }}
```
---
