Ticket #2284 (assigned malfunction)
The sub-domains and domain aliasses are still active if the parent domain is disabled
| Reported by: | nuxwin | Owned by: | benedikt |
|---|---|---|---|
| Priority: | normal | Milestone: | ispCP ω 1.1.0 |
| Component: | Frontend (GUI) | Version: | ispCP ω 1.0.5 |
| Severity: | Medium | Keywords: | |
| Cc: |
Description (last modified by nuxwin) (diff)
IspCP 1.0.4 has introduced a new layout for domains that are disabled. Some bugs found after 1.0.4 release have been fixed in 1.0.5 but a new problem was found : all subdomains linked to one disabled domain are still active. It's the same for all domain aliasses.
We should review this stuff and take decision on what should be disabled or not when the parent domain is disabled.
If we considere the parent domain as an unique entity (customer account) and then, this domain was been disabled because the customer was not respected him contract, we should disable all objects (subdomain, aliasses) linked to the parent domain.
In a other view, if we considere a domain name as a real domain name where the user account is an separate object, in this case, we should provide API to allow disable of all objects one by one (aliasses, subdomains..) linked to one domain name.
What do you think about this ?
Change History
comment:2 Changed 2 years ago by TheCry
My opinion is, if a customer not respect his contract, i want to disable all objects of him. This is the best way to make him clear, that he has to respect his contract!
comment:4 Changed 23 months ago by benedikt
this ticket and #2141 seem to be duplicates. I will check this.
comment:5 Changed 23 months ago by benedikt
- Owner set to benedikt
- Status changed from new to assigned
comment:6 Changed 22 months ago by benedikt
- Summary changed from The Subdomains and the domain aliasses still actives when a parent domain is disabled to The sub-domains and domain aliasses are still active if the parent domain is disabled
comment:7 Changed 16 months ago by benedikt
- Owner benedikt deleted
- Status changed from assigned to new
I won't have the time to fix this ticket before RC2 Release. Therefore, I release it.
