It sounds like your theme isn’t compatible with WordPress 2.1. You might want to contact the Theme author about this. Does this happen when you switch to another theme? Good luck!
spencerp
My theme IS compatible with WordPress 2.1, so when it’s not the whole theme didn’t work…
Hmm, I’m not familiar with the Blix theme really. I never really messed with it before. If I have some time, I’ll look into it. 🙂 In the meantime, maybe someone else around here can help you better. Good luck though.. :);)
spencerp
I hope so, maybe someone else for now?? Thanks.
I try to use this contact and about pages in another theme and it works fine, but not in the Blix theme, strange enough…
Either way, I’d contact the theme author about this issue. Because if other themes are working, just not Blix, it must be something in the theme itself.. Good luck!
spencerp
I contact the theme author also. I hope he comes up with a fix or something.
B.t.w.: I see the pages in my admin panel, it’s called contact, archive and about. So, they still there but I see no button on top of the page.
Any news about this issue??
Ok… this seems to work:
In header.php replace
<li<?php if (is_home()) echo " class=\"selected\""; ?>>">Home
<?php
$pages = BX_get_pages();
if ($pages) {
foreach ($pages as $page) {
$page_id = $page->ID;
$page_title = $page->post_title;
$page_name = $page->post_name;
if ($page_name == "archives") {
(is_page($page_id) || is_archive() || is_search() || is_single())?$selected = ' class="selected"':$selected='';
echo "<li".$selected.">Archives\n";
}
else {
(is_page($page_id))?$selected = ' class="selected"':$selected='';
echo "<li".$selected.">$page_title\n";
}
}
}
?>
with
<li class="<?php if ( is_home()) { ?>current_page_item<?php } else { ?>page_item<?php } ?>">"><?php _e('Home'); ?>
<?php wp_list_pages("title_li=&depth=-1&sort_column=menu_order");?>
It worked for me, it should work for you!!
My theme IS compatible with WordPress 2.1
Whatever you say…
If it is using special queries (and it does, that’s why nobody wants to mess around with it) that are based on the pre-2.1 database structure – then it is NOT compatible.
Blix is one of the few featured themes from http://wordpress.org/extend/themes/ , so it is no wonder that several people expect it would be fully compatible with WP 2.1, or at least they would get some help to continue using it.
It must be stated that even though it is called a WordPress Featured Theme, it is not fully compatible whith WP 2.1, because some of its special functions in BX_functions.php are not working under 2.1.
Jakeanders’ code snipplet above is no working solution for that issue. Maybe it could become one…
Okay, now this is a working solution for Blix theme in WordPress 2.1, based on jakeanders’ snipplet.
1.
In header.php, replace lines 35 to 61 (as given by jakeanders, beginning with <li<?php if (is_home()) and ending with the three }) by following code:
<li<?php if (is_home()) echo " class=\"current_page_item\""; ?>><a href="<?php bloginfo('url')?>"><?php _e('Home'); ?></a></li>
<?php wp_list_pages("title_li=&depth=-1&sort_column=menu_order");?>
2.
In spring_flavour.css replace line 81
#navigation .selected,
by
#navigation .current_page_item,
This is very much what Jakeanders said, but preserves a permanent home link. Also, I removed a typo in Jakeanders’ code. Note that I followed Jakeanders in including translation for the home link. If your language file has a translation for “Home”, this will be translated. If you want it exactly as in Blix 0.9.1, i.e. without translation, replace <?php _e('Home'); ?> by the word Home or whatever you want for your home link.
Pardon, be sure you don’t get double ?> marks at the end of the inserted code. This means, either remove lines 35 to 62, or don’t paste the ?> from the end of my code fragment above.
A free modified version of Blix called Blix Krieg which incorporates these changes, and adds some features is available at http://www.utheguru.com. It can be dropped right over the top of an existing blix installation in two minutes flat – saves coding.
Also backwards compatible with earlier versions of WordPress.
Thanks for cleaning up my code and making it work for everyone. As you may have guessed from what I produced I’m not a regular coder but I’m slowly learning through doing things like this.
