404 on Collection Page

Publishing help Project settings
1

I’ve got a collection that suddenly broken after an asset compression and republish yesterday. All the pages inside that collection are yielding a 404. This has been up and running for over a year. Here’s what I’ve noticed:

  • Both staging and prod return 404
  • New items published using new slug to collection - OK
  • Deleting and re-adding to same slug does not work
  • Password protection on page still shows 404
  • Restored multiple backups prior to noticing issue - still showed 404

I saw the 404 issue last week, and saw it come back after their fix was deployed. This feels similar, but nothing seemed to be reported on status page.

2

Hi there!

For Collection pages showing 404 errors while new items work correctly, let’s first verify the publish settings since this is often the root cause of selective 404 errors:

  1. Go to the Pages panel
  2. Hover over the ‘templates’ Collection template page and click the settings “cog”
  3. Go to Publish settings
  4. Verify the toggle is “on”

Since new items with new slugs are working, the issue might be related to cached or outdated URLs. Make sure that the slugs in your Collection items match the URLs you’re trying to access. You can check this by viewing your Collection items in the CMS and comparing their slugs to the URLs showing 404 errors.

Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.

3

I didn’t see anything obvious, basically;

  • Make sure the collection page is published, under the collection page settings. You could try turning that off, publish, turn it on, republish…
  • Make sure the collection items are published individually.

At a glance those both looked correct, so I’d guess something deeper and contact support.

4

Thx for taking the time, Michael - I tried toggling the template page publish option and republishing, but that didn’t change anything. I have a ticket open, but no response. It’s been 24 hrs… hopefully they can get to it soon.

5

Hopefully, I suspect there are still home hosting issues happening that might relate to the problems that occurred a few days ago.

6

This was finally resolved by engineering with a deployment. The issue had to do with Hubspot form integration. I was binding some of the hidden fields to collection fields to pass data back to Hubspot. In doing so, it creates invalid HTML. It worked before, but broke recently b/c they tightened up the threshold for how much invalid HTML to allow. I believe it should’ve failed gracefully instead of creating 404s, but something to watch out for if you’re using Hubspot forms and hidden fields.

7

That’s new, are you referring to an app integration?
Or invalid HTML in the rendered collection page itself which failed at server side rendering during the CMS merge?