altjira

From my blog (Sorry if this comment is bulky, but I think it lays out the entire logic):

At first I hated the way WordPress sent pingbacks to itself – if I put a link on a new post that referenced back to something I wrote earlier, the pingback registers itself as a comment on the original post, and takes a stab at a relevant quote from the new post to include in the comment. But after browsing the WP Support Forums, trying to figure out a way to turn this function off, I saw it tauted as a feature – the pingback notified the reader that there was more information posted, and I could see the utility in that. So I learned to live with it, stopped deleting the pingback comments, and just checked the quote so that it was no larger than it needed to be and gave a good idea of what the new post was about.

But it’s still annoying, primarily because of the way my blog and most others are formatted. My main screen, the blog home, shows the last ten posts on the first page, most recent first. As you can see, each post is formatted something like this:

Date

Title (which links to a page that shows the post, all its comments, and space to enter yours)
/ – –
{Body of Post}
– – /

Posted by {me} as {List of Categories} at {time}

{#} Comments (the number of comments and the same link)

I don’t think that’s a good arrangement, primarily because, in my experience, it takes a lot to get the casual visitor to click any link once they arrive. They are more inclined to just read the post and determine whether it contains the information they came looking for, and if it doesn’t, they leave. They don’t know that the comments might contain a link to a more recent post that has more information – as far as they know, it’s just some drongo saying “so what is the solution to the problem?”, when in actuality it might be a link to the answer they also want.

I think it’s a better approach to distinguish between when the blog pings itself back and when someone else comments or sends their own pingback or trackback. I’d calling these self-pingbacks “forward links”, and although I have no desire to get into the trackback/pingback standard debate to suggest making forward links identify themselves, I think we can do something with WordPress. I have in mind something that looks like this:

Date

Title
/ – –
{Body of Post}
– – /

Posted by {me} as {List of Categories} at {time}

Updates: (or “Forward Links” or something configurable)
{Date-time} {Forward Link, showing Title} {Excerpt/Summary?}
{Date-time} {Forward Link, showing Title}

{#} Comments (not including forward links)

or the Forward Link section could look like this, relying purely on the linked post’s title:

Updates: {Forward Link}, {Forward Link}

Off the top of my head, I don’t know whether this could be achieved at the plugin or the theme level (probably both), or if it would require a core files hack. Although I think I could figure out how to do it, I just don’t have to time to do so. But it sure would be nice.

If you’re just running this query, the variable wpdb is not being resolved. In the original useronline-install.php file, you also had the declaration
require_once('../wp-config.php');
which supplied the database name. Why are you trying to run this query alone instead of running the useronline-install.php file?

If you’re using the img button to insert the image, you’ll end up seeing the html code for the link i.e. img src=”…” alt=”…”

Just add another attribute inside the tags – width=”XXX”. I’ve done it before and used 640 – the pixel width I wanted, which worked fine for me using two sidebars and 1024×768 resolution. Don’t worry about height – your browser with scale it with the same aspect ratio.

Note that the image download will be slower as your browser resizes the large image to fit the sixe you specify.

Excellent idea – it wasn’t quite right, but it put me on track to find the answer. Using my FTP client I noticed that my edit-form-advanced.php file had a size of zero bytes – apparently there was a glitch in my upload. Thanks a lot!

After my upgrade to 1.5.2 from 1.5.1.3, my Write Post subpanel disappeared from the write post tab in Write. I followed the update guidelines on the Codex but admit that I forgot to disable plugins, however none modify the write post function.

Then I found that if I changed from advanced controls to simple controls, the write post subpanel reappears. But if I try to access my drafts, the write post subpanel does not appear, even with simple controls selected in options. I had a few hacks, basically only format changes – change the font in the admin.css, for instance, all precisely documented ( I saved my fc /N outputs in text files.) Any clues where to start troubleshooting this?

Woah! Forget the hack functions.php option. It results in “Parse error: parse error, unexpected T_VARIABLE in …/wp-includes/functions.php on line 747.” The hack was a year old, and it looked like it would work, but it doesn’t.

Some spirited discussion here. I fall in the don’t-want-those-ugly-pingbacks-in-my-comments and hate-those-stupid-emails camp myself, but I see the point of those who think automated forward linking is a good idea. So what’s the best solution? Hacking the functions.php (which will disappear next time I update,) using gregh’s plugin (but I don’t even want to moderate those pingbacks,) or disabling pingbacks altogether? I really think there ought to be user-set options, and I think the active debate here shows that.

Thanks to you, Lisch. I was trying the same thing, following closely the https://codex.www.ads-software.com/Adding_Administration_Menus guidelines and examples, and it wasn’t working – but you reminded me I had to activate the plugin. Duh!