Syahir Hakim
KeymasterKuala Lumpur, Malaysia
When not perched on my workspace, I tremendously enjoy hiking in the bushes and climbing mountains. They serve as much-needed refuges from the pretense of cities.
Forum Replies Created
-
Admin
Try go to Graphene Options > Display > Navigation Menu Display Options. What’s the value that you have for the “Dropdown menu item width” option? If there’s any value, try deleting that value and leave it empty. If it is empty, try entering 200.
You can limit that to just pages by prefixing the selectors with the
.pageclass:.page .post-title a,
.page .post-title a:visited {
display: none;
}After the browser stops loading, can you try right-click and select “View source” and tell us what you see there?
Erm.. if both Firefox and Chrome are throwing out errors in your system, the source of the problem may lie in neither…
Have you googled around to see if other people are experiencing the same problem?
I’ve moved it around and zoom in/out for a good 1 minute or so, and no crash or hang with Firefox.
OK I lied. Maybe 20 seconds or 30 seconds, but it didn’t crash. Just went back again and tried again, and no crash 🙂
All the while my computer is running World Community Grid computation in the background.
Good job on the site! The sidebar widgets can probably do better without the border and shadow though, which are meant to be displayed on top of a light background. Try this:
#sidebar1 div.sidebar-wrap {
border: none;
box-shadow: none;
}Ooh…I see Niko Bellic…
Oh, and if you can modify the calendar background image to be red as well, that would blend it in perfectly with the rest of the colours.
Lol..but guys, IE9 has really come a long way since the days of IE6 and IE7. Thanks in no small part to Mozilla that started the initiative to build (much) better browsers.
I haven’t been experiencing the issues you guys mentioned on Firefox though. Using version 7.0.1 atm.
It does appear so that IE9 displays each letter a little bit thicker. Not sure there’s anything I can do about it though.
Quote:However, if people can’t intuitively choose “the photo that doesn’t belong”… do we really want them having the ability to leave a comment in the first place?The concern is not so much as whether they can or not, but whether they’re willing to be bothered to do it or not. To promote discussions we should always try to make it as easy and hassle-free as possible for people to submit their comments, otherwise some just might not bother.
There’s actually a pretty strong opinion in the internet that we should get rid of captcha altogether, and rely entirely on behind-the-scene, seamless spam filtering methods. Of course in an ideal world this would be perfect, but it’s not an ideal world and so such methods rarely works 100%.
Aksimet is one such example of behind-the-scene spam filtering, and it got rid of most spam, I’d say 90% or more. If you can live with manually deleting the other 10% or less, then Akismet alone should be enough. But if that 10% or less translates to tens of spam comments every day, coupling Akismet with a Captcha usually does the trick.
Yep, because sort_column is used for the wp_list_pages() function, while other custom queries that use WP_Query() use orderby, with a slightly different syntax. It’s this slight difference in syntax that brought about the mistake in the first place.
See http://codex.wordpress.org/Function_Reference/wp_list_pages
