Bryan Davis

Add an extra slash before the start of the link address,

i.e. <a href="/site/about-site/">About</a>.

That will cause the link to default to the base URL of the site before the linked page.

Hope that helps/makes sense.

If just for general page use – i.e. you don’t want more than 3 posts on any index or archive based page, set it in the options on your WP install.

Go to:
Dashboard->Options->Reading and change the Blog Pages “Show at most” setting.

Other suggestions for fixing errors on your site are already here.

See this section in the Codex:

https://codex.www.ads-software.com/Template_Tags/query_posts#Exclude_A_Category_From_Your_Home_Page

When using wp_list_cats(); the default behaviour requires you to wrap it in a <ul> in the template. Why not give that list a specific ID and then style the <li>s within to have the bullet graphic?

For more info on this function see https://codex.www.ads-software.com/Template_Tags/wp_list_cats

From looking at the Validator response and Viewing Source, I can see a few things straight away. These are (X)HTML issues (which is what the Validator is checking out) not PHP. The Validator checks the page that is viewed by the Browser (Client-side) after PHP has done it’s dynamic trickery (Server-side).

1. In your template, you have <h4> and <h5> tags used as content containers – change these to <div> with different classes for your style hooks. That will take care of all the warnings about <p> in invalid locations.

2. Your Digg and Del.icio.us links have unescaped Ampersands; & should be coded as &amp;. This may be something you can edit in your post template or may be the result of a plugin. How are you generating these links?

3. Several <br> tags are present. This is an XHTML document (according to DOCTYPE!) so these should be <br />

4. In the footer, the “x calls to the database” line is lacking a closing </li> tag.

That’s a few things off the top of my head, there may be more. Can I recommend that you run your templates through HTML Tidy (or similar) before uploading and, in any case, Validate, Validate, Validate.

After a quick test I can confirm that the CSS3 property target-new isn’t supported by Mozilla Firefox 1.5.0.6, Safari 2 or Opera 9 on Mac.

As this is CSS3, I don’t know which, if any, browsers will support it at this time. I’ll have a play with it and see if I can make it work at all.

Alternatives:

If using a “transitional” DOCTYPE in your templates then using the target attribute in your links will still work without (X)HTML validation error.

If using a “Strict” DOCTYPE then indicate the links to be opened in a new window with a class and then intercept them with a little DOM scripting and have the new window open that way.

Real question is: do you really need links to open in a new window at all?

Hi Robert

You can add pages for each of your parent categories and set your Permalinks accordingly. Then, in the template for each page, set The Loop to display only the required parent category. Examples of how to do that can be found here.

You can then set your Archive root to something different (e.g. /archive/) and, by using Category Archive links you can maintain an archive structure for your different Parent Categories. It’s a bit of a hack but it works; it’s a technique I’ve used on several sites.

Hope that helps. Please feel free to bother me about it further; either here or via my site (includes links to sites that do this) which you’ll find on my profile. When I have time, I’ll also sit down and write a clearer explanation of this on my blog, just in case anyone else needs to do similar.

Cheers…

Try adding

type="text/javascript"

to each of the opening <script> tags.

i.e. <script type="text/javascript">

My guess is that the XHTML WP templates aren’t recognising the Javascripts without referring to it as Javascript and therefore ignoring them.

I’m not sure whether that’s possible or not. However, it strikes me that it may not be necessary.

It seems that you’re trying to have a main site managed by WP along with a separate “Articles” section, also WP-powered. On a single install, and with careful inclusion/exclusion of Post Categories within templates, it should be possible to keep different sections of your site separate in this way.

Thus, you only have one set of users and one set of templates. Does this sound like it could work for you, or am I over-simplifying your requirements?

Admittedly it’s a while since I used MS Word but can you not create a document and then save it as plain text (.txt)? All the user has to do that’s extra is a “Save As…”; not too arduous even for the technophobic.
Presumably this would purely give out the content without MS formatting and allow a safe copy/paste into the WP WYSIWYG for final formatting.

Or maybe I’m being naive…

run the upgrade.php file (again) – then everything will be cool. I had the same problem the other week and everything’s now fine and dandy.

Had time to try out the Link thing for myself. It’s a margin issue on the 1st level Link Items.
Either cancel the margin for sidebar <li>s and space them with a Margin/Padding on the <h2> or add a class to the particular <li> containing your additional menu items and style accordingly.

tylkum:

In your CSS, try

li#pagenav ul {margin-top: 0;}

if it’s not that, then it’s probably an inherited list-item margin problem.

interknox:

I don’t have a Gallery on my site. Recommended music links are using an Amazon plugin I found here on the Support forum. Calendar is a separate system which I’m working to make available as a plugin – probably figure it out in the next 3 years!