Community theme update

[Havouza]

As I understand it, updating to the new theme will overwrite all css changes done, also in module css files. Am I right?

[lesley]

That is correct.

[Havouza]

And 1.0.2 will also make that update?

[lesley]

Correct. You can always back your css files up and replace them after the upgrade. We included the css editor in the backend to solve some of these issues with updating themes.

[Havouza]

but if I copy the theme folder, rename it and upload it again as another theme? Will that work

[lesley]

You would need to create a new installer for the theme, but that could work. You can also cherry pick, like if you know you have edited the global.css file you can just grab the updates from it, there has not been too much added, https://github.com/thirtybees/community-theme-default/commits/1.0.x/css/global.css

[Havouza]

I know there is much added in the modules css also. So then I will keep it as it is. No update in the near future

[lesley]

Yeah, there is. The benefit of having the more semantic html was worth the change though, it should help with SEO.

[Havouza]

The site work as it is so its no need to update and risk loosing all the hours

[dynambee]

@Havouza said in Community theme update:

but if I copy the theme folder, rename it and upload it again as another theme? Will that work

@lesley said in Community theme update:

You would need to create a new installer for the theme, but that could work.

Wouldn't this work?

1. Create a copy of the theme folder with a new folder name.
2. Go to the back office (Preferences --> Themes) and choose "add a new theme"
3. Choose "Create a new theme"
4. Give the new theme a name and set the theme directory name to be the what was created in #1 above.

I think this is how it was done in PS 1.6, no? Did something change?

[lesley]

It would work, but you would have the same issue with the custom css.

[Havouza]

The PS modell tp clone a theme is NOT a good idea. ou will end up with a LOT of work if you do. changed settings, enabled and disabled modules etc etc. I have done all that now so I hope the changes I have made to the theme is now protected when updating to 1.0.2

[Jeff]

I just tried to update the theme but I get a "Bad Configuration File" error when I try.

I have tried uploading the zip file in the back end and also tried SFTP on Cloudways. (which I am new to)

[lesley]

Did you upload it over the current theme?

[Jeff]

@lesley No current theme is intact.

[Jeff]

@mdekker

I see what you mean now. No it does not have a Config.xml file.

[Jeff]

I think I see my problem. I uploaded a 3rd party free theme and it works fine. The 3rd party theme has a modules folder, a themes folder, and a separate Config file.

The community theme default just has a folder called "community-theme-default-1.0.1" with no separate config file.

I wasn't aware that the community theme cannot be installed using the "add a theme" in the backend. I'll just hold off updating the community theme for now.

[Jeff]

@mdekker Deleted my initial reply. No there is no Config.xml file. I was looking at the config file inside the folder.

[lesley]

When I download the theme zip I can see the config.xml file, maybe you did not get it uploaded to your server.

[Jeff]

@lesley Where is the best place to download from? The only link I could find was in the blog post about the update.

[alwayspaws]

@lesley I really think we should have one main place for all downloads. It's becoming difficult to know what to download from where.

[lesley]

You can download the zip from the github release page, then extract the files, then upload them over your current theme via ftp, https://github.com/thirtybees/community-theme-default/releases/tag/1.0.1

[alwayspaws]

Would new users know this? No! :)

[Jeff]

@alwayspaws Yeah I am a new user. Never used PS either. And I am new to Cloudways as well. Very early on the learning curve. its killing me. lol

[lesley]

That is almost word for word what is in the blog post page. I will try to make it clearer.