Content element of other pages rendered
We are currently experiencing a weird state where pages have been deleted but content elements on them where not and they where "assigned" to some Gridelement containers.
What we are seeing in the end is that Gridelements shows these content elements in the frontend within containers even though they actually reside on other pages. The view in the backend looks like expected.
Thus I'd like to suggest to limit the query which retrieves content elements for a container to include the current page ID. This way unrelated content elements are not rendered in Gridelement containers.
#1 Updated by Jo Hasenau over 3 years ago
- Category set to Frontend
- Status changed from New to Accepted
- Assignee set to Jo Hasenau
You should still consider cleaning the database by firing some DELETE queries for elements that reside on another page than their container.
On the other hand you could adjust the pid with an UPDATE query as well.