geoffe

If you want to quash trackback spam and don’t want to go into every post to turn off Allow Pings, you should use this query in phpmyadmin to disable all trackbacks and pingbacks:
Update wp_posts set ping_status=”closed”

where wp is the prefix you would be using for your WordPress tables.

This will disable trackbacks on all posts.

And if you want to quash trackback spam and don’t want to go into every post to turn off Allow Pings, you should use this query in phpmyadmin to disable all trackbacks and pingbacks:
Update wp2_posts set ping_status="closed"

where wp2 is the prefix you would be using for your WordPress tables.

This will disable trackbacks on all posts. I had the same trouble as you, did this and problem solved.

see here https://www.ads-software.com/support/topic/107931?replies=6#post-531336

RScott, when you disable ping/trackbacks it only sets the default for future posts, yet you need to fix your current posts.

To do that, you could use this query in phpmyadmin to disable all trackbacks and pingbacks:
Update wp2_posts set ping_status="closed"

This will disable trackbacks on all posts. I had the same trouble as you, did this and problem solved.

I believe I have the answer to your trouble right here:
https://www.ads-software.com/support/topic/106361?replies=13#post-519016

You have to disable ping backs and while there is a way to set the default for future posts, you need to fix your current posts.

To do that, you could use this query in phpmyadmin to disable all trackbacks and pingbacks:
Update wp2_posts set ping_status="closed"
I had the same trouble as you, did this and problem solved.

There really needs to be a feature in WP to set this automatically because it’s a problem for a great deal of people. A great deal of people who had labelled their forum posts with the tag spam. But the moderators here must be behind all the trackback spam, because they don’t want you to know about those people who have all had trouble with this. They’ve killed the spam tag. They’ve brutally murdered the search function repeatedly. All these helpers will repeat their mantra of spam-killing solutions while avoiding the root of the problem. We must unite! …under the umbrella of the spam forum tag.

Me, I’ve got my tin hat and my Update wp2_posts set ping_status="closed" and I’m ready to rock this problem.

Oh and change the table prefix of wp2_ if you need to and don’t wear a tin hat if you have blond hair. Use a teflon pan.

… and then you can enable your comments again. I believe that the system for trackbacks needs to be changed but nobody listens to me anyhow. I’m just a crazy guy who can’t stop ranting about the conspiracy against solving spam, the guy who gets all nuts every time he hears the standard mantra of use Akismet, use SpamKarma, use your toothbrush. A load of bull. There’s a problem in the system but they don’t want to see it.

There used to be a lot of posts when you visit https://www.ads-software.com/tags/spam and I notice all of them are gone now.

What happened?

If you don’t need trackbacks, make sure that all ping_status values in your posts table is set to ‘closed’.

There is no global option to disable trackbacks as far as I’m aware.
https://www.ads-software.com/support/topic/106361

I’ve gone through the same trouble:
https://www.ads-software.com/support/topic/103650

Although deselecting “Allow link notifications from other Weblogs (pingbacks and trackbacks.)” will prevent future posts from allowing pingbacks and such, it does not solve the problem for current posts.

To fix that, you need to change the ping_status field of your posts table in the database from ‘open’ to ‘closed’. Or, go to each post and deselect the option to allow pings.

There ought to be a global option to disable pingbacks, but as far as I’m aware there isn’t. There is a global option for comments to be restricted to registered users, as well as an option local to each post that can be overridden.

Apparently the trouble is that there is no way to set a global option for posts to disallow pings and trackbacks.

My solution was to edit the db to change all posts with an open ping_status to closed.

The option to disable pings only sets the default for new posts, but does nothing for old posts.

Your other possible method is to go to each posts and uncheck the allow ping field (above allow comments).

I still think that it’s an ugly hole for spam to get through and that there should be separate moderation schemes for regular comments and trackback comments. And a way to completely disable trackbacks/pings alltogether.

I must point out that it’s weirdness, not wierdness.

That’s just weird.

Does no one else experience this problem or am I not asking in a proper way or channel?

I had it happen again tonight, an unregistered visitor attempting to post spam. As all comments are moderated, it doesn’t go far, but I’d still love to know how the requirement to register is not 100%.

Also, Allow link notifications from other Weblogs (pingbacks and trackbacks.) is disabled.

Has anyone else discovered an issue with the restriction to registered users not actually working?

I have registration disabled as well, yet I would get comments. Has happened only once since upgrading to 2.0.7, but I’d like to know if someone has discovered this problem before I try hunting it down.

I had a problem with it, but discovered that after I upgraded WP, I had lost my settings for the wp-contactform plugin.

And so the settings were set to default, which does a bugger job of letting you know that this is the problem. But maybe that’s yours too.

the URL has moved to https://guff.szub.net/2005/02/26/the-excerpt-reloaded/

however you may need something more specialized to get that done handily. But if you go this route, you might want to see https://www.miklb.com/blog/2006/my-site/thumbnails-on-home-page/

It can absolutely be done, but your needs should dictate how it should be done.

The _e() function used to be in a file called wp-includes/wp-l10n.php which is going to be renamed to wp-includes/l10n.php.

There should still be a reference in your wp-settings of
require_once (ABSPATH . WPINC . '/wp-l10n.php');
Perhaps your wp-settings.php in the wordpress root folder is the problem.