• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by mikeeeeeeeeeeeeeee

  1. M

    when creatinng default skin package -> custom.css is blank

    @ Lev: I'll rework this and follow best practice, thanks for the help! @ whytefyre: I did use "default" also and it does generate a package but the custom.css is blank also. This is, from what I understand above, default and expected behaviour for Plesk 12.5 ...? Cheers all
  2. M

    when creatinng default skin package -> custom.css is blank

    Hi Kate, Thanks for the reply! I am indeed using version 12.5... I should have specified. The documentation link you provided definitely details version 12.5 specifics better than the 12.5 advanced administration guide that I used... Through some head banging, I actually went to...
  3. M

    when creatinng default skin package -> custom.css is blank

    a quick update... this is strange.. listed themes as 'Default' but it cannot be packaged... [root@]# plesk bin server_pref -sl Skins installed: Default [root@]# plesk bin branding_theme -p -name Default -vendor admin -destination /tmp/Default.zip Skin with name Default was not found on...
  4. M

    when creatinng default skin package -> custom.css is blank

    Hi all, I'm trying to create a custom skin by editing some css components but when I follow the instructions at: http://download1.parallels.com/Plesk/Doc/en-US/online/plesk-themes-guide/ when creating creating the default skin package it successfully completes, however, the custom.css is...
See more
Back
Top