Themes for v6 also working for v7?

[Yzord]

I'm totally new to the WHMCS world, so i have already the v7 installed, but it seems there are not really v7 themes around. Are v6 themes compatible with v7?

[brian!]

v7 was only released on Monday, so many developers will have been waiting until that final release to confirm v7 compatibility.

 

if you take a look in the Marketplace, there are many themes in there that state they're now v7 compatible.

[twhiting9275]

Unfortunately, WHMCS hasn't really been very forthcoming, historically, as to what changes for themes, from version to version. From that perspective, it makes a developer's life harder to work with.

As Brian mentioned, check the marketplace. Don't just take that as the gospel though. Go to the developer's site, browse their releases, and see what they've said in the changelogs.

If you don't see anything new, ask the developer.

I only mention this, because there's a few that haven't exactly made the releases official on marketplace (yet).

[WHMCS Edward]

Unfortunately, WHMCS hasn't really been very forthcoming, historically, as to what changes for themes

 

How so? Template changes are always made available on Github: https://github.com/WHMCS/templates-six/commits/master

[aegisdesign]

To be fair, Github is a relatively recent event if you've been using WHMCS prior to v6.

 

I speak from experience of diff'ing and merging templates from v3 onwards and trying to glean from the release notes what has changed and how it relates to your custom theme branch. When I started, my theme was quite different to the one provided by WHMCS but over the years, having to merge changes into your design, you end up not diverging too much or you're spending days doing an update.

 

IMHO, it'd be much easier if there was a base parent theme for the release and custom themes were merely overrides like Wordpress does child themes or Prestashop does it's themes.

 

ie. you have a support/templates/base/ folder and a support/templates/my_custom_theme folder

 

WHMCS then looks for say header.tpl in my_custom_theme and if there is none, gets it from base.

 

That way, if the auto-updater updates templates, you get the new template updates in base but your custom changes are still used.

 

For a long time WHMCS was stuck on a really old version of bootstrap which meant the themes were using old bootstrap syntax. Merging it in with a site design based on an up to date version was a nightmare.