So let's suppose that'll I'll be adding CSS, chnaging existing CSS etc.

Is it best to do this in the default (aka Curve2) theme

OR  should I make a copy of the default (Curve2) theme and then make all the changes in that copy.

Then set that as the'forum default'


Thoughts? Pros/Cons of each approach.

Well,  I realise you're only changing a bit of css etc, but if anything should go wrong with the default theme your forum won't load, it needs that theme to operate.  The recommended way is to make a copy of default and edit that one.

I always edit the default. BUT....Any file I edit is backed up before I start so if something does go wrong I can revert back quick. The best way though is how Lurkalot said to do it. It's a lot safer that way.

Thanks.

When new versions of SMF are released, are changes made to the theme files?

If so does that mean everything theme wise has to be set up again from scratch?

Yes pretty much. If a big enough upgrade comes than most custom edits have to be done over. If you copy the default theme and customize it and than an upgrade comes, your copied theme does not get updated but the regular default theme does. So, whatever changes where made to template files in the update must be made to the theme you copied manually.

Hmmm is that not the case when edits are made directly to the default?

No edits to the default theme would get over written. Edits to a saved default theme would be saved but the updates that should be in it from the update would not be there. So it would have to be updated.

Quote from: LandyVlad on Feb 09, 2019, 07:56 PMThanks.

When new versions of SMF are released, are changes made to the theme files?

If so does that mean everything theme wise has to be set up again from scratch?

This come with the territory I'm afraid. I mean testing software which isn't finished.  It's the reason you haven't seen many themes or mods made for 2.1 because stuff keeps changing.

Now it's reached RC stage you'll notice a lot more mods themes etc becoming available, as any changes from now onwards shouldn't be too drastic to overcome.

May I suggest putting all your changes into a new css file. Then you may have less work to do when future RCs roll in.

Then you just need to remember to add a link in index.template.php.

Oh what? Only half my post made it. >:(

So do you mean another css separate to the existing index css and both run in concert

Yes.

---

I'm too lazy to redo my post so here's a screenshot.