• 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!
  • 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.

Input Suggest to add date to KB articles

Bitpalast

Plesk addicted!
Plesk Guru
Often the relevancy of KB article content cannot clearly be identified, e.g. articles say "known bug, will be fixed in future updates", but then never get updates, so even "old" bugs that have been fixed are listed as "will be fixed in future updates".

It would be helpful if the KB articles had a date to them when they were written, maye even a marker whether they are still current.
 
According to @SunRabbit (person, responsible for KB articles), they are going to do this work in the near future.
 
Actually, the information about article creation and last modification dates is available on the special informational panel for every KB (the panel could be hidden though, press on "<" in the very right part of the screen to unhide it):
KB_dates.png


But in any case your point is absolutely valid - we need to review our processes in order to keep the information in KBs about existing bugs and their status up-to-date.
 
Back
Top