WordPress.org

1. cybershot
   Member
   Posted 1 year ago #

   I am developing a custom theme on the back of the twentyten theme. I am using starkers naked wordpress theme which is built on the twenty ten theme. I did a find and replace of all twentyten and replaced it with my theme name. Now the stylesheet is no longer working. All the posts show up but absolutely no styles. Antyhing that uses bloginfo to get the directory is broken. Do you know why?

2. kmkoetsveld
   Member
   Posted 1 year ago #

   I'm looking for the exact same answer. I don't have a clue, so sorry.

3. Jan Dembowski
   Volunteer Mod. & Brute Squad
   Posted 1 year ago #

   I did a find and replace of all twentyten and replaced it with my theme name.

   You are working way to hard, and Twenty Ten is not right for that kind of work. It's just too complex and as you found, simple search and replace does not work.

   Try a framework such as Hybrid or Thematic, create your child theme for the framework and start styling, filtering, adding actions, etc. It's just easier.

4. kmkoetsveld
   Member
   Posted 1 year ago #

   I'm not a guru and I'm not sure if this will work for you too, but I did the following and that worked for me, creating my own theme, based on twenty ten:

   With ftp I got the directory wp-content/themes/twentyten down to my computer.
   I renamed the directory there to my theme name. In all the files inside I 'find and replace'd all twentyten to my theme name, as well as all Twenty Ten and Twenty_Ten.

   In the stylesheet I also edited the description of the theme and the author.
   Then, when I was sure there wasn't any twenty ten left in the content any more I uploaded my theme directory with ftp up to wp-content/themes/mythemename.

   Then it was visible in the backend (i believe it's called) in appearence/themes. I simple activated the theme. The only things that were missing were the background and header image. Rest functions completely.

   Hope this works for you too. Good luck!

5. cybershot
   Member
   Posted 1 year ago #

   I discovered that is was because the header.php file from my theme found it's way into the root directory some how. I had to replace all files site wide and slowly worked backwards to figure it out.

Topic Closed

This topic has been closed to new replies.