sofastar

Checking the log-files did not reveal anything. Anybody got the same problem?

What do you mean with “the content of the ‘archives’ folder”?

You should have an installation folder, where all your wordpress files reside. You could delete all files and folders except your wp-content folder (your theme and your plugins are in there!) and your wp-config.php file, and upload all other files again. There should be no need to re-install your weblog.

Maybe there’s another file damaged? add_filter is a function that’s called in the default-filters.php file but defined in another file. Probably uploading the whole bunch of WordPress files again may solve your problem.

< br / > tags are automatically removed, and paragraphes are enclosed by < p > tags…

entering < br / > tags does not work with version 2.0.4, but you can hack functions-formatting.php and comment out line 59, where it says:

$pee = preg_replace('|<br />s*<br />|', "nn", $pee);

don’t know if this causes any troubles, for me it is working right now, i have to use < br / > tags for extra linebreaks though, and it would be nicer if multiple \n’s would work es well…

did you modify single.php?

you have to do it with css, so you just answered your own question ??

This text doesn’t belong to the comment section, you can find this in the single.php template.

I just gave it a try… The text sent with a pingback depends on the html-tags you use in your templates… i just edited some tags and tried to ‘restore’ the status of the default theme, and suddenly the sent text of the pingback looked much more like it should, though it’s still not perfect… I find this to be an odd dependency, which is surely inconveniant!

I think it’s going to be quite hard to figure out what kind of html-tag structure leaves the single.php template in a form that it’ll work for pingbacks.

Got the same problem! When I sent a trackback, the content of my post is shown in the comment WordPress sends, but if I enable automatic pingback, some strange data is sent with the comment… Any ideas?

I applied RonR’s hack to WordPress 2.0.4 because this issui still seems not to be fixed. The hack works great, thanks to Ron!