prjg

They do if you want them to, and they’re checked by default. It’s the same place as posts are when you write them, radio boxes for allow comments and pings.

To make your stuff editable. You’re hosted with apache so this’ll be simple.

SSH or telnet into your account, navigate to your theme directory and do
chmod 666 *
at the command line. That makes them “world writeable” in Unix lingo, meaning you can now edit them from within WP.

https://validator.w3.org/check?uri=http%3A%2F%2Fdarran.digital-pulse.net%2F
Try fixing those. I don’t have IE 7, but it works well enough in FF 1.5.0.1 and Opera 8.53

Run it through this first –> https://infohound.net/tidy/
That’ll “un-Word” it like nothing on Earth ??

All you need to do now is get browsers to display links, I know Opera and lynx do and so will Firefox/Mozilla with an extension but, keep in mind, the requirement to support link rel and rev is *optional* according to the spec; so much for it being a “Web Standard”.

Why bother though? Seems to me you’re going to the ends of the earth in the name of semantics and minutiae. Of course, you’re free to do that…

I’ve checked your host’s website and some of the sites that share your virtual host’s IP addy, they all work fine with lynx. It’s just you, from what I can see.

I’m seeing it at the top of your blog. You must’ve fixed it.

Wrap an anchor around the picture.

Look for

<meta http-equiv=”Content-Type” content=”text/html; charset=<?php bloginfo(‘charset’); ?>” />

in header.php of your active theme. Change the php bit to explicitly state UTF-8

i.e

<meta http-equiv=”Content-Type” content=”text/html; charset=UTF-8″ />

Failing that, add a
AddType “text/html; charset=utf-8” php
directive to the .htaccess in the doc_root of your blog.

If that doesn’t make it output in UTF-8 I don’t know what to tell you.

OK then, you’re still stuck with the logistical problem of how to send a 410 header for something the server no longer has a record of. 410’s need to be explicitly set and how are you going to do that with a deleted dynamically generated URL?

If you do Redirect gone /blog/03/26/whatever it won’t work unless you manually mirror each and every post you intend to trash into real and canonical filenames. Because technically, they do not exist until the page is called and PHP and MySQL do their thing.

Definitely in the too hard basket, if you ask me.

You could ask the admin to do a .sql dump of your account and have them send it to you.

The OP means to centre the picture in the sidebar as opposed to having it aligned left or justified like most themes do sidebars.

The old fashioned way is to add an align=”center” attribute to the img tag which may break validation depending on the doctype, the other and more groovy way is to use something like margin: auto

410 is usually used where someone has had stuff hosted, such as a student on a University account, and they moved and taken it with them and the host has no information on where they’ve gone.

It’s basically a “return to sender, address unknown” code.

If *you* delete something from your system, *your* system mind you, not somebody elses, that is, a domain you control as opposed to just a /~ account, then it’s a 404 because it isn’t technically “gone” because you *know* where it went.

I think that’s why “404 Not found” is actually correct as opposed to “410 Gone”. The former is temporary while the latter is permanent.

They are both permanent conditions, in fact you could argue 410 is the more temporary as it’s expected the host will remove the code sooner rather than later once search engines and friends of the “gone missing” get the idea the resource is gone. It’d then become a 404 if anyone or anything tried accessing the resource.

So, 410 makes little to no sense on a website/domain controlled by one person/entity who knows where stuff has gone.

Will any .htaccess work for you? Can you write one and add, say, a redirect to see if it works? I’m just wondering if your host has set limitations on AllowOverrides