Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Queries table forgets setting for Show ... entries #3252

Open
el-ephant opened this issue Feb 23, 2025 · 4 comments · Fixed by #3253
Open

Queries table forgets setting for Show ... entries #3252

el-ephant opened this issue Feb 23, 2025 · 4 comments · Fixed by #3253

Comments

@el-ephant
Copy link

In V5, the Show ... entries value in the Queries Table remained until the cookies were deleted, while in V6 this value is automatically reset to the default value of 10 after some time. In the Network table and the Adlist table, the set value remains saved.

Is this behavior intentional?

Core version is v6.0.3 (Latest: v6.0.3)
Web version is v6.0.1 (Latest: v6.0.1)
FTL version is v6.0.2 (Latest: v6.0.2)

@rdwebdesign
Copy link
Member

rdwebdesign commented Feb 23, 2025

These settings are created and controlled by datatables plugin.

We didn't change the behavior (at least not intentionally). We only updated the plugin.

Which browser are you using?
Are you able to replicate the issue if you access the web interface using a different browser? or from a different device?

@el-ephant
Copy link
Author

I am using Safari on macOS and iOS. I also tried it with Google Chrome on macOS now, with the same result. The value is reset to the default value after about 3 minutes (again, only in the Queries table, not in the Network table).

My webserver.session.timeout value is 2592000.

@yubiuser
Copy link
Member

This is a bug. I'll fix it.

@rdwebdesign
Copy link
Member

Ohhh...

v6 code was initially created years ago, without the stateDuration: 0 option.

After that (but still a long time ago), the option was introduced in v5, but never in v6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants