Feature Requests
Share ideas, discuss and vote on requests from other users in community
 

The option to use a theme for front end and theme for client area

Sam R shared this idea 3 months ago
Under Consideration

Would love to have the option in which whmcs would allow a template for the frontend (site) and the option to choose a template for the client area other than the frontend of needed

Comments (3)

photo
1

Not sure what you mean by this. Your site's front end is entirely separate from WHMCS's client area. You can use any of the WHMCS theme's assets in the front end, independently of the theme you've chosen for the client area.

photo
1

Hi

What I mean if you have already the front end running a theme for WHMCS, and you want to use for client area one of these client area themes now you are stuck, you would either have to convert your frontend whmcs theme into anything else to be able to use the client area theme

So I would like to have the option to be able to use a whmcs theme for front end and another for the portal (client are end) each differently

photo
1

I'm not really following.

If you've a front-end site using say WordPress or plain HTML, it has its own stylesheets and design. It's totally independent of whmcs.

If you want your client area to look like your front end then you've got the option to do that by changing the header and footer and the CSS in the templates all the way through to modifying templates to match the front end. That's usually the easiest way with the least amount of changes required whenever whmcs is updated. The least change to whmcs templates the better IME.

You could, in theory, use the CSS, layout etc from whmcs in your front end site. That's relatively easy with plain HTML and a bit more complex with WordPress as you'd be creating a WordPress theme from scratch. The concern is that whmcs uses quite ugly templates and outdated bootstrap V3 so your front end ends up ugly too.

As far as I can tell, all the third party themes for whmcs that include front end site designs on themeforest use the approach of a WordPress/HTML front end using Bootstrap v4 and a mostly minimally changed WHMCS theme using Bootstrap v3 for the client area. Usually it's just a CSS file and edits to header.tpl & footer.tpl. The reason being that WHMCS has embedded HTML that is Bootstrap v3 specific...but that's another argument entirely.

photo