cPanel temporary domain for customers
We have since a long time been using a temporary domain for customers to use freely as they see fit.
The whole point of temporary domains is to let the user see their content in an easy way before they point their real domain to their new account (and without allowing userdir).
After 11.40 we have seen a few problems. Not sure if it was a change in 11.40 or something else. Either way, here is our suggestion.Allow a set of domains to act as "temporary domains" on each server. From this list of domain, users are allowed to use subdomains for parked or addon domains as they see fit.The idea is to allow this for a list of domains that acts as a "whitelist" from the tweak setting "Allow domain parking across accounts".An option of automaticly adding a parked domain of a newly created domain should also be availible in tweak settings.Example:User buys a cPanel account with the domain example.net.The temporary domain set up by the web host is example.com.The suggested automaticly added parked domain would then be: example.net.example.com.If the user wants to use more domains, he/she would the be able to add anything that is free based on <subdoman>.example.com.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Hello,
What about the option to allow users to create subdomains based on the server's hostname ? When .htaccess rewrites are needed for tempory site URL's this is how we do it.
The whole ~/username method should have been abandoned a long time ago, creating on the hostname allows user's quota and stats to be checked properly and could also be used with a wildcard SSL to allow customers to have a shared SSL like with the current system that uses https hostname/~username
Hello,
What about the option to allow users to create subdomains based on the server's hostname ? When .htaccess rewrites are needed for tempory site URL's this is how we do it.
The whole ~/username method should have been abandoned a long time ago, creating on the hostname allows user's quota and stats to be checked properly and could also be used with a wildcard SSL to allow customers to have a shared SSL like with the current system that uses https hostname/~username
Third party web developers and consultants often ask us about getting a "temporary URL" while they publish their site in development on our server before they point the A record over. We just tell them that cPanel does not have that feature available at this time. Using a subdomain does not solve the issue primarily because most sites are Wordpress sites and Wordpress requires an explicit URL to be set (e.g. the Home and SiteURL parameters in the Wordpress dashboard/database). At this time there is no solution for us to provide a temporary URL. monarobase mentioned a possible solution above, but it wasn't clear if monarobase actually implements that or how to do so.
Third party web developers and consultants often ask us about getting a "temporary URL" while they publish their site in development on our server before they point the A record over. We just tell them that cPanel does not have that feature available at this time. Using a subdomain does not solve the issue primarily because most sites are Wordpress sites and Wordpress requires an explicit URL to be set (e.g. the Home and SiteURL parameters in the Wordpress dashboard/database). At this time there is no solution for us to provide a temporary URL. monarobase mentioned a possible solution above, but it wasn't clear if monarobase actually implements that or how to do so.
As a web design and hosting provider im frustrated that they is not a simple option, to make matters worse I use WordPress when I exclude a domain from mod_userdir all im getting is "not supported".
As a web design and hosting provider im frustrated that they is not a simple option, to make matters worse I use WordPress when I exclude a domain from mod_userdir all im getting is "not supported".
Replies have been locked on this page!