This is my dev environment with the latest commit (06b9d396):

They’re in a different place on mine :confused:

(Also 06b9d39662cdb0768d91829db2120adfd1f420c7)

wait, what? that shouldn’t be there.

it looks like something in the layout broke.

looks like something related to OTP, maybe a non-default auth plugin causes this?

e: your specific issue is a layout bug related to using an authenticator which doesn’t provide an ability to change passwords

https://git.tt-rss.org/fox/tt-rss/commit/5b6d9cee2957c1d41288d31aada1edb826db1916

Same with only the auth_internal plugin and the latest commit (5b6d9cee2).

  • Firefox 70 on Fedora
  • Microsoft Edge on Windows

I forgot to mention all users are concerned (my ldap unprivileged user and my admin internal user)

Also i don’t know if it’s relevant the webserver is an nginx 1.14 and they are another nginx 1.14 as a TLS reverse proxy

have the layout fixed itself on update? post a new screenshot of the entire prefs screen.

e: also check for preference key/values in ttrss_user_prefs database table. going by your first screenshot it looks like everything is missing other than the API one.

i.e. select * from ttrss_user_prefs where pref_name = 'USER_CSS_THEME'

user 1 is the admin account, and 4 is the user account :
ttrss_pgdb=# select * from ttrss_user_prefs where pref_name = ‘USER_CSS_THEME’;
4 | USER_CSS_THEME | | light.css
1 | USER_CSS_THEME | | default.php

all user switch between night and day template whatever the value are here
screenshot is coming

This screenshot is from Microsoft Edge on Windows

post a screenshot of an entire browser window. don’t cut out things.

are the other prefs sections there? what’s with the huge white empty space above the authentication panel?

are you making this harder than necessary on purpose? use chrome, take a screenshot of an entire window, don’t cut or blank shit out, etc.

here’s how this should look on edge (at default settings) on windows 10. note how there’s no huge empty space or broken layout.

e: alright, huge blank space looks like an edge-specific issue which happens sometimes when opening preferences in a really tiny window. see, this is why using obscure browsers nobody cares about simply adds to the overall confusion.

Ok, sorry let’s restart on my main client setup firefox 70 on windows 10 in private mode local admin user :

This screenshot is without any plugin other than auth_internal
I dont have/use Chrome

Sorry for the confusion with shitty edge

interesting. other preferences are there so it’s probably not database-related. so it’s just language, timezone and theme / user CSS which are not shown for some reason.

i’m not sure what could cause broken layout in that particular area, maybe a strange theme filename in themes / themes.local? i.e. something with a quote sign. ← i’ve tested with some weird filenames and couldn’t break it, unfortunately.

# ls -1 themes.local/
feedmei
feedmei.css
feedmei+.css
feedmei_night.css
feedmei+_night.css

even after removing all files the problem is still present

yeah, i’ve tried with those filenames and it didn’t break anything.

i think at this point you should dump and PM me the database, maybe that’ll help. i’m out of other ideas.

the structure ? because the database is 2 or 3 Go
3,9G ./postgres/data/

Registered Tue, Dec 10 2013 - 14:56
Subscribed feeds count 139
Stored articles 669932

Did you think it could be related to nginx and or phpfpm as you said the database was not in fault ?

# git status
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	modified:   cache/upload/.empty
#	modified:   feed-icons/index.html
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	g2ttrss-mobile/
no changes added to commit (use "git add" and/or "git commit -a")

Same thing afer removing g2ttrss-mobile

the structure won’t help i’m afraid. i’m not sure if a dump would help at all tbh.

you can try this to reduce the size:

  1. pg_dump your actual tt-rss database
  2. load the dump in a temporary different database
  3. delete from ttrss_entries cascade
  4. dump the resulting much smaller dataset

anything is possible but it’s extremely unlikely that fpm or nginx has something to do with it (unless you’re modifying returned HTML with it by using something like ngx_http_sub_module``).

Ok i will do that during the day, also i have plan to review my configuration of the 2 nginx
thx