• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved [UI] TTL value of the previous opened record in the Zone Record Template is shown on next record

Kaspar

API expert
Plesk Guru
Username:

TITLE


[UI] TTL value of the previous opened record in the Zone Record Template is shown on next record

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 7
Plesk 18.0.50 update 2

PROBLEM DESCRIPTION

This is a minor UI bug. The TTL value of the previous opened record is shown when updating the TTL value for the next record in the Zone Record Template which does not yet have any TTL value (TTL value is empty).

STEPS TO REPRODUCE

This only occurs on records who do not have a TTL value yet (i.e, the TTL value is empty).

1) Go tool & settings > DNS settings
2) Click on a record that already has a TTL value, or if non of the records has a TTL value, click on a record and first set a TTL value.
3) Click on any other record that has no TTL value
4) Notice how the record already has a TTL value, with a similar value as the previous record, in the input field.
(Clicking the OK button does not save the value).

ACTUAL RESULT

The TTL input field shows TTL value of previously look at record (when clicking on the record to edit)

EXPECTED RESULT

The TTL input field should be empty when clicking a record to edit on which no TTL value has been set yet.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Last edited:
Back
Top