Custom folder in child theme should be recognised whether named WC or CC

[ghost]

Describe the current situation
An existing site may have a woocommerce folder set up in a child theme for custom versions of some of the files. If this is changed to be named classic-commerce it is not recognised. So this folder currently still needs to be called woocommerce, even when using CC.

Additional context
It's a good idea that the woocommerce folder is recognised so as not to break existing sites that already have this folder in place. But anyone setting it up from scratch would probably call it classic-commerce. Can it be set up to to recognise either of them?

[timbocode]

This requires a small change to function template_path() in includes/class-woocommerce.php as shown in this gist:

https://gist.github.com/timbocode/62b21ea425a48375ea4db2e94b6eba40

This will first look for the existence of directory theme-name/classic-commerce. If that exists, it is set as the template path ( WC()->template_path() ). If theme-name/woocommerce exists, it is ignored.

If theme-name/classic-commerce does not exist, theme-name/woocommerce is set as the template path if it exists.

This does mean that the user cannot have both theme-name/classic-commerce and theme-name/woocommerce in use at the same time but I personally think that's best anyway otherwise things could get a tad messy.

I think theme-name/woocommerce should be for legacy installations only and that we encourage the use of theme-name/classic-commerce.

Thoughts?

[bahiirwa]

Agree with approach. Yes, either....or... is neat.

[ghost]

I think theme-name/woocommerce should be for legacy installations only and that we encourage the use of theme-name/classic-commerce.

Yes, that's what I think as well. That solution seems perfect to me.

[timbocode]

OK, I'll do a PR.