I am stuck for a solution here. I have renamed the 1) Framework theme folder, 2) the .info file, 3) the name (within .info file). But the site now displays Times as the font, and just doesn't seem to see the styles.css file. The layout seems correct, but the searchbox is wider, the font is Times and changes in the styles.css won't take.

Additionally, the site looks fine in Firefox, but wrong in Safari and CSSEdit. I have cleared browser and site caches. I am also using a font page template, but I don't think that is the problem.

Are there more things to rename?

I found the below comment in this post.

1) take the Framework theme, rename it as a new theme (making sure to rename .info files and template.php function names)

What should be done within the template.php file?

Thanks

Comments

rvnd’s picture

rvnd commented

Just to add:

- the correct css file *is* being read after all No, the style.css file is not being read in Safari. It shows in the source, but changes to style.css don't take.
- the original Framework theme is also not working properly for me

edited to correct

ps - I'm sure something really simple is occurring.

rvnd’s picture

rvnd commented

Permissions, I think.

Every time I save the style.css file, the owner/group changes from 502/20 to 502/502.

rvnd’s picture

rvnd commented

Edit:

Wow! This was a very difficult thing to troubleshoot.
Although I don't understand it - here's what I've narrowed it down to. This problem is unique to a combination of Framework + CSSEdit with Live Preview switched on. Another Mac user can check this. If the live Preview window in CSSEdit is used, the process breaks.

So, with much relief, I can still use Framework, just with a little workaround of not having the preview window open. I'll still update this if I find out more.

This is fast becoming my blog :|

peterjmag’s picture

peterjmag commented

Open up template.php, and change every instance of function names that begin with "framework_" to reflect your theme name. For example, framework_body_class would become yourtheme_body_class. Don't forget function calls as well, like so:

function framework_preprocess_block(&$vars, $hook) {
  ...  
  include_once './' . drupal_get_path('theme', 'framework') . '/template.block-editing.inc';
  framework_preprocess_block_editing($vars, $hook);
  ...
}

would become

function yourtheme_preprocess_block(&$vars, $hook) {
  ...  
  include_once './' . drupal_get_path('theme', 'yourtheme') . '/template.block-editing.inc';
  yourtheme_preprocess_block_editing($vars, $hook);
  ...
}

You will also need to change one function name in template.block-editing.inc and two calls in page.tpl.php. Hope this helps!

andregriffin’s picture

andregriffin commented
Status: Active » Fixed

To fully convert Framework to your own custom theme, it is encouraged that you:
- Copy the 'framework' directory in sites/all/themes/ and rename it as 'yourthemename'
- Change the filename and contents of the .info file accordingly
- Use find/replace in template.php to replace 'framework' with 'yourthemename'
- Upload and enable the theme
- Modify as needed

To create a sub-theme based on Framework, see: http://drupal.org/node/225125

kristin.e’s picture

kristin.e commented

I have just upgraded to version 6.x-3.0 for Drupal 6. However, I am getting this message:'This version is incompatible with the 6.20 version of Drupal core.' for 'myownthemename' after following instructions to the letter for converting to my own custom theme. Any ideas on why?

I have been using Framework happily until now. I ran update.php after installing framework3 and cleared all caches too. I had this problem of 'incompatible theme' before when I tried modifying the .info file. Is there a particular file format that it has to be saved in? I have been editing it in Dreamweaver. Here are the contents of my .info file.

; $Id: anana.info,v 1.6 2011/02/18 05:47:53 andregriffin Exp $
name = Anana
description = Anana is developed out of Framework, a blank canvas for theme developers. Use Framework as a starting point to facilitate your theme development.
version = VERSION
core = 6.x
engine = phptemplate
stylesheets[all][] = style.css

regions[left] = Left sidebar
regions[right] = Right sidebar
regions[header] = Header
regions[content] = Content
regions[navigation] = Navigation
regions[footer] = Footer

; Information added by drupal.org packaging script on 2011-02-18
version = "6.x-3.0"
core = "6.x"
project = "framework"
datestamp = "1298009101"

Thanks in advance :)

andregriffin’s picture

andregriffin commented

I've tried it myself, and it work as it should. Try removing the "information added by packaging script" and everything after it. Also, you'll want to do the same find/replace in template.block-editing.inc

kristin.e’s picture

kristin.e commented

Thanks so much for your response. I removed the 'information added by packaging script' and everything after as you suggested. This seemed to do the trick! I am now happily using myownthemename and can reuse the excellent framework theme for new theme development too. I had been tearing my hair out over this

:))

spacereactor’s picture

spacereactor commented

template.block-editing.inc should be include into readme.txt took me few hrs to solve this problem.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.