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

[Bug is confirmed: EXTPLESK-3973] Path to document root is no longer generated when you add a new subdomain

Maarten.

Golden Pleskian
Plesk Guru
Username:

TITLE


Path to document root is no longer generated when you add a new subdomain

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 8.6 (Sky Tiger)
Plesk Obsidian 18.0.46 Update #1

PROBLEM DESCRIPTION

When you add a new subdomain, the document root is no longer generated.
The browser console shows this error:

Code:
Uncaught TypeError: EventTarget.dispatchEvent: Argument 1 does not implement interface Event.
    handleDomainNameChange add-subdomain line 521 > injectedScript:141
    a helpers.js:74
    d try catch.js:185
    y instrument.js:458
    <anonymous> add-subdomain line 521 > injectedScript:145
    <anonymous> add-subdomain line 521 > injectedScript:144
    <anonymous> add-subdomain line 521 > injectedScript:151
    <anonymous> add-subdomain:521
    <anonymous> add-subdomain:521

STEPS TO REPRODUCE

- Go to a subscription
- Add a new subdomain
- Enter the name of the subdomain

ACTUAL RESULT

The document root field is empty

EXPECTED RESULT

A proposed document root

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
That's odd. I've tried Firefox and Chrome (latest versions) on macOS, and they both have the same issue.
Even in private/incognito mode without any add-ons.
 
No worries, I think that when you post an issue here it is very likely a real issue and worth a detailed examination. I just wanted to give feedback what the situation is on our servers here. I hope this can be sorted out.
 
Fixed in the extension htaccess to nginx:
1.1.2 (03 October 2022)
The extension no longer produces errors in the console and does not block auto-filling of the "Docroot" field. (EXTPLESK-3973)
 
Back
Top