silverks

The theme uses sprite images for performance reasons, and the background of the navigation menu is in the sprite_h.png image file.

If you’re not familiar with srite images and how they work, it’s easier to just define your own background and not use that sprite image. Firebug plugin for Firefox will be a handy tool in determining which CSS you need to modify.

Link to your site? Version of the theme you’re using?

No worries ?? Now if you would kindly mark this as resolved, that would be great!

Hi manicolaus,

You may also want to take a look at this note here: https://forum.khairul-syahir.com/graphene-support/new-navigation-menu-in-version-14-a-heads-up

Hi jbinnie,

Please update to the latest version (1.4.1). Also, you might want to take a look at this note here: https://forum.khairul-syahir.com/graphene-support/new-navigation-menu-in-version-14-a-heads-up

Please update to version 1.4.1 and let me know if you’re still having issues.

Hi,

I’m the theme author and have been testing the theme with 3.2 since the beta came out, and haven’t discovered any issues. If you do discover any bugs, please report it in the theme’s Support Forum.

Hi flamenco,

Yes, it’s a conflict with one of the jQuery libraries being included with the theme. It has been reported on the theme’s Support Forum and has been fixed in the upcoming version 1.4.

The overflow: hidden property was added so that excessively big images would not overflow the content area, but it has unintended consequences of text not wrapping properly.

This issue has been addressed properly and the upcoming version 1.3 will have this issue fixed.

The upcoming version 1.3 will include the option to show full posts instead of excerpts in archive pages.

Thus usually happens when there’s a stray </div> closing the content area’s opening <div> too early before the sidebar is loaded. Check to see if you have any unopened </div> in any of your sidebar items.

Thanks everyone for your responses. As the Graphene theme author, I would also recommend the solution that Adeptris suggested.

PS: My apologies for not responding earlier. I have very, very little free time at the moment. This is the busiest time of the year for me.

ok, i’ve resolved this issue already. It seems like the kses filter is stripping out all html tags, even the usual ones.

I replaced the kses filter with HTML Purifier using HTML Purified plugin, and everything works fine.

HTML Purifier is supposed to be the better sanitizer, but it is also more resource-intensive. But since I haven’t noticed any performance hit on my website, and also the sanitizer will only be invoked when saving posts and submitting comments, it’s a good enough solution.

Maybe WP developers should implement a better HTML sanitizer than kses? even htmLawed seems to be better…

I found out that the above issue is because WordPress automatically strip all HTMLs from the comment, including all the <p>,

,
, etc.

I noticed this as when I’m logged in and post the comment, all the html tags were included in the comment (and I notice the _wp_unfiltered_html hidden input in the form).

Question is, how do I get the same functionality for non-logged-in users? I know allowing full unfiltered html comment could be dangerous, but at least allow the standard tags (like the one here in WordPress support) through?

Please if someone can help me. Thanks.

I have the same problem..actually, it’s more like a series of bugs..for example when I add a new category the message “An unidentified error has occurred” is displayed, but when I refresh the page the new category is there. Other problem is that in the Edit Post page, adding a new custom field will not get instantly updated, but when I hit Publish, the new custom field is there, but it is duplicated, so I have to delete it everytime.

Happens on WP 3.0 using my self-developed custom theme.

I tried switching to the fault TwentyTen theme, and everything works fine, so I know that whatever causes all the bugs must somehow be related to my theme.

Then I tried deleted the functions.php file of my theme, and everything works fine! So then I know there’s something not quite right with the codes in my functions.php file.

I checked and there’s no syntax error at all. PHP is not throwing out any errors or warning, so the issue must be how WordPress handles the functions.php file.

It turns out that in the functions.php, you must not close the initial <?php opening tag until at the very end of the file. You can, however, close the initial opening in the middle of a statement.

The following works for me:

<?php

echo 'something';

function whatever() { ?>
   <h2><?php bloginfo('name'); ?></h2>
<?php }

?>

The following does not work:

<?php
echo 'something';
?>

<?php
function whatever() { ?>
   <h2><?php bloginfo('name'); ?></h2>
<?php }
?>

Why? It’s probably a bug in WP 3.0, I don’t know, maybe somebody can follow it up. But everything works perfectly in my WordPress install now.