dille

It’s not really going to help you, I’m afraid, but it works in my 2.9 setup. That would make it a “2.9 with certain hosters” problem; there’s a few of those.

…And what if you don’t control the PHP version on the server? Some people still use shared hosting (me being one of them) and even though I whole-heartedly agree with everyone on the merits of PHP5: if they won’t upgrade, there’s not much I can do, short of finding me another hoster.

That might happen anyway, but in the meantime, is there any way to use OpenID?

My problem was solved by adding a line in /index.php, just before wp-blog-header.php gets included:

define('WP_USE_THEMES', true);

After upgrading a blog from 1.5 to 2.3.1, all pages that were not in wp-admin showed up blank.

When comparing /index.php with /wordpress/index.php (the former being “old”, as in “already there in 1.5), I found out that in the NEW index.php, there’s a define before the wp-blog-header.php file is included. After adding that to the /index.php file, everything was peachy again:

define('WP_USE_THEMES', true);

This makes perfect sense, of course, but since you get NO OUTPUT whatsoever, it’s a bit hard to figure out. Hope this helps someone.

You want to google for “wordpress bbpress”, that should get you going. At least as far as combining wp users and bbpress users.

I’m currently hooking the two up for a customer’s site. Maybe it’s my apache/php setup, but I require extra work to let the bbpress users actually log into wp — it involves a bit of code to update the proper wordpress tables.

Also, I can’t go ahead and include the wordpress wp-config.php file. This might be a plugin issue on my side. So this doesn’t work for me. Yet.

(small update: I’ve disabled most plugins, but the error logs tell me that bbpress and wordpress try to define the same functions. In other words: forget function integration. Bummer.)

Well, actually, I was able to solve my own problem.

As it turns out, the problem occurred in posts that contained apostrophes (‘). I assumed that those would be escaped by the various filtering functions that the data is trown through, but I was wrong. That resulted in MySQL errors, and since these are pretty much suppressed within WP, no info to work with =]

A quick $wpdb->escape() before I feed the data to wp_insert_post() and all is well.

What irks me, though, is that this isn’t captured by the filtering functions. I can post content with apostrophes in them, so where’s the big difference when importing? Does this qualify as a bug?

Maybe it’s superfluous info, but the fact that you’re not able to *send* ping-/trackbacks may be a firewall issue. The system relies on being able to connect to the receiving weblog over HTTP, so if your host blocks port 80 outgoing (I know mine does) you’re outta luck. That should also mean you’re unable to ping to pingomatic.com. Oh, and it means that you should be looking for another hoster, because blocking port 80 is just plain evil.

You can check your connection skillz here.

(boing)

Moshu: it’s not really the same. The method described there is about creating a link that’ll take you to the comments box when clicked. I want to be taken to my own comment (or at least the start of the comments) automagically after I’ve posted a comment.

@BebiRoxors: Yes, the fix was for an older version. In case you didn’t have it solved: the method was changed. Now, you can specify a “redirect_to” parameter (using a hidden input) which the script will jump to after doing it’s thing. If the parameter isn’t supplied, it jumps to the referrer (IMO that’s a bad thing — not all browsers will specify a referrer, or not a correct one, but that’s another matter).

Simply change
wp_redirect($location);

to
wp_redirect("$location#comments");

or to
wp_redirect("$location#comment-$wpdb->insert_id");

…if you want to jump to the comment that was just posted. Note: if the comment wasn’t posted, or if it hit the moderation queue, it’ll jump to a non-existent anchor, which means no jumping.

Of course, you could go all groovy and change the template to include an anchor (let’s say #lastcomment) right before the last comment, and jump to that. That’ll always work, or at least until the next WP upgrade.

edit:
Aw, heck, it’s a simple hack anyway…

1. Inside the comments loop (usually right after the <li> element, but this may not be the same across themes), before the name and comment and everything, you add this line:
<?php $commentcount++; if ($commentcount == count($comments)) echo '<a name="lastcomment"></a>'; ?> (all on one line)
2. Have the comment-post script redirect to “$location#lastcomment” (see above)
3. Feel totally groovy. At least until the next upgrade…

@marc: an entry doesn’t have to be all that long — just had a look at your site, for example the “Sometimes you ask why”-post, and really, I can’t see any comments when I’m at the top of the page. Maybe you have a big-ass screen in front of you, but this laptop has a pretty standard 1024×768…

Apart from that: after a couple of comments, everybody has to scroll — even if one of the comments _was_ made by Tolstoy.

Not that that means that I’m not quirky, of course =]

@root: what exactly do you mean by that? I’m not that shy of re-engineering, but why would it be a neccesity (spelling may suck, it’s way past bed time)?

@zack56: As in Esher art? (I can’t seem to find the one that springs to mind on Google; the same effect was in the plugin icons for older Photoshop versions)
That might actually be bloody brilliant! I envision hell with the shadows and the white “outline” around the center column, but I might give it a try. =]

Thanks for the feedback (so far, more is always welcome!)

…that, and/or they’re referrer-spamming him. It has been happening to my GF too, her blog suddenly took up > 1Gb/month, instead of the 200~300 MB it usually does, and *LOTS* of referrers to all kinds of pr0n. Blocking a few IP ranges in Apache’s httpd.conf (yes, globally) halted that.

But that’s not WordPress-related.

That’s real nifty. I *assume* that, at some point, this setting will be moved into the database, right?

Also, does anyone know if the feed is cached? I just took a quick peek at the code, enough to see that Magpie is used, but not enough to see if it’s cached.

What happens if you apply 777 privileges to the directory containing the .htaccess file?

Arr 2: sillY, not sillE. I’ll stop posting to forums for a bit, now =]

Arr, made an error when copy-pasting… The original line 821 should of course read

$rewrite_rules += array($uri . '/?$' => "index.php?pagename=" . urldecode($pagename));

Sille me for not checking my utterings…