changing theme name breaks layout?
| Project: | Internet Services (with 2nd Edition) |
| Version: | 4.7.x-1.1 |
| Component: | Code |
| Category: | support request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I like this theme (thanx for your work) and wanted to use several versions of it on one site along with switchtheme module for users to toggle between them, but whenever I rename this theme's folder from "internet_services" to anything else (e.g., internet_services_1 or whatever), the layout breaks.
Specifically, the primary menu items no longer appear as highlighted rectangles horizontally placed in the header, but instead appear as a long, vertical bulleted list in the header.
I went into template.php and noticed several theme specific functions, meaning that a users can't simply rename the folder but has to edit code as I thought was kinda common Drupal practice?
Problem is that when I did a global search-replace for the theme name in template.php (2 occurances), i got the primary links menu to display twice, stacked on top of eachother in the header-- one as the bulleted list, and then once below that as the intended horizontal/highlighted recatangles. I couldn't find any other references to the theme name in other files, so not sure where else to look.
Two questions:
- Is it possible to rework this template to be more generic/forgiving of name changes, and/or
- What other code do I have to change to get the primary menu links to only display once?
Thanks again-- nice theme and hope to be able to use it.
-KV

#1
according to your Qs:
what you need to change when renaming a theme:
drupal PHPtemplate is well documented, and i will suggest you to have a look about that, if you hope to take some customization to existing themes. on the other hand, hope you can provide your code if you still facing difficulty, so i will be able to have a look for you ;-)
#2
thanx for getting back; I must admit i've never read the PHPTemplate docs after renaming quite a few themes without problem, but that's totally no excuse for my ignorance (I must have been lucky so far :-) and appreciate the link. I'll read up on the docs and recheck my code and let you know if I still have probs.
#3
user reply as problem solved, and so this thread will be closed.
#4