• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue How to permanently hide/collapse website log check panel

pleskuser67553

Basic Pleskian
Server operating system version
CentOS Linux 7.9 and AlmaLinux 8.9
Plesk version and microupdate number
Plesk Obsidian Version 18.0.59 Update #2
Is there a way in Panel.ini or settings to permanently hide or collapse the UI panel that appears at the top of the website logs? I find I'm collapsing it manually 99% of times that I go to look at website logs in Plesk. It does not stay collapsed the next time I go into website logs (i.e. apparently not storing a preference in cookies). It takes up way too much space on the screen.

When I do collapse it using the chevron button, it's necessary to click the UI 'Refresh' button, or temporarily resize the browser viewport with dev tools, to force the log area to fill the remaining part of the screen. The log area should, at the very least, resize when the chevron button is clicked please.

I know I can hide it in my browser with chrome/userContent.css (which might be my last resort).

And I know I can disable the feature altogether in Panel.ini with this:

INI:
[websitesDiagnostic]
enabled = false

But I don't want that yet - I'm still evaluating whether it's a useful feature (mostly producing false positives for my use cases - needs some granular options for ignore this and that, and more history in the charts).

Example: log checking enabled via its UI in Tools & Settings > Assistance and Troubleshooting > Website Log Check
1710931709425.png


Example: log checking disabled via its UI
1710931778127.png
 
I reversed the CSS 'logic' in my userContent.css, for anyone interested

CSS:
@-moz-document regexp(".*:8443/smb/log-file/browser/.*") { /*{}*/
    .pul-panel--expanded .pul-panel__content { display: none ! important; }
    .pul-panel--collapsed .pul-panel__content { display: block ! important; }
}
 
Edit (above regexp was too greedy):

CSS:
@-moz-document regexp(".+?:8443/smb/log-file/browser/.*") { /*{}*/
    .pul-panel--expanded .pul-panel__content { display: none ! important; }
    .pul-panel--collapsed .pul-panel__content { display: block ! important; }
}
 
I had to make the CSS selectors a bit more specific because it was catching other panels around the Plesk UI in situations when the page was not a full browser load, but JavaScript load (e.g. location changed with the History API). And thus, the regex can be more broad.

CSS:
@-moz-document regexp(".+?:8443/.*") { /*{}*/
    .content-wrapper:has(#log-browser) .pul-panel--expanded .pul-panel__content { display: none ! important; }
    .content-wrapper:has(#log-browser) .pul-panel--collapsed .pul-panel__content { display: block ! important; }
}
 
Back
Top