Closed (works as designed)
Project:
Omega
Version:
7.x-3.0-alpha4
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
27 May 2011 at 01:19 UTC
Updated:
30 May 2011 at 18:22 UTC
brr .... copy starkit to the /sites/all/themes and in appearance no any starkit ...
Comments
Comment #1
protools commenteduse 7.2 drupal
Comment #2
fubhy commentedopen the .info file of your subtheme and follow the instructions. one of the first lines tells you to remove the "hidden = TRUE".
Comment #3
protools commentedhidden = false ??? and what's the catch? no in appearance no any starkit
Comment #4
protools commentedI think that the way of sub-themes in the Omega is not the best, but I understand that the API
changes in version 7, but it's all confusing to end users. The traditional approach would have been better. Maybe the traditional approach would be more understandable Most of users.
Comment #5
fubhy commentedThe starterkits should NOT be visible in the appearance listing. They are not meant to be activated or configured anyways. They would just flood the listing and would annoy the end-user. I know that they did annoy me. The starterkits are easy to use => Copy them, edit the .info file => Start themeing. There is really nothing wrong with it.
Comment #6
fubhy commentedThese are some of the first lines in the starterkits info files. They couldn't be any clearer. You have to edit the .info file of your subtheme in order to change the name and the description. There is simply nothing wrong with the hidden = TRUE assignment if the end-user just deletes it for his subtheme that he wants to be visible on the listing. It couldn't be easier. The wizard that I am working on (subtheme creation wizard) is going to make this even easier. So what exactly do you find confusing and what was different for you with the "traditional" approach?
Comment #7
fubhy commentedComment #8
protools commentedSorry, slept little and had not noticed the inscription, besides the habit subtheme copied to a folder in all>themes, but must be in a folder all>themes>Omega>subtheme
why if i put subtheme in all>themes/mysubtheme - no display in appearance ?...
I put to the Omega folder, set mysubtheme by default, then moved from Omega to the all>themes/mysubtheme
and mytheme work, but in appearance no display ...
Comment #9
protools commentedin http://drupal.org/node/225125
in Drupal 6 and 7 it can be placed outside of the base theme's directory.
Comment #10
fubhy commentedYou are doing something wrong. This works as designed. Make sure you remove the line "hidden = TRUE" in your subthemes .info file. You can of course place your subtheme in "all/themes/YOURSUBTHEME".
Comment #11
protools commentedfresh install Drupal 7.2 and latest Omega - starkit work only from Omega sabdirectory
no work from "all/themes/YOURSUBTHEME" tested 3 times!
Comment #12
fubhy commentedI have 3 live sites running and tested it about 100 times locally: The subthemes work. Did you maybe forgot to rename your subtheme? You cant have multiple subthemes with the same name... Oh... And subthemes can't start with a digit! This works with a certainty of 99999999%!
Oh and another thing... This is something (folder structure of themes) that Omega / Alpha have NOTHING to do with. This is core behavior and CAN NOT!!! be changed by a theme. Themes work from within any folder that is scanned for theme .info files. Please re-check everything. This is working (so many people are using it and I myself tested it a million times). This is not a bug!
Comment #13
protools commentedyes work, rename starkit and all work,
hm when i don't rename sub theme, it worked Frome Omega, but not from all/themes/YOURSUBTHEME
Comment #14
fubhy commentedYes because when you didn't rename it (but had it in the subfolder of Omega) it was included AFTER the original (unmodified) starterkit and therefore overruled that one (obviously)
Comment #15
protools commentedThank you, sometimes I'm really stupid :)
and I forget to say thank you for such excellent work
Omega - really cool theme !