Originally Posted by Karl
I agree that Hsphere did this really well. We are in the process of dumping Hsphere for cPanel but the way cPanel handles the domains are confusing clients and our tech support.
I am also second guessing myself every time I add a addon domain in cPanel and every time I go into a clients account that has 20+ addon domains and have to hunt for files.
I would love to see this new way implemented here soon.
While I support the concept of having each cpanel account handle many domains which are configurable to act as normal, addon or parked I do not see the current setup as a fault as when it comes down to it, this kind of functionality is what reseller accounts were designed around.
Tony Kammerer - Senior Admin, United Communications Ltd.
Proudly hosting over 50,000 customer websites since 1998!
Our lively customer community with over 70,000 posts!
It seems this idea has become fairly well formed and solidified. I am preparing a report to present to our development team about this desired functionality. Please take a few moments to review this report and ensure it accurately reflects the functionality desired:
---
True Multi-Domain Support
The goal of the paradigm of True Multi-Domain Support is to eliminate the concept of a "main domain" along with the concept of "addon domains." Instead, the True Multi-Domain paradigm is of a hosting account that can have several domains, all having equal capabilities.
In the True Multi-Domain Paradigm:
- Any domain can be parked on any other domain in an account
- Adding a domain DOES NOT also result in a subdomain being created
- Any domain can be assigned a static IP
- Because any domain can be assigned a static IP, multiple SSL certificates can exist in a single hosting account
In this paradigm, the recommended file path for a domain is /home/user/service/domain (e.g. /home/davidg/public_html/example.com). This helps keep things simple for novices (no accidental deleting of email in an attempt to clean up files). Also, when a new novice logs in via FTP or WebDisk, they see a list of their domains and it is intuitive to "place their web page on their web site" rather than trying to figure out what different services do. Also, this would be consistent with current design (/home/user/mail).
When this system is implemented, file paths for existing accounts should not change. The new recommended file paths should only apply to new domains. As with the current system, the recommended file paths are merely recommendations, customizable by the account holder.
Regarding migrations from remote servers, the easier path is to simply keep everything intact and not change directory structures to forcefully fit this new paradigm once this functionality is implemented.
Implicit in this request is the ability to change the docroot of a domain without having to remove/re-add the domain. Multiple domains should be permitted to serve content from the same docroot.
The functionality of changing a domain's docroot could also serve as a basis for a "migrate to new paradigm" utility to optionally and automatically handle changing the docroot of a domain and moving of files to fit this new paradigm. However, the user would be responsible for ensuring their scripts are fixed to accommodate the new file locations. A very obvious warning should be displayed to users in this "migrate to new paradigm" utility warning customers that this will likely break scripts they currently use and they are responsible for ensuring the scripts are corrected after the migration. This should be an option in Feature Manager so it can be enabled/disabled similar to the Advanced DNS Zone Editor.
Greetings all,
I have filed this report with our developers and they have some questions about expectations about how this functionality will affect current aspects of cPanel/WHM. If you can share your expectations about the following, that would help us implement this functionality as desired:
--
Clarification: should domain parking be limited to parking on domains hosted on the server and owned by the account?By "Any domain can be assigned a static IP" does that include Parked domains?How would True Multi-Domain capability affect the following tweak settings:
- Allow users to park subdomains of the server’s hostname main domain.
- Allow domain parking across accounts
- Allow Remote Domains
What should happen in this scenario?
1. User parks parkedexample.com on example.com
2. Then, User parks example.net on parkedexample.com
3. Then, User deletes parkedexample.com
4. Optionally: User then parks parkedexample.com on example.net
I'm going to compare cPanel to DreamHost's panel.
/http://awesomebox.net/img/cpanel/dh1.png
See how every domain (parked, redirect, etc) is treated equally in one list? This is just so much more practical. Now lets look at users:
/http://awesomebox.net/img/cpanel/dh2.png
DH lets you associate different domains with different users, this allows for more freedom. Again, so much nicer.
cPanel is fine, really, if you just have one website. But once you have more than a few under one account, it can get really annoying to navigate. For example, all your MySQL databases are prefixed with your main site's name, this causes me confusion.
The only practical way to deal with multiple websites with a cPanel host is to buy a reseller account so you can have one cPanel per website, but reseller accounts can get expensive.
My two cents.
Last edited by Infopro; 07-30-2010 at 04:45 AM.
Rename the term to "mirror" or something. When I think of parking, I think of Sedo and NameDrive.Clarification: should domain parking be limited to parking on domains hosted on the server and owned by the account?
And yes.
Only fully hosted, parked seems impractical.By "Any domain can be assigned a static IP" does that include Parked domains?
Only allow them to park over domains in their account.Allow users to park subdomains of the server’s hostname main domain.
No, unless you want to add a toggle to WHM.Allow domain parking across accounts
What?Allow Remote Domains
In the table of domains on the user's account, there should be a column that says "Fully Hosted" or "Parked". Subdomains should be treated the same as "Fully Hosted" because they're just domains. Is a co.cc domain a subdomain or no?User parks parkedexample.com on example.com
Then, User parks example.net on parkedexample.com
On the "Park a domain" page, user can only park on top of Fully Hosted domains.Optionally: User then parks parkedexample.com on example.net
Just my two cents.
IMO, this will solve the issue with .htaccess parsing for add-on domains which we had for a long time before getting the option to host an add-on domain "out of the public_html" directory in WHM Tweaks.
Also, what would be the impact of this on Subdomain? If they are being created in /home/user/service/domain/subdir (e.g. /home/davidg/public_html/example.com/clients for clients.example.com), this will again have the same issue for people trying to use the subdomains as a completely separate entity/site (similar to google.com and mail.google.com).
It's better to discuss on this before any development progresses --
/home/davidg/public_html/example.com/clients
/home/davidg/public_html/clients.example.com
Which of these will suit the most?
With later one --
1. You can have separate .htaccess for the subdomain, no hierarchy
2. An IP can be assigned to a subdomain in the similar way to a domain (given, the internals of cPanel treats them that way). It was also a demanding feature some time ago
Thanks,
Vijay
The discussion you reference was about defaults. In this paradigm, users will retain the ability to have files stored anywhere within their cPanel account.
Regarding subdomains, some have come to expect something.example.com to be accessible via example.com/something. More experienced web designers are aware of this and may prefer to not have this - hence the option to store data where you want to store it, rather than being forced to store it in a directory of the domain the subdomain belongs to.
I think we should do one thing at a time. However, there has been much discussion that we should make it easier to move domains from one account to another. I think it'd be a great idea for us to have a feature request thread for that so we can have a more formal discussion about getting that done.
As of version 11.25.1, the database prefixing is optional. This can be opted out of via a setting in Tweak Settings. However, once you opt-out, you cannot downgrade to a version of cPanel/WHM that did require this prefixing.
This is an issue that moving to this paradigm will resolve.
A remote domain is when a domain is added to a cPanel account, but all the DNS for that domain is edited to point to another server.
In the context of cPanel/WHM, example.co.cc would be considered a domain and .co.cc would be considered a TLD. I realize we're stretching technical/formal definitions a bit though with regards to these type of TLDs.
Friendly Moderator Note
Due to the similar nature of the discussion a different thread has been merged into the feature request for true multi-domain support in cPanel. The other thread was titled "Change IP in additional domains" of which that narrow request is included within the larger goal of true multi-domain support in cPanel.
cPResources: Submit a Support Request - Submit a Bug Report - Review existing Tickets
- Support Options - Extra Support Options - Documentation - Mailing Lists - Latest cPanel Builds
- cPanel.net Site Search - Documentation Search - Forums Search - Forums Advanced Search
-- Donald cPanelDon Holl - Analyst, cPanel Quality Assurance
Important cPanel/WHM Version Number Designation Change
Please Note: Important cPanel/WHM Version Number Designation Change
As of July 28, 2010 the cPanel/WHM version number designations have been officially changed.
Version 11.25.1 is now designated 11.28 and version 11.25.2 is now designated 11.30.
These new changes were explained in some detail recently at the July 2010 - Quarterly Road map - Webinar direct from cPanel's PodCast Studio in Houston, Texas with speakers David Grega and Mario Rodriguez.
An official press release about these changes is forthcoming and can be accessed at this link as soon as it's made available to the Forum Team:
Important cPanel/WHM Version Number Designation Change (To be updated)
This post serves to update users who are subscribed to threads (where this message is posted) looking forward to upcoming enhancements in future versions of cPanel.
I looked at the slides and the progress but didn't see any information about this topic? Did I miss something or what? I am still waiting for this to be done. It's really confusing/time consuming trying to clean up files in people's account because it's not organized and it looks sloppy.
I am also getting clients that are complaining when they find out you can go to http://maindomain.com/addondomain.com and get the addon site especially when they have nothing to do with each other...
Last edited by midwestkel; 07-30-2010 at 04:29 PM.
There is not yet an ETA for this functionality nor is this on the roadmap for version 11.28.
Is there a chance of it making the 11.30 ? or is the 11.30 already planned in advance ?
Do you have a goal about how often new updates will be released ? (3, 6 or 12 months …)
LinkBack URL
About LinkBacks
