Hello,
It’s strange that protected details page doesn’t show the right records, while the unprotected one with same content does in my Next-gen app. This started to happen recently for some strange reason, I believe this is a bug.
Can someone address this issue please?
Thanks
You might want to provide a little more info. When you say protected do you mean with a login? What type of issues are you seeing … what varies between the page with a login vs that without?
Thanks LeighBerre96926 to reply!
The login protected page doesn’t show the correct details from a listview as opposed to a non-protected public page, where all details are correct. This means that when one click on a details view button on the login protected page, the child page displays other than the connected content of that specific record. I wouldn’t say it has got to do with the login option, but somehow a bug occurs. I have tried to redo the structure, but unfortunately it didn’t solve the problem. The details page simply picks up a random value (richtext field and connected fields values) for the parent page where it is being called from.
Now, when I’m just trying it again, it seems to be working all fine. Could be a temporary issue with the backend I assume, which I hope will be steady in the future. I’m on EU servers and might be related to it.
Seems odd, so hopefully it was a glitch.
Yes, it is, and very frustrating. When I set the page to be modal, it shows the correct record, but if I leave it non-modal. the page again shows the wrong data. I think this is something cache keeps the first opened record to be rendered all over again, whereas the modal option refreshes something that can get the right data.
I have tried it with other browsers, the problem still persist for the non-modal child page views.
@Attila - I’d recommend raising a support ticket if you can replicate the issue. @Kara have you heard of this issue?
Update - Kara replied to me directly and asked that you raise a support ticket as this is not something that the product team have seen.
Thanks @CarlHolmes for contributing on this!
I have raised ticket and they were able to replicate the issue. As I have the same page one for public and one admin as private page, they explained that I should either change link for the public one or delete it. But slugs are and were different, so I’m confused, and also don’t want to delete any of them, as public needs to look at services while admin should be able to manage them, as it was perfectly fine under classic builder. I don’t understand what has changed since.
Same data sets of pages one for public and one behind login is not possible anymore?! 
Just an update on this, Knack has confirmed that it’s a bug and they are working on it to resolve.
Good catch @Attila. I’ve got an engineer working on it. It’s a pretty unusual edge case that most users won’t run into, we’ll keep you posted on progress.
Cheers,
Kara
Hello Kara,
Thank you to address this problem!
In my opinion this scenario and workflow is quite common amongst Knacksters and should be a critical function of Knack to be able to build backend at the same time for public showing adjusted data at the front.
Thanks, Attila
Kara via Knack Community Forum <notifications@knack.discoursemail.com> ezt írta (időpont: 2025. nov. 18., K 19:22):