Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] v-change-domain-owner ---> Error: Target domain doesn't belong to the new user #4345

Open
DeRaja opened this issue Apr 1, 2024 · 0 comments
Labels
feature New feature or request

Comments

@DeRaja
Copy link

DeRaja commented Apr 1, 2024

Describe the bug

I want to move a domain under user A to user B.

Currently this domain under user A is having custom root mapped to maindomain.com.

Because the maindomain.com is not moved, the v-change-domain-owner throws an error.

Tell us how to replicate the bug

One can repeat the bug by doing the following:

Map the ownerA---->domain.com--->/customroot>>>maindomain.com

v-change-domain-owner domain.com ownerB

---> Error: Target domain doesn't belong to the new user

Thus, a modification of the Line 60 of this script if [ -n "$CUSTOM_DOCROOT" ]; then is required.

Here a message is better that the $CUSTOM_DOCROOT does not exists at the target location and should be manually created.

Currently it throws an error because the custom root is a maindomain.com that does not exists under the new user because - logically the maindomain.com is not moved.

@DeRaja DeRaja added the feature New feature or request label Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant