When updating from 1.17.3.1 to 2.0.20: Child theme breaks

Well .. your 1.x child theme is never going to work with 2.x, exactly like it wouldn’t work with a completely different theme.
Which actually is the case, considering that CC2 is an almost complete rewrite ??

So, yes, if you insist on using that specific child theme, you need to stick to the last available 1.7 version.

The other option would be to scrap that child theme and build a completely new one, using the few hints given over there: https://themekraft.usability-idealist.de/cc2/howto/child_themes

(thats part of the documentation which is currently work-in-progress ;))

Thou one has to take note: In most cases, using a child theme is obsolete, because there is this all new & fancy Color Scheme system, which solves about 90% of all the shortcomings with colors and stuff AND is update-proof as well ??

cu, w0lf.

Thank you for your reply. It appears that, for now, we’ll have to stay on 1.17 then ??

Do you know if the 1.x branch still gets updates should compatibility with future upgrades of WordPress break? Or is it abandoned as EOL?

If you need to revert back out of any reason, you can safely go back to the premium version and get a free update to the 1.x version as a 1.x farewell present ??

The CC 1.x version is available on Github! From now on its up to the community to update it if needed and keep it working.

We want to focus 100% on the current theme (ie. CC 2) and thus say goodbye with a big THANK to 1.x! Custom Community was a great success and we believe that CC 2 is going to follow up onto this fantastic road and become even more successful.

resolved

Was there no way that V2 of this theme couldn’t have been on a separate branch?

Nearly anyone that’s created a child theme and hits update is going to have a broken website.

Just tried using the CC 1 version on Github but when we preview the theme it works for a second before going blank. Like it’s doing a licence check and finding we don’t have one – which we don’t as we were using the free version.

What can we do?

there are no license checks in cc1. do you have a link.

CC1 was build based on the first BuddyPress default theme architecture and this is not supported any more. we needed to rebuilt it. We didn’t have an other choice…

Also the review guidelines ask us to remove all features which could become plugins…

Sent me a link and I take a look.

Like the OP, my site was completely destroyed by clicking “update” in Custom Community. Anyway, I downloaded a site backup from two days prior, and I overwrote all of the files (so I thought?) yet the site is still messed up. It’s back to 1.17.3.1, but all of my customization is gone. I am not sure how this could have happened after restoring? I must not know where CC1 “stored” its configuration files (color settings, font settings, header and footer settings, etc.). What would I have to upload from my old site to get it looking identical again?

Thanks!! ??

Hi @chriscrowder,

all options are saved serialised in the option “custom_community_theme_options”. We do not delete or modifier this option.

If you use the latest 1.x free or pro you should be back to normal.

I hope that helps you
Sven

Hi @svenl77

I appreciate it. This is located in the cheezcap.php file, correct? I uploaded my old one to site\homedir\public_html\wp-content\themes\custom-community\admin and overwrote it, and the site is still broken looking. What could I be doing wrong?

Thanks for any help, mate! ??

It seems as though whatever I changed in the “Theme Settings” area is lost, even though I am overwriting all of my old files for Custom Community 1? This is in the section where you choose the header image, width of the page, color of fonts, etc.

With an old backup of my site, what file do I need to find so I can restore those settings?