quasistoic

Reporting back, nine months later:

The wp-hackers list pointed me to this bug report:
https://trac.www.ads-software.com/ticket/1786

which appears to have been resolved by using wp_die() instead of die() in the wp-comments-post.php file. I suppose wp_die() must be hookable.

These changes made it into the wordpress trunk on July 5th, but somehow didn’t make it into the 2.0.5 release on October 27th. It looks like they still haven’t made it into the 2.0 branch, and thus probably won’t make it into the 2.0.6 tag, which was apparently due 5 days ago.

Looking further into this, the wp_die() function is slated for the 2.1 release, which does not yet have a date on the official roadmap.

Just as an update: this seems to only occur if the database and webroot are on different servers.

I’m having the same problem, except that I’m using today’s WP 2.0.3 and a *real* Movable Type Export (exported from version 3.2).

Ah, LesBessant, thank you! Sometimes the most obvious ideas elude us. I’ve been on wp-hackers for nearly two years.

As it turns out, there was a brief discussion about this very thing on the wp-hackers list in October 05. I’ve inquired as to the state of affairs, and will report back as necessary.

I agree with chtito. Form error handling in wordpress needs an overhaul. Are there any plans to implement hooks for error handling so that I can customize the way I deal with errors via the API, or am I going to have to hack out wp-comments-post.php and the other offending files, only to be forced to constantly diff and merge whenever there’s a WP update?

This IS a support question.

That’s one hilariously big “whoops”. I found the same problem on my 1.5.2 install today.

Podz,

Repeatedly closing these threads is bad form. If this issue is going to be discussed (which you have no control over), it would be better to have it discussed within the community, here on the forums.

If I need to post this in the “Criticism” topic, I will. There are too many hypercritical non-WP-users out there talking smack about software that we care about dearly. One of the biggest defenses that we can offer is that WordPress listens to its community. Let us speak our minds.

jsmishell: I’m working on it. I got the required Cache Plugin installed and got rid of the errors it gave me at first, and I’ve done the same with the Audioscrobbler Plugin, but I’m still not getting any data output. It seems that my cache files aren’t updating (they’re completely empty), but I don’t know exactly where the problem lies.
I’m not a Php wizard, and I couldn’t write something like this from scratch for the life of me, so I’m trying to contact Alex Stapleton (the author) to get some assistance.
If I can get this thing working, I’d be more than happy to update the wiki with step-by-step instructions for both plugins. The steps I’ve had to go through so far were not incredibly intuitive, so I can see how the docs would be necessary. Audioscrobbler is one of my favorite toys, and I’d love to see more people using it.
(By the way, even though AS signups are currently closed, they’re still open for Last.fm, which shares the same database.)

jsmishell: I’ve been wanting to drop this into my own weblog, but I have hesitated because I haven’t seen a successful implementation yet and I’d like to know what it looks like first (the example linked in the wiki has been gibberish every time I’ve clicked through).
Seeing now that there’s someone else interested, I may allow myself to be the guinea pig. I’ll let you know when I go through with it, but the next few days are looking really hectic for me, so it may be a week or more.

Not sure I understand the rquest:
Do you want to display only the comments on a particular post? I believe I saw a hack for this somewhere….

By the way, the most useful tool I’ve ever come across for page design is the EditCSS plugin for Firefox.
If you install no other plugin, let this be the one.

desk003: the most common solution to that involves using a background image.
See here: https://www.alistapart.com/articles/fauxcolumns/

Now, is there any way, when reading your weblog, to view all categories except asides?

Sadly, I chose to give up on Alex’s style switcher.
I’m using A List Apart’s Php Switcher script instead, which works fine for me. It means a little more hard-coding, but eh, such is life.

Alright…I’ve already posted about this over in another thread, but this one also in on-topic, and may even have been the more appropriate venue, considering the specifics.
I’m getting no love with Alex’s 1.2-Compatible WP-Style-Switcher and WP 1.2beta. My server’s running FreeBSD/Apache and I’m getting almost exactly the same symptoms as rfrancis,

The list of styles appears without error in the menu bar. When I select one of the 3 alternate styles from the menu the URL shows the new style (index.php?wpstyle=dots), the page refreshes and the style remains the wp-default style.
If I set a different default style as the readme file explains to, the new style applies fine, but again using the style-switcher menu of styles does not change the style of the page.
In both cases the refreshed page *does* know which style should be loaded, as it grays this option. It just doesn’t apply the style to the page.
Keying in the url with the ?wpstyle=dots (for example) does not change the style either. I’ve also checked each style.css file, and they are there as intended.

with two differences:
1. no style in the list is ever greyed-out.
2. the cookie IS being set (to the correct value) on my computer (it shows in Firefox’s cookie manager). It must not be getting called properly.
Also, this website is on my hosted account, not running on a local server.
Please take a moment and look at the symptoms: https://quasistoic.org/ts/
Respond if you have any guesses or questions which might guide me in the right direction.