By kevinr1247 on
I'm trying to write a simple theme and keep running in to this problem. This is the code "Pro Drupal Development, 2nd addition." What should I check next?
So far I've,
1. I' ve cleared the cache
2. I've changed 6.4 to 6.x and back again
3. Followed the guidelines on http://drupal.org/node/171205
My .info file looks like this:
name=greyscale
description = Demurely grey tableless theme.
screenshot = screenshot.png
core = 6.4
engine = phptemplate
regions[left] = Left sidebar
;Wedo not have a right sidebar
;regions[right] = Right sidebar
regions[content] = Content
regions[header] = Header
regions[footer] = Footer
;Features not commented out here appear as checkboxes
;onthe theme configuration page for this theme.
features[] = logo
features[] = name
features[] = slogan
features[] = mission
features[] = node_user_picture
features[] = comment_user_picture
features[] = search
features[] = favicon
features[] = primary_links
features[] = secondary_links
Comments
seek
Did you try comparing it with other theme info files in the core distro that DO work?
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
.dan. is the New Zealand Drupal Developer working on Government Web Standards
yes
and I stripped it down even further just to make sure and substituted the bluemarine theme with just some minor changes like "name."
So it has to be something other than that .info file, right? I'm just trying to put the pieces of the puzzle together so I understand what it could be. Here's the blue marine .info that I used.
...
Wondering if you've unearthed a bug?
Try renaming the theme, maybe grayscale2, so Drupal thinks this is a totally new theme you're adding.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
regarding Bluemarine
Maybe, I'm not familiar with Drupal enough to have a feel for it.
To work towards a solution I'm hacking into bluemarine and one thing I discovered was that if I change the name of the .info file in the bluemarine directory to something else, that causes bluemarine to be incompatible.
Why is that?
Furthermore if I don't change the name of the file but change the "name" in the content of the file. That also causes the incompatibility error. Hmmmm
Then if I change everything back to the way it was initially, the error persists. What's up with that?
:-/
Unable to replicate.
The example you gave at the top works just fine for me - once you change 6.4 back to 6.x
.info files should be named after the directory they are in. The name inside the file can (i think) be anything.
From your description of breaking bluemarine, i'd suspect you are using a hopeless windows text-editor which has renamed your *.info file to *.info.txt or something invisibly. It's not that silly is it?
Either that or permissions, because clearly "putting it back the way it was" should work again. No serious caching AFAIK, jusr refreshing the admin/themes page re-scans the infos.
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
.dan. is the New Zealand Drupal Developer working on Government Web Standards
good thinking dman
AFAIK the editor in use is Dreamweaver, which is no problem as long as its done in "Code view", however if you attempt to format the file in "Design View" (such as hitting return to enter line breaks) that'll be whacking paragraph & line break tags into the .info file, so....
I actually tried this to see if I could generate the same error...
bingo...
Adendum: simply removing the evil
<p>tags (in code view of course) immediately rectifies the situation without any need to clear caches.Need help with IE?
Learn basic XHTML and CSS first.
Get smart with web specs.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
good-o
Good job.
It's pretty hard to second-guess someones non-editor messing up that badly.
Code is text, FFS! Some assumptions are just to basic to even include on the checklist.
Next thing we'll be debugging problems because someone used MSWord or TextEdit rtf to edit their source files !
... and people wonder why hard-liners still use commandline, vi and emacs ;-)
.dan.
if you are asking a question you think should be documented, please provide a link to the handbook where you think the answer should be found.
| http://www.coders.co.nz/ |
.dan. is the New Zealand Drupal Developer working on Government Web Standards
didn't work for me
I tried using "textEditor" (no Richtext) on the mac and I'm still having the problem unfortunately. In Dreaweaver I have been using codeview strictly. I upgraded to 6.5 and same issue.
Like I mentioned, if I simply duplicate Bluemarine and rename it, it causes the error. More frustrating is trying to figure out why my page.tpl.php isn't being called. I feel like these issues are connected somehow but not sure.
OK, lets just get this
OK, lets just get this strait.
1) copy/paste Bluemarine and rename the directory - thus you get /themes/bluemarinea/
2) rename the .info file, now must be called bluemarinea.info
3) Give it a new name e.g name = Bluemarine 2
Upload and you get errors?
That *should* work fine, I mean I do this 5 times a day.
Pimp your Drupal 8 Toolbar - make it badass.
Adaptivetheme - theming system for people who don't code.
YUP;
just did it again to make sure. Followed the step by step perfectly.
It pops into the theme window but it says its incompatible; red x denotes that it is not enabled.
Let me try it one more time:
copied working Bluemarine. (downloaded it from server to make sure that it is exactly the folder that is working)
changed folder to redmarine.
changed .info to redmarine.info.
changed "name" to Redmarine in the info file....
shift Reload theme page.....there it is
"This version is incompatible with the 6.5 version of Drupal core."
then, the crazy ass frustrated grin on my face. It's got to be something simple that I'm missing.
SOLUTION
http://drupal.org/node/325020
Common cause of "version is incompatible with the 6.x" problem
There are apparently a lot of reasons this error can be thrown, and I think I've read through all the postings about it, seeing if I could find anything that looked like mine. But all I was doing was copying installed themes to a new folder. That caused them to become "incompatible." Then I discovered that I couldn't even install a new, very compatible theme like Acquia Marina -- it too became incompatible with our Drupal 6.10 core.
My problem turned out to be file permissions. My Expandrive had a custom permissions mask of User [read, write, execute], Group [read, write, execute], Other [read]. Well, the "Other" in this case is Drupal, and it couldn't execute, so it was throwing the "incompatible" error. As soon as I turned on Execute permissions for "Other" I was fine.
If you have this problem and can't find what's causing it, and especially if something has been working just fine until recently (my situation) or is working fine on another server that you're trying to clone from, check the permissions that are being set when you upload, create, or modify a file.
One other thing to check (Line Break Formatting)
After spending an entire afternoon on this I figured out that Dreamweaver on my Mac was saving .info files with the mac linefeed formatting instead of the more commonly accepted CR LF windows or simply linux LF. This was causing troubles for drupal when attempting to read the file and thusly would mark the whole template incompatible. If you're editing .info files from a mac be sure the Line Break type is set to the Windows or Linux standards on your editor. In DW this is found under Preferences>Code Format>Line Break Type.