Aaah! I found the reason! :-) The serendipity_plugin_comments plugin only hands the email of the commenter and not the url. Gravatar needs an email, Favatar needs an URL. Without the URL information, Favatar is not working, so the Gravatar Plugin directly falls back to Gravatar. So serendipity_plugi...

Hi. I recently added the gravatar plugin to my blog. Nice, I like it. I configured it, that it first tries Favatar. The result is, that the comments directly below my articles use Favatars first and only if not found, try to get a Gravatar. This is, what was intended. But the sitebar plugin serendip...

Thanks for the info.

Are there answers to the first post? As I have the same questions..

In my code the real URI is sent via pingback. Garvin's code was changed a littel and now only the base url is transmitted. If you use my patch above, everything works. I did another patch on base of the source I found in the CVS, that is correcting this problem. If you are interested, I can send it ...

I hope this is no "user too stupid" problem. I downloaded the static pages plugin using Spartacus. So well.. I have no documentation on this plugin so I started creating my first static page. I changed the Permalink, choosed an "Article" static page, changed titles and content an...

Did you change the setting, Garvin mentioned? I guess the upgrade only fixes the bug setting the user's default value to "not publishing" but doesn't change the value once set by former installations.

P.S.: Is there an anonymous access to your version system (is it CVS or SVN?) on BerliOS? I think it is more comfortable fetching the files directly instead of copy and pasting "downlods" from the web interface..

Or will the trunk be in the next nightly build?

As we Germans say: Thanks a lot for the flowers ! :D I like s9y a lot and am very willing to contribute. I diffed your checked in code with my code. You changed the signature of serendipity_pingback_autodiscover and for that you had to change the code of this function. The problem is: With your code...

Well okay. The problem was not, that s9y didn't POST the pingback (it did), but it posted with the wrong content type. Pingback needs text/xml. So I patched the functions_trackbacks.inc.php to make pingbacks work: /** * Check a HTTP response if it is a valid XML pingback response * * @access public ...

I inspected the code, that Slim first posted. This is no dead code at all, pingbacks are sent already by s9y, the function serendipity_pingback_autodiscover is already called in serendipity_reference_autodiscover directy after serendipity_trackback_autodiscover. But the code seems to be just a "...

You want to see it incoporated into the trackback plugin because of performance reasons or why? Is the trackback plugin in a stable state or are you implemnting new stuff? If I add functionalty into this plugin, I don't want to merge code to often.. This was the main reason, why I was thinking about...

Btw: Actualy I'm thinking about implementing pingback functionality into s9y, because the WP books w/o rdf trackback metainfo I've seen in most cases had a pingback link attribute (that could be fetched by the dead code you've mentioned). But I will open a new topic for this. I guess, it should be a...

Yes, of course I can do that. Thougt there is some nice PHP directive switching on the dumping of function names or something. I'll try that.

Ahm sorry.. Patch in what way?