texet

This works for me:

* {
word-wrap: break-word;
}

You can also just apply that as a style rule to a {} or p {}.

As far as I know, the P2 theme works fine in IE with the exception of this AJAX replies problem. Are there other incompatibilities with IE?

noel, I have the exact issue here and have the same specs as cheovent:
WP(MU) 2.9.1
P2 – latest from the themes repository

In addition to the error message, the AJAX processing of the replies seems “broken” somehow in MSIE 8.0.

FWIW, I tried deleting line 41 as cheovent recommended, but it doesn’t remove the error message.

nice fix, thanks!! it seems ok to me. hopefully the developers will pick up this bug fix for the next release.

I’ve also got this exact problem. Attempting to install BP on WP, not WPMU

hmm… I don’t think so. I’m getting the same error.

Will try the old-fashioned manual upload…

here’s some code that you can use in your prologue_comment function to restrict comment editing:

<?php if ( $comment->comment_author == $current_user->user_nicename || $comment->comment_author == $current_user->user_login ) edit_comment_link( __( 'Edit' , 'p2'), ' | ',''); ?>

again, this doesn’t take care of the admin panel – users who find that will be able to edit comments. you could either insert similar code somewhere in the admin area, or use the “adminimize” plugin to hide the comments admin area from Authors.

If anyone out there is trying to do this: one way to accomplish it is to edit your kses.php file to specifically include allowed tags

OK, fresh install of WP, default theme:

Authors:

CAN edit COMMENTS on their own posts. of subscribers, anonymous commenters, or even admins.

—
So to achieve this democratic ideal of twitter-like equal authors, you’d have to override the default behavior of WordPress in the prologue_comment function, somehow, such as:

“If the logged in user is the comment author, THEN display the edit_comment_link”

This is still a problem if you ever decide to allow access to the Dashboard, because there, Authors will still be able to edit comments on their posts.

It’s this whole Comment/Post dichotomy that is sooo Web 1.0…

Doh!! Is it maybe a default behavior of WordPress that Authors are allowed to edit any comments that appear on their posts??

(dlopeman, I think you might have been confused in post #2, where the OP was asking about an Author’s ability to edit COMMENTS, not POSTS…)

If it’s a default WP behavior that Authors can edit comments on their own posts, then getting back to the OP’s comment, WordPress is simply not set up, out of the box, to accommodate a “democratic” twitter-like community of equal authors (presumably what many P2 users are trying to do).

I could not find any WordPress documentation saying what Authors are allowed to do with comments on their own posts, but in the backend of my WPMU installation, my authors have the ability to edit and delete comments that appear on their own posts.

I will try a fresh WP install and see what Authors are allowed to do.

I have the same problem (Authors are able to edit each other’s COMMENTS, seemingly at random sometimes).

I do not think this is a problem related to creating 2 users locally. I just set up a proxy user, obviously using a new IP, and he/she is able to edit comments on his own posts.

It does something. It changes the PERMALINK URL.

So instead of
https://www.site.com/here-is-my-title-here-is-my-post

You get:
https://www.site.com/here-is-my-title

the lack of H2s is the problem. Somehow, there must be a way to insert $title into post_title using the .js files.

here’s the deal:

1. this is a very small function that was somehow deprecated and/or removed from WP recently.
2. It doesn’t matter. the title gets updated anyway. despite the error, the widget title will update.

the end.

can’t wait for the p2 2.0! do we really have to wait for WP 2.9?

here’s the deal:

1. this is a very small function that was somehow deprecated and/or removed from WP recently.
2. It doesn’t matter. the title gets updated anyway. despite the error, the widget title will update.

the end.

can’t wait for the p2 2.0! do we really have to wait for WP 2.9?