davedg629

Same problem, just cropped up out of nowhere.

Having the same issue, but I’ll note that it’s only when my site is being browsed with the mobile version (the theme is switched using the w3 total cache plugin, caching is turned off though).

Ok, I saw in the Notes under the User Agent group section that plugin supposedly sets the “w3tc_referrer” cookie, but I’m printing my cookies and I don’t see this cookie being set. The theme is being switched properly, but this cookie is definitely not doing the job. Any help would be great, thanks!

O, no it does not. It just allows you to use the link to the taxonomy term without the base slug and it will redirect the base slug version to the non-base slug version.

Yes, that is the intended functionality of the code.

Same problem, first noticed when I was using WP 3.0.3. Just upgraded to 3.0.4 and still not able to search the media library.

Sorry, the code I posted earlier uses the post mash filter plugin, even if i use the following code, the other categories are not excluded:

`<?php next_post_link(‘%link’, ‘« Previous Project’, TRUE, ‘6 and 7′); ?>’

Yea, same problem I am having. The links above do not help. They only work when you are dealing with top level categories. They do not work when you want to only page through the posts in a subcategory.

Here is my code:

<?php next_post_link_menu('%link', '&laquo; Previous Project', TRUE, '6 and 7'); ?>

The posts I want to page through are in category 5, I want to exclude categories 6 and 7. The problem is that categories 5, 6, and 7 are all children of another category.

I can’t get this to work for subcategories. It seems to only work with top level categories.

alright, thanks, really appreciate your help.

Yea, turned off JS in my browser and it made no difference, no js functionality and website sub pages still load goofy in Firefox/vista.

Yea, it looks like every time there is a *property hack (e.g. *display: inline;), there is a parse error right after it.

Got rid of all the *property hacks, still loading messed up in Firefox. There are some other hacks in the code that I left in, but they are in the default wordpress css file (themes/default/default.css).

FYI the site I’m testing on now is at brycecullen.com/test

Thanks for showing me that link. Looked at the 46 errors and they are all for css properties that aren’t officially recognized by the validator or for various css hacks. I don’t think using these properties or any of the css hacks should cause the website not to load correctly. Idk, does anyone know of such a case?