Solved Issue with Evolution-Standard skin/theme not displaying user-level information correctly

Serg951

Verified User
Joined
Apr 1, 2022
Messages
12
I am facing a peculiar problem, it seems that the quota/disk/bandwidth information that should be displayed is simply blank, without any information.

To clarify, two screenshots: In one, the information is displayed correctly (on the right side) in the other, the page simply remains blank.

I eliminated the possibility of it being due to some browser cache, for example, by testing in an incognito window in different browsers and also on different networks.

I will also attach some more screenshots with information that may be relevant.
 

Attachments

  • incorrect.png
    incorrect.png
    35.8 KB · Views: 5
  • correct.png
    correct.png
    53.6 KB · Views: 5
  • Skins.png
    Skins.png
    50 KB · Views: 5
  • DAVersion.png
    DAVersion.png
    62.4 KB · Views: 5
May you check browser's console to see if any errors are seen there?
 
Thanks for the feedback.

Yes, I was comparing it with other servers and there are some very strange reports that only occur on this server. I'll send you the prints.

Something peculiar is that the only theme in which this doesn't occur is "Refreshed", which I'll also send you the print.
 

Attachments

  • consolept4.png
    consolept4.png
    110.4 KB · Views: 3
  • consolept5.png
    consolept5.png
    104.4 KB · Views: 3
  • consolept3.png
    consolept3.png
    112.2 KB · Views: 2
  • consolept2.png
    consolept2.png
    110.3 KB · Views: 3
  • consolept1.png
    consolept1.png
    159.2 KB · Views: 3
  • refreshed.png
    refreshed.png
    93.9 KB · Views: 4
Another detail is that one of my tests was to use the /usr/local/directadmin/data/skins folder from another server where these layouts were working correctly, thinking that it could solve the problem, however, the problem persisted in the same way and I reverted this change .

I've never seen anything like this on some other DirectAdmin servers that I manage, and I haven't even been able to reproduce this same problem on them.
 
Solved in ticket opened with directadmin.

The problem occurred due to the day/month formatting regarding the account creation date in the user configuration file:

grep date_created /usr/local/directadmin/data/users/*/user.conf

Incorrect (sáb ago)
/usr/local/directadmin/data/users/example/user.conf:date_created=sáb ago 20 10:00:33 2022

Fixed (Sat Aug)
/usr/local/directadmin/data/users/example/user.conf:date_created=Sat Aug 20 10:00:33 2022
 
Back
Top