[BUG] Payloadcms.com

[viperxeyes]

Describe the Bug

Well , I was showing a client around payload , and i visited the website https://payloadcms.com and when I navigated to Blog section I got the client side error on your official website which was a little embarrassing , I know it is not something with payload functionality but you guys should fix your Blogs page , also the scroll down before going bag to blog posts from a blog is something should be looked into.

Link to the code that reproduces this issue

None

Reproduction Steps

visit https://payloadcms.com/posts/blog , go to any Blog and use the browser back button , not the "Back button" on the blog page itself , after some going back and force and noticeably after the scroll down effect that happens the app breaks

Which area(s) are affected? (Select all that apply)

Not sure

Environment Info

None

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload