Search results

I'm trying to install Onyx using both the one click installer as well as the console installer and both methods only let me choose 12.5.30. Onyx isn't even in the list when run with --all-versions I'm trying to install Onyx on a Debian 8 VM. Any ideas?

Awesome! Exciting times ahead. Here's hoping the upgrades go well.

If I use the --mbox option it doesn't work (picks up 0 spam), but if I remove the option, it picks up the spam just fine.

Many thanks for the reply UFHH01 :)

Awesome. Thank you very much!

I'm running Plesk 12.5.30 on Debian 7 at the moment but would like to eventually be on Debian 8 and Onyx. Looking at it from an in place upgrade point of view (I don't want to build another server then migrate across to it), would it be safer to upgrade to Onyx first, then Debian 8? Or Upgrade...

Spamtrain runs for all mailboxes on the server but often I want to put spam into the spam folder and then run spamtrain for a single mailbox. Is this possible?

I don't mean to be rude but I'll wait thanks. For me it's stability over new features.

Speaking for myself, but I'm sure other people feel the same way too, it's because it's not yet reached late adopter stage yet.

Ok thanks for the replies Igor and serverpoint! Sent from my iPhone using Tapatalk

I just saw the blog post about PHP 7.1 on Onyx. Will there be any plans to support PHP 7.1 on Plesk 12.5.30?

Apologies @cepesh84 I misdiagnosed the problem. It's not caused by multiple roles, it's caused by PHP 7. The problem only seems to happen when the site is configured through Plesk to use PHP 7. If I switch back to the default PHP (5.4), the problem goes away. Here are the errors thrown in...

Found the problem. Wordpress Toolkit is not able to handle Admin users with multiple roles. My user has the roles of administrator and backwpup_admin. As soon as I remove backupwpup_admin, I could scan just fine. I'm assuming this is a bug.

Wordpress Toolkit is having problems getting the admin username of one of my sites when doing a security scan. This is the error it spits out: An error occurred while checking the administrator\'s username on the WordPress installation 'xxxxxxx' I've replaced the sitename in the above error...

Thanks @UFHH01 I think i'm going to have to do what you suggested. It would have been nice if Horde cleaned up itself but it is what it is. This is what i've settled on which should handle other tmp files as well: find /tmp -name "*" -atime +30 | xargs rm -f

In my /tmp directory there are hundreds of files named cache_xxxxxxx, some dating back 5 months ago. I figure Horde is leaving these files behind, but is there a way to make Horde cleanup after itself?

I've found a problem with the hover state of all the Dark skins. Sometimes when you hover, the text will become bold, and then will disappear a second later. It seems to happen when the little arrow tab appears to collapse/hide the sidebar. I've captured screenshots to help show you what's...

I'm just glad that even though it's not technically Plesk's problem, they're helping to do something about it.

Many thanks for the official response @NatalyaF @IgorG !

There's a file in /etc/asl named config.dpkg-dist, but i'm not sure if this is a Plesk config or just a generic one that comes with the aum package. I tried cp'ing that file to config but it still throws the error. I'm a bit hesitant to set CONFIGURED="yes" because it specifically says not to...