Closed (won't fix)
Project:
Mix and Match
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
15 Dec 2011 at 17:29 UTC
Updated:
9 Feb 2013 at 19:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
nedjoClarifying title. I'm using Mix and match in the Open Outreach distro and look forward to being able to upgrade to Fusion 2.x. Happy to review any draft patches.
Comment #2
radoveden commentedGood news ! I'm using Mix and match also. Skinr is the only module giving me problems in upgrading my site from drupal 6 to drupal 7. So, I'll wait for this solution. Keep on the good work !!!!
Comment #3
drupalninja99 commentedThe skinr include is almost exactly the same as fusion apply. I am playing around with re-creating the openchurch mix and match theme for D7. I will let you know if I have any luck.
Comment #4
drupalninja99 commentedAll you need to do is add
To the .info file
Then create the path skins/core/core.inc And place essentially the same code in a different function hook, see below:
Comment #5
drupalninja99 commentedYou could support skinr and fusion apply simultaneously in the since that its basically the same code. If fusion apply is enabled it will use this skin, if skinr is enabled it will use the other.
Comment #6
nedjoHere's a patch based on #4 with minor key naming edits. Seems functional on my basic testing.
Comment #7
nedjoPrevious patch generated a whitespace error.
Comment #8
nedjoAdd in responsive settings to .info file for use with fusion accelerator. Fixes the issue reported in #1606938: Invalid argument supplied for foreach().
Comment #9
ajross commentedSo sorry for the delay and thanks for all your posts. I completed a quite a bit of work on a new release working with Fusion Accelerator with extra responsive features, etc. However, it appears that Fusion and its associated module are not being actively maintained any longer, as far as I can tell. As a result, I've switched and am working on instead building a responsive 7.x version of the theme on a different base theme and that one will continue to use Skinr. Should have a release of that soon. As far as the Fusion version goes, I will try to do one more release with some basic bug fixes, but if there is no indication that Fusion or Fusion Accelerator is going to be actively supported in the future I don't think it makes sense to continue with that as the base.
Comment #10
spidersilk commentedOut of curiosity, what base theme are you going to be using? I used to use Zen when creating custom themes for clients, but had been shifting in the direction of Fusion - but if Fusion's future is in doubt, that's obviously not a good plan. So now I'm curious what might be a better pick, that would be more full-featured than Zen, but more actively supported than Fusion...
Comment #11
ajross commentedI've been setting up test versions on AdaptiveTheme and Omega for comparison. Omega is a terrific base theme but I think the configuration options on AdaptiveTheme are a bit closer to what Fusion has so I'm planning to release that one, and then have it work with Skinr for block styles. I just think it will be a little less disruptive for folks that are used to Fusion. I've also worked with Zen and while it's responsive version is very good too, again it just is very different from what I had set up with Mix and Match and Fusion. Although please feel free to weigh in if you have any specific thoughts about any of the base themes.
Comment #12
nedjo@ajross: thanks for the update and good to hear your plans. I've moved this to a new issue, #1852830: Produce new branch of Mix and Match based on AdaptiveTheme or Omega, so we can close this one.
Comment #13
ccannon commented@Nedjo - patch in comment #8 worked like a charm. Thanks very much for taking the time to put it out there!
Comment #14
spyderpie commentedwill this (mix and match patch) be committed soon? I'd rather not patch and it looks like this theme hasn't had an update since 2011 ... pweeeeease?