Facebook
Twitter
Username:
TITLE
[UI][MINOR] Scheduled Task model dialog box show literal HTML entities of special characters
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS 7.9
Plesk 18.0.48
PROBLEM DESCRIPTION
The Scheduled Tasks model dialog box which show details about failed tasks shows literal HTML entities of special characters in the command. As can be observed in the image below the special characters used in the command are converted to HTML entities and also shown as such. Which makes it difficult to read the actual command in the
model dialog box (and may cause confusion with users).
STEPS TO REPRODUCE
1) Go to Tools & Settings > Scheduled Tasks and click the Add task button.
2) Create a task with a command that created an error. For example I used
3) Click the Run Now button, observe the task fails and click the See details link in the Toaster box which opens the model dialog box.
4) Notice how in the model dialog box the command is shown as mysqldump foo > dump.sql because the > character is shown a the literal HTML entity.
ACTUAL RESULT
Special characters in command shown as literal HTML entity.
EXPECTED RESULT
Conversion of special characters to a readable format.
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
[UI][MINOR] Scheduled Task model dialog box show literal HTML entities of special characters
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS 7.9
Plesk 18.0.48
PROBLEM DESCRIPTION
The Scheduled Tasks model dialog box which show details about failed tasks shows literal HTML entities of special characters in the command. As can be observed in the image below the special characters used in the command are converted to HTML entities and also shown as such. Which makes it difficult to read the actual command in the
model dialog box (and may cause confusion with users).
STEPS TO REPRODUCE
1) Go to Tools & Settings > Scheduled Tasks and click the Add task button.
2) Create a task with a command that created an error. For example I used
mysqldump foo > dump.sql.3) Click the Run Now button, observe the task fails and click the See details link in the Toaster box which opens the model dialog box.
4) Notice how in the model dialog box the command is shown as mysqldump foo > dump.sql because the > character is shown a the literal HTML entity.
ACTUAL RESULT
Special characters in command shown as literal HTML entity.
EXPECTED RESULT
Conversion of special characters to a readable format.
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug