Gerd

Oh, you should add this piece of code after the original style tag, like this:

<style type=”text/css” media=”screen”>
@import url([Your Path]/style.css );
</style>

<!–[if gte IE 5.5]>
… And here is the IE patch …
<![endif]–>

Forgot to mention this, excuse.

And note the sytax is [if gte IE 5.5], not [if get IE 5.5]. gte means “greater or equal” :).

Min-Height is supported by Mozilla, Firefox, Netscape 6+ and Opera only. No IE, no Safari, no Konquerer. IE supports it for table elements like td, tr and th, though – or at least it claims so.

A common trick is to set height for IE only using:

<!–[if gte IE 5.5]>
<style type=”text/css”>
<!–
#insideWrapper{height:600px;}
–>
</style>
<![endif]–>

IE will expand if neccessary, so this should have the same effect than min-height.

Out of the head: I think the correct param to pass is “description” not “blogdescription”. Having an unknown pram let’s WP fall back to the default, which is “name”: The name of the site.

I’m having similiar problems with PHP 1.2.2 on PHP 4.1.2 (Debian Woody). Nothing happens if you create, update or delete custom fields, allthough WP states it was successfull. The SQL WP generates works, I tested that in PHPMyAdmin.

This makes using the TechnoTag plugin quite a pain.

Custom Fields work, however, with PHP 4.3.x.

I slighly get the impression that WP never was tested on PHP 4.1.2 accordingly (though this is still the second wide spread PHP installation), and this make me shiver when looking forward to WP 1.5 with it’s bunch of new code.

No I haven’t solved this, how could I – without a single response? ??

I’ll keep on talking to myself ??

Tried out https://www.tamba2.org.uk/wordpress and it works. However, this server sends a pingback XML containing the following tag hierarchy:

params – param – value – string – /string – /value – /param – param – value – string – /string – /value – /param – /params.

I still tend to blame my problems on the additional array and data tag in the failing pingback requests. Unfortunately, I don’t understand the according code in WP 1.2.2, so I cannot help.

To be honest, this bug really annoys me, since all the sites unsuccesfully pinging me actually are WordPress related sites running WordPress like wordlog.com, for example. And the pingbacks are on articles regarding my WordPress plugin. Duh! WP should be able to process its own requests, shouldn’t it?

Having a short look over pingback and XML-RPC specs, I tend to think that an array tag is not allowed here. Just guessing: May it be this actually is a bug in WP 1.5 sending wrong pingback requests?

A funny bug: enter &lt;array&gt; and look at your post. There should be < a r r a y >, but there is has disappeared…

It’s me again ;-). I switched on debug logging and captured a pingback request that failed:

2005-01-18 16:41:12 Input: <?xml version=”1.0″?>
<methodCall>
<methodName>pingback.ping</methodName>
<params>
<param><value>< array > <data>
<value><string>[Caller URL]/</string></value>
<value><string>[My URL]</string></value>
</data>< /array ></value></param>
</params></methodCall>

2005-01-18 16:41:12 Output: Incorrect parameters passed to method: Wanted , got at param )

2005-01-18 16:41:12 Output: <methodResponse><fault>
<value>
<struct>
<member>
<name>faultCode</name>
<value><int>3</int></value>
</member>
<member>
<name>faultString</name>
<value><string>Incorrect parameters passed to method: Wanted , got at param )</string></value>
</member>
</struct>
</value>
</fault></methodResponse>

May it be my wordpress 1.2.2 gets confused by <param><value>< array ><data>?

Yes, trackbacks and pingbacks are enabled, and trackbacks work.

Interestingly, I can ping myself. This is: If I write an article and refer to one of my prior ones, a comment is added to the this article.

But pinging back from the outside seems to have no effect. I tried it with my local test installation and nothing happended (I am able to trackback, though). Pingbacks I got the last days (e.g. from bloggingpro.com) didn’t show up either.

While I think it is OK that pings from address “localhost” don’t show, I wonder about the others, though. Maybe it’s just some coincidence and there’s a bug on the other side?

It would be nice if somebody can point me to a web ressource to test pingbacks on my side.

Tracing futher it all comes down to this two lines:

if ( isset( $_SERVER[‘PATH_INFO’] ) )
$_SERVER[‘PHP_SELF’] = str_replace( $_SERVER[‘PATH_INFO’], ”, $_SERVER[‘PHP_SELF’] );

Since PATH_INFO and PHP_SELF have the same value on my machine (wordpress15/wp-login.php), the str_replace function simply replaces the whole PHP_SELF with an empty string.

I’m sure this isn’t desired. I was trying to figure out, what this code is instead supposed to do, but since there is no documentation on the PATH_INFO parameter on php.net, I still don’t know.

A temporary solution is to comment out the following lines right at the top of wp-login:

// If someone has moved WordPress let’s try to detect it
if ( isset( $_SERVER[‘PATH_INFO’] ) )
$_SERVER[‘PHP_SELF’] = str_replace( $_SERVER[‘PATH_INFO’], ”, $_SERVER[‘PHP_SELF’] );

if ( dirname(‘https://&#8217; . $_SERVER[‘HTTP_HOST’] . $_SERVER[‘PHP_SELF’]) != get_settings(‘siteurl’) )
update_option(‘siteurl’, dirname(‘https://&#8217; . $_SERVER[‘HTTP_HOST’] . $_SERVER[‘PHP_SELF’]) );

Commenting out is done by adding /* before and */ after the lines like this:

/*
… The code form above
*/

I had the same error on a fresh WP 1.5 installalation taken out of the CVS right today (January 7th).

I installed WP locally under https://localhost/wordpress15. I also changed the table prefix to be “wp15” instead of “wp”. install.php finishes successfully, but when trying to to login I get the following error:

https://localhost/wp-login.php?redirect_to=%2Fwordpress15%2Fwp-admin%2F
404 File not found

Of course the address should be
https://localhost/wordpress15/wp-login.php?redirect=…

I traced it down to the following:
1. After install the option siteurl in table wp15_options is set correctly to “https://localhost/wordpress15&#8221;
2. However, after wp-login.php is called, this has changed to “http:”.