• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Obsidian 18.0.24 and again the CSS is different…

M

Martin.B

Plesk Certified Professional
Plesk Certified Professional
I'm a bit frustrated currently… I just installed the new Update to 18.0.24 on one of our systems and had to realize, that our company's skin is broken… again! :mad:

What's up with the plesk developers/designers?
Previously we had a skin, which worked perfectly in Plesk 17. It looked always the same, from the first 17.0 versions, up to the last 17.8 ones, never had we take care of updates breaking the skin.
But since the upgrade to Obsidian, with every release, they seem to change the naming or the use of the CSS classes, which require updates to the skin. And since the Skins don't even have an automatic update mechanism, it's a lot of work to deploy them to all our systems.o_O

Is it even wished anymore, that people create their own skins?
 
DM?

I already edited the skin for the new version…
The element, which was the class .page-sidebar-wrapper in the previous version became .pul-layout__sidebar-inner in the new one… just had to add the class to the CSS. But why is it even necessary to change the classes with each version?
 
I am much more annoyed that I have to check and re-adjust our custom templates every couple weeks now.
Before v18 these only changed with major releases, but now they do also with minor
 
It's basically the same situation, like with the skins…

It would be really nice, if the Skins contained some sort of auto-update mechanism. Like providing a download-URL inside of the meta.xml and with every update, the installer checks if there is a newer version available. This way it would still require manual adjustments, but at least would save the hassle of deploying the new version of the skin to all the systems.
 
Today(?) the version 18.0.26 was released, and what should I say? It's the same situation again!

Are custom skins even welcome? :(
 
You must log in or register to reply here.

Similar threads

M
Resolved Webmail Broken After Update to 18.0.61.5
Replies
7
Views
2K
MacGyver
M
learning_curve
Resolved Permissions on some of the files packaged by Plesk are incorrect[ERROR] - Post 18.0.69 Upgrade
Replies
19
Views
971
learning_curve
learning_curve
P
Multiple instances of .wp-toolkit when smart update is activated
Replies
1
Views
2K
Kaspar@Plesk
Kaspar@Plesk
C
Issue Backup takes very long and slows down entire server
Replies
4
Views
2K
ciB
C
S
Resolved Dovecot Broken After Latest Update
Replies
4
Views
2K
scpcomp
S
Back
Top