• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

[PPP-526] Hide controls for rejection messages NOT WORKING.

C

CruzMark

Regular Pleskian
I'm running Plesk 12 (installed last week) on a Centos 7 box. I'm running in ISP View, and in the Interface Controls Visibility section I've checked the box for "Hide controls for rejection messages for non-existent mail addresses".

However, when I log in as a subscriber, I can still see those controls.

What am I missing?

Thanks.
 
CruzMark said:
I'm running Plesk 12 (installed last week) on a Centos 7 box. I'm running in ISP View, and in the Interface Controls Visibility section I've checked the box for "Hide controls for rejection messages for non-existent mail addresses".

However, when I log in as a subscriber, I can still see those controls.

What am I missing?

Thanks.
Click to expand...
I just tried to do this on my Plesk 12, CentOS 6.6 box and was able to see them also. Must be a bug in Plesk or something.
 
Yes, bug PPP-526 still not fixed. I have updated this bugreport with your cases. Thanks.
 
So when you say "still not fixed", how long has it been a bug? Where is the bug report list for Plesk? And if it has been a bug for a long time, why not fix the interface to warn admins that it doesn't presently work, until the bug is fixed. Having a feature that is known not to work is frustrating to the admin and just dumb.
 
IgorG said:
Yes, bug PPP-526 still not fixed. I have updated this bugreport with your cases. Thanks.
Click to expand...
18 months on and this *STILL* seems to be a problem in the latest build of Plesk 12.5 (12.5.30 Update #54).

How on earth is it taking so long to fix a trivial bug to disable part of the Plesk interface?

Should we expect this to ever be fixed?
 
You must log in or register to reply here.

Similar threads

jola
Issue Firewall stops working
Replies
7
Views
737
Peter van der Kleij
P
Linulex
Forwarded to devs Service Plans creation not following server rules: controls for non-existent mail are visible
Replies
6
Views
2K
Linulex
Linulex
P
Resolved Upgrade Mariadb 10.3 to 10.6 completes but trying to start MariaDB fails with error "systemctl status mariadb.service" and "journalctl -xe"
Replies
13
Views
2K
PeterK900
P
B
Issue Backup Manager (and migrator) not working after failed inplace upgrade
Replies
6
Views
14K
Kaspar@Plesk
Kaspar@Plesk
K
Resolved [UI][MINOR] Scheduled Task result detail model dialog box has no closing controls
Replies
7
Views
2K
Peter Debik
P
Back
Top