Repeated Header in a Next.js page using iframe and BBPress
A user is experiencing issues with their Next.js website that integrates BBPress. After registering and logging in, the page displays two navigation bars due to an iframe nesting problem. The user is seeking assistance to resolve the bug and has found a temporary workaround by refreshing the browser.
- ▪The user's website is built using Next.js and BBPress.
- ▪After a user logs in, the page shows two navigation bars due to an iframe issue.
- ▪The user has attempted various fixes but is still facing the problem.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48232545 |
| Publication time | Fri, 22 May 2026 06:04:50 +0000 |
| Retrieval time | 2026-05-22T06:32:00.835Z |
| Last seen | 2026-05-22T06:32:04.858Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | keolrJlSF0un |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
I am new to the tech stack of this issue. I am new to Next.JS and I am new to BBPress. But this is the tech stack of my "WEC MFG" website, https://excellencematter.net. My page.tsx for the interaction menu option has the <iframe> which contains the bbpress functionality.Now, here is the bug. After a new user account is registered and the new user logs in, the web page is a mess. It looks as if the iframe nests an entire website so that it produces a look where the whole webpage has two navigation bars. I hope I am describing this accurately. Please view the screen shot.I have done some work with adding "snippets", custom pages and "Additional CSS". But so far the problem has been resistant to my efforts. I need help.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.