Hi,

Love the project but I have a question for you.

Having used version 1.2 to built a theme and site using your instructions to modify the theme files, now you have upgrade to version 1.3 what do I do?

Do you have any instructions to perform an upgrade?

Doesn't changing the core of your theme rather than constructing a sub-theme make it very difficult when performing an upgrade, what do you do yourselves?

Regards

Dave

Comments

Jeff Burnz’s picture

Jeff Burnz commented
Assigned: Unassigned » Jeff Burnz

First - dont upgrade to 1.3, wait for 1.4, due to big advances in the Skinr module UI we need to release a new version to account for this, and we're taking the opportunity to slip in some extra theme settings and a couple of kickass new featues. Right now I have a bug with conditional styles I need to squash and then 1.4 will be released (will be early this week).

Genearlly there is no real reason to upgrade unless you want features in the later version, or to account for a possible bug fix.

However, that said I am building themes all the time and have migrated several of them through various versions.

Generally I don't touch the core of the theme, and if I do this is restricted to templates files and layout.css (required if using LayoutSP). If I need to add preprocess stuff I just put this at the bottom of the relevant function so its easy to find later on.

Normally I can migrate between versions in a few minutes.

If you are using a version prior to the preprocess split (now all core preprocess functions are in seperate inc files) you need to account for that in during the upgrade.

I realize I haven't actually told you how to do the migration, mainly because this will depend on what you have changed in the core theme, so what if you send me the theme and I'll take a look and give some more specific feedback - jeff [at] adaptivethemes [dot] com

david1409’s picture

david1409 commented

Hi Jeff,

Thanks for the reply, I will wait until 1.4 is available and then have a look. So far I have only made fairly minor changes and the site's not yet in a production enviroment so I'll have a go myself to start with but if I get into trouble or confused I will take up your suggestion to have a look for me, it's very kind of you to offer.

My initial confusion is because I'm quite new to Drupal so have been trying out different themes and modules and have got used to updating other things where creating sub-themes is normal so trying to sort out a theme which says don't make a sub-theme change the core instead is new to me. I really like the flexability offered by AdaptiveTheme so will definatly make a effort to get my head around this.

Thanks

Dave

Jeff Burnz’s picture

Jeff Burnz commented

I'm going to have a crack at subthemeing AT this week, I think it should be fairly easy. The "dont subtheme this" message is more directed at our commercial themers who are building themes for AdaptiveThemes. The last thing we want are myriads of support requests from concerned clients when Update Status starts nagging them to upgrade the base theme, when there is no real reason for them to do so.

Also because I have never really tested it out.

I'm running tests now, 99.99% of the new code is in place and working well, the new Skinr stuff is great and I have a bunch of "how to" videos down on paper ready to be recorded (man I wish there were more than 24hours in a day...).

Let me know how you get on.

wtrke’s picture

wtrke commented
Version: 6.x-1.2 » 6.x-1.3

I'm eagerly waiting for 1.4! Great options.

Jeff Burnz’s picture

Jeff Burnz commented

Under limited testing I found building a subtheme no problem at all, I was using the dev version which is very nearly ready ;)

david1409’s picture

david1409 commented

Hi Jeff,

Thanks for the new version, I'm getting the hang of the sub-theming now, not as much of a problem as I thought it would be, still can't get my head around Skinr (but thats another issue), I did have a minor problem and found a couple of minor bugs (I think) and have logged these as seperate problems.

Thanks for your help.

Dave

Jeff Burnz’s picture

Jeff Burnz commented
Status: Active » Closed (fixed)

Cleaning up the issue queue.