I am creating a sub-theme based on the Sky theme for 6.0 which is up and working on my site. I have a folder with my theme name, a .info file and a .css file. When I go to Admin->Site Building->Themes I see a addition to the theme table but it has this message:
"This version is incompatible with the 6.0 version of Drupal core."
I have experimented in every way I can think of and nothing fixes it. Any suggestions? Here is my current .info file:
name = WGJ
description = First theme developed by Spithra for The Web Geek Journal based on the Sky theme.
core = 6.x
base theme = sky
stylesheet[all][] = wgjstyle.css
engine = phptemplate
regions[header] = Header
regions[left] = Left sidebar
regions[right] = Right sidebar
regions[contenttop] = Content top
regions[contentbottom] = Content bottom
regions[contentfooter] = Content footer
regions[footer] = Footer
; Information added by drupal.org packaging script on 2008-02-27
version = "6.x-1.1"
core = "6.x"
project = "wgj"
datestamp = "1204142108"
Comments
Try deleting everything
Try deleting everything after "regions[footer] = Footer"
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.onnetworks.com
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.chapterthree.com
Tried that
but nothing changed. I even cut and paste the .info file from another working theme and got the same error. Thank you for your help, I need to get this set up for the site designer to move forward and I'm pulling my hair out!
Try adding this line (as is)
Try adding this line (as is) under "description"
version = VERSIONShot in the dark, but its the one difference I see between garland/minnelli, and what you posted.
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.onnetworks.com
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.chapterthree.com
Nah -- that's not it. Here's
Nah -- that's not it. Here's something weird though, I copy and pasted the info file you posted and put in minnelli.info -- and it worked perfectly. I think maybe the base theme, not WGJ is the culprit?
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.onnetworks.com
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.chapterthree.com
Seems Dreamweaver is the culprit??
The problem seems to be that I open the .info file in Dreamweaver to edit it then post it. When I started all over again but used *only* TextEdit to make my changes, it worked. Its as if the core = 6.x never gets read once its been opened in DW. Doesn't make sense to me, but it did make the error message stop.
Thank you *very* much for your time and attention!
It could be that dreamweaver
It could be that dreamweaver was using unkosher characters like "smart" quotes....
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.onnetworks.com
--
"I'm not concerned about all hell breaking loose, but that a PART of hell will break loose... it'll be much harder to detect." - George Carlin
--
Personal: http://www.nicklewis.org
Work: http://www.chapterthree.com
I'd like to help resolve this
I code the Drupal API and jQuery API extensions for Dreamweaver and my extension for Drupal helps recognize .info file but I hadn't noticed an issue myself.
1. What version of Dreamweaver are you using?
2. Do you have the Drupal API extension installed?
~ ~ ~ ~ ~
Chris Charlton
Download Drupal extensions for Dreamweaver - http://xtnd.us
~ ~ ~ ~ ~
Chris Charlton, Author & Community Leader
Learn how to create and edit Drupal Themes by watching my videos - http://tinyurl.com/theme-drupal
Download Drupal tools and extensions for Adobe Dreamweaver or Eclipse - http://xtnd.us
line-endings
Hey Chris,
My guess is that this is a line-ending problem. This person's DW is not set up properly re: line-endings. It's my understanding that this won't have many adverse effects in drupal -- except for info files, which rely on proper UNIX line-endings in order to be properly parsed.
Just had a similar mystery at my work. IT finally came in and solved it. Very puzzling.
http://CrookedNumber.com
How did they solve it?
How did they solve it?
2 things
1) Open, then save, the file in something other than DW (that has the proper line-endings)
2) In DW, go to Preferences >> Code Format >> Line-break type. Change it to UNIX (LF). Then open the file, make sure all is OK, then save.
http://CrookedNumber.com
Theme incompatible error
I'm getting the theme incompatible error message, and I'm about out of ideas.
The site is one instance within a multisite installation, and the theme works in every other site except one. Maddening.
I've uploaded several contributed themes to this site, and I get the error message with all of them. I tried cutting out various parts of the .info file (with Notepad, not Dreamweaver), and tried uploading with no edits to the .info file.
So, I'm guessing it must be a setting in this site that is causing my woe?
I've searched through the Drupal forums, but no luck so far.
Grateful for any leads.
FWIW, I believe this error is
FWIW, I believe this error is displayed if there is a syntax error that prevents Drupal parsing the theme.info file correctly.
This could be due to line breaks, file encoding etc, or in my case the fact I had the following line:
screenshot =
replacing this with screenshot = screenshot.png fixed it, presumably because the parsing code didn't slip up on the empty declaration.