Forwarded to devs SSL It! - inconsistent Let’s Encrypt branding

[pleskuser67553]

Username:

TITLE

SSL It! - inconsistent Let’s Encrypt branding

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.55_build1800230919.07 os_RedHat el8, AlmaLinux 8.8, Intel Xeon Processor (Skylake, IBRS) (2 core(s))

PROBLEM DESCRIPTION

Let’s Encrypt brand is represented in the Plesk UI and email notifications in a variety of ways (text enlarged for legibility):

• Logo with curly apostrophe (or closing single quote mark): Let’s Encrypt
• Text with straight apostrophe: Let's Encrypt
• Text without apostrophe: Lets Encrypt
• Text with back tick: Let`s Encrypt

STEPS TO REPRODUCE

Open SSL It! extension, observe in the Certificate Authority column "Let`s Encrypt" (text with back tick) and in the Certificate Name column "Lets Encrypt" (text without apostrophe).

Open the SSL It! settings panel, observe "Let's Encrypt" (text with straight apostrophe).

Click on a secured domain in the Domain Name column. On the next screen, observe "Let’s Encrypt" (logo with curly apostrophe) and "Lets Encrypt" (text without apostrophe) in the Certificate Name.

Check a recent email notification from Plesk about a certificate renewal, observe "Let`s Encrypt" (text with back tick) in the subject and body text. Observe "Lets Encrypt" (text without apostrophe) also in the body text. It is not possible to amend the email template myself, since the vendor and certificate name strings are variable in these templates.

Search for "encrypt" from the main search bar in Plesk. Observe "Let's Encrypt" (text with straight apostrophe) in Extension Name.

Search for "encrypt" in the Extensions catalogue. Observe "Let's Encrypt" (text with straight apostrophe).

ACTUAL RESULT

EXPECTED RESULT

Only expecting to see text or logo with curly apostrophe.

Let’s Encrypt

ANY ADDITIONAL INFORMATION

I appreciate this is low priority stuff, but nevertheless important to properly represent a brand and I believe consistency improves trust

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Peter Debik]

Thank you, forwarded as PPS-15176. The different spellings probably result from the fact that the screen display is created from different sources such as two different extensions and a language string database for translations. Further tracked as PPPM-14194, PPP-63141.

 

[AYamshanov]

Hi guys, it is already known issue with bug id EXTLETSENC-1186.
Unfortunately, fixing the problem is not as simple as replacing one symbol with another in Plesk (and related extensions) locales.