Components in wrong context

Wappler Version : 7.1.2
Operating System :
Server Model:
Database Type:
Hosting Type:

Expected behavior

An element (in this case a Page Flow) should always be found in the proper context (either dmx.app.data OR dmx.app.data.content)

Actual behavior

In a rare, but consistently reproducible, use case, the component moves from dmx.app.data to dmx.app.data.content

How to reproduce

First let's search the entire project looking for a possible duplication of component. You can see here the component is found only once, on the layout, so the expectation is that it will be found at dmx.app.data. That flow is only called from one place, also shown below.

Screenshot 2025-07-31 at 3.21.01 PM

And indeed when most content pages are loaded, it does register properly.

Screenshot 2025-07-31 at 3.12.40 PM

However when one page loads meal_plan the context moves to .content.

Screenshot 2025-07-31 at 3.13.33 PM

So far I can only reproduce this on one particular content page (the same layout is used throughout), so I am assuming I am doing something unique on this page that is causing this. Attached is the content page and a partial that could be involved.

Archive.zip (14.0 KB)

Please check if this is not caused by the unclosed script tag at the end of the page?

<script src="/js/posthog_content_footer.js" defer="true">

Teodor for the win! Nice catch, thanks.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.