[kerrick]

I’m getting the same error too. I’m on lunarpages hosting, and I went through “enable php5,” but the error is still there. What else can I do?

Here’s the error:

Warning: cannot yet handle MBCS in html_entity_decode()! in /home/[censored]/public_html/semostudents/forums/bb-includes/wp-functions.php on line 113

EDIT: Alright, I removed php5 and re-added php5, something went wrong with the .htaccess files. It’s working now under php5.

[Ben L.]

@Fender:

You would need to have the link put into the post at the time of display, not at the time of posting. I already emailed you the plugin you asked for.

[Ben L.]

Or, even better, use the database prefix.

[cre8tivexjs]

i tried switching my mt’s Grid server to php5 and the errors are gone …

if you can switch your server into php5 as well that should fix the MBCS error problem.

be careful though as some php4 codes may not work in php5

[cre8tivexjs]

getting the same errors as criketos

I’m guessing that one of the php function used in the new release of bbPress only supports PHP5

http://bugs.php.net/bug.php?id=25670

[criketos]

I would like to install bbpress 0.9.0.4. but at the second step (http://vinblog.com/forums/bb-admin/install.php?step=1).

I have error “Warning: can not yet handle MBCS in html_entity_decode ()! in / home / vinblog / www / forums / bb-includes / wp-functions.php on line 113. “

someone would have the solution?

THANKS

christian

[circuit]

paste the code into the SQL field in phpmyadmin

export the result to a CSV

import the CSV to your bbpress forum tables.

[Fender]

I was able to achieve most of what I wanted to do with almost no core hacks.

I editted my template front-page.php to basically be topic.php but without the re_permalink() ; call and statically setting $topic_id = 2.

The core hack I made was to change functions.bb_templates.php to modify all location query functions to trick it into thinking ‘front-page’ is topic-page instead (these are mostly case statements inside functions like is_front() and is_topic()) , meaning that post.php, post-form.php and /bb-post.php all fuinctioned on my new front page in the same way they would on topic.php. I would prefer to develop a plugin that did this modification, but I don’t have time to make one.

So it essentially does what I wanted it to do, albeit with a core hack that will have to be manually maintained in future releases unless a plugin is developed.

In the last few days, I’ve basically discovered that neither WordPress or bbPress can do more than 60% of what I want, and it’s a different 60% in each case. bbPress has one major advantage for me over WordPress right now, and that is bbPress Moderation Suite. WordPress has nothing remotely resembling it and I doubt I’ll be able to find someone willing to build it, even for cash. But even bbPress Moderation Suite is missing one key thing for me, and that’s email notification to the users, but Nightgunner is working on that one already.

[Fender]

I’ve been playing with this one and there’s a modification I would mind seeing, or some help on how to make the modification.

I’m trying to use the AJAX Quote plugin with this, but unfortunately it breaks. The reason is simple … the AJAX Quote plugin basically copies the id=x&page=y#post-zz into the postbox so that you can find and navigate to the original post being quoted. When using this script, it gets broken because the most recent posts are always on page=1, meaning that when a post that’s been replied to gets bumped to page=2, the link is now incorrect.

What I’d like to see is that the page id’s for a paginated topic don’t change … the earliest post will always be page=1 and the most recent posts will be on the highest page number. I can see that the quoting system can still be broken if the posts per page setting is changed, I know. But assuming it doesn’t change, then this would maintain the integrity of the quote links.

Any ideas?

[John James Jacoby]

Looks like a few changes might be needed unless I’m missing something along the way…

This makes the favorites load properly for me.

includes/functions.bb-users.php

line 221

FROM

if ( !empty($user->favorites) ) {

TO

if ( !empty($user->bb_favorites) ) {

includes/class.bb-query

line 442

FROM

$where .= $this->parse_value( 't.topic_id', $f_user->favorites );

TO

$where .= $this->parse_value( 't.topic_id', $f_user->bb_favorites );

line 559

FROM

$where .= $this->parse_value( 'p.topic_id', $f_user->favorites );

TO

$where .= $this->parse_value( 'p.topic_id', $f_user->bb_favorites );

Basically, there are a few other places where $user->favorites needs to be changed to $user->bb_favorites.

So, I’ve got it up and working from doing the above. I’ve never needed to commit a change to the trac before. Should I just open a ticket, or can I change it directly?

[Ipstenu (Mika Epstein)]

Yes, you should use absolute pathing. Try this:

Redirect 301 /bbpress/register.php http://www.scopedin.com/wordpress/wp-login.php?action=register

You want bbpress/register.php and NOT your theme because the main register.php is actually what gets called.

[mpttt]

Update:

(Nevermind this stuff below. WP does this even without bbpress, it may be the template.)

Removed the cookie code from wp-config above.

Checked “must be logged in to post comment” option in WP Discussion options.

Logged in with a Subscriber account. Posted comment. Tried to click “Logout” on comments page. Continue to get error:

“You are attempting to log out of The Site

Please try again.”

Difference between the URLs in admin vs comments page.

Admin “logout” url: ****/wp-login.php?action=logout&_wpnonce=stringofcharacters

Comments “logout” url: ****/wp-login.php?action=logout

[mpttt]

Hello.

Installed wp2.7 in root dir, and bbpress alpha 6 in sub-dir. Enabled permalinks, added code to htaccess in sub-dir.

Test 1. Logging in to wordpress admin.

Navigate to comments: shows logged in as admin user

Navigate to forum: not logged in

Navigate to forum admin: not logged in

Test 2. Logging in to bbpress admin.

Navigate to comments: does not show as logged in as admin user

Navigate to wp admin: logged in as admin

Is this how it’s supposed to work?

More info:

After adding the following lines of code to the wp-config file:

define(‘COOKIE_DOMAIN’, ”);

define(‘COOKIEPATH’, ‘/’);

This does not change anything except, if I am logged in to the WP Admin, I can not log out. Clicking Log Out presents:

“You are attempting to log out of The Site

Please try again.”

Am I missing something with the code above? Should I be adding the domain name somewhere?

I appreciate your help.

[Ben L.]

$warnings = $bbdb->get_results("SELECT user_id, meta_value FROM $bbdb->usermeta WHERE meta_key='bbmodsuite_warnings'");

Okay, so now I have all of the warnings from every user with them. That was easy, just one query. However, I don’t know any good way to go back to the database, once I loop through them all, since I will need to delete some of the usermeta entries, update the others, and update a second set of usermeta keys designed to lower database traffic. Thank goodness this is only on cron.

How do I update hundreds (or even thousands) of database entries all at once?

[chrishajer]

If there is none there, then yes, you need to create one. Be sure it starts with a period:

.htaccess

That indicates a hidden file on Linux/Unix.

[Ipstenu (Mika Epstein)]

No, it would go in the public_html folder.

And it would be something like…

Redirect 301 /forum/register.php http://mysite.com/blog/wp-register.php

[mzimmers]

Hmm…is this what you’re talking about?

bb_get_uri(‘register.php’, null, BB_URI_CONTEXT_A_HREF + BB_URI_CONTEXT_BB_USER_FORMS),

Replacing the third parameter with the URL of the WP registration page?

Sorry if this is a lame question, but the code in this page is rather obscure to me.

Edit: or is it the first parameter that gets replaced?

[mzimmers]

Hey, circuit – where in the code did you make that change? There appears to be a variable called “register-page” but I can’t find its definition.

[mzimmers]

Oh, I’m sure it works just fine. The “yuk” was elicited by this:

5. search your bbpress templates and force all registrations/logins through wordpress from the several places they are buried on the forum (the WP login interfaces are far more developed) – unfortunately at least one bbPress login location is hard coded in the core which will require a direct hack everytime you upgrade.

I was hoping for something more one-time, but…I think I can live with this.

[circuit]

update: the queries above worked fine with a bit of manipulation (i guess the table layouts on both systems have changed a bit since the above were written, so the number of fields didn’t match in some cases). i didn’t need to update the slugs or use the second bit of code for post freshness – it just worked.

[deadlyhifi]

Specifically regarding the Approve User Rrgistration plugin.

Fatal error: Class ‘BB_User’ not found in …/bb-plugins/approve-user-registration/approve-user-registration.php on line 58

I’ve seen in some other plugins compatible with 1.0 the use of ‘WP_User’ and ‘BP_User’. I’ve tried using these and there is no error, but the plugin doesn’t work…

Anyone know how to fix this? I really need the features of this plugin – it would be really good if it was a standard option in bbPress.

[John James Jacoby]

In my WordPress functions.php file, I am queuing up jQuery for some interface objects I’m using.

wp_enqueue_script('jquery');

It seems this messes with bbPress’s javascript inclusion, causing none of the JS from bbPress ever to get loaded.

Because I am using jQuery also in bbPress, is there a way around this that anyone can think of?

[chrishajer]

> #header div.search input.submit {

> style stuff here;

> }

Well, the cascading part of Cascading Style Sheets means that higher level stuff pertains to lower level stuff, and so on, and so on.

So from the right, an input element, with a class of submit, but only if it’s in a div with a class of search and then only if it’s in an element with an id of header.

So, based on that, the markup in the php file should look something like this:

<div id="header">

<div class="search">

<input class="submit" foo="bar" blah="blarg">

Does that make sense?

> I’ve never seen the “div” used like this, and I’m not sure what the “input.submit” is.

The div.search just ties the search class to the div element (man I hope I’m not mixing up my terminology here…) So, if you had another element on the page, maybe a <p> with a class of search, like so

<p class="search">

This div.search would not apply to this element, because the .search was tied to the div element. Same exact thing applies to the input.submit: only an input element with a class of submit will be affected by that specific CSS.

> Also, it’s not clear to me how the “return” button code comes last in the

> php file, but the button displays above/before the login stuff.

I’m afraid I don’t know enough about it to figure that one out. Sometimes, when it works, it’s best not to question why

One thing that helps immensely with the CSS, for me anyway, is to use Firefox with the Web Developer add-on from Chris Pederick. You can hover over an element on the page and display the CSS classes and ids that apply to it, then click and see the actual CSS. You can also make changes to the CSS in the browser and see them immediately, then once you’ve sorted them out, just paste those local changes into the CSS for your template.

http://www.mozilla.com/en-US/firefox/

https://addons.mozilla.org/en-US/firefox/addon/60

Also, be sure to validate the XHTML and CSS both, to ensure the things you’ve done are in order:

http://validator.w3.org/

http://jigsaw.w3.org/css-validator/

Those two tools are linked from the Web Developer Toolbar.

You will find with CSS there are a lot of invalid things in the stylesheet that don’t hurt anything: they make things look better in some browsers, but don’t do anything and don’t harm anything in other browsers. When adding things to your templates, I would at least validate the XHTML.

HTH.

[Fernando Tellado]

You’re wellcome ericharison

[mzimmers]

No, I’m happy with the result; I just wish I had a better understanding of exactly what I did!

Specifically, I’m not sure what this means:

#header div.search input.submit {

style stuff here;

}

I’ve never seen the “div” used like this, and I’m not sure what the “input.submit” is.

Also, it’s not clear to me how the “return” button code comes last in the php file, but the button displays above/before the login stuff.

Any enlightenment would be appreciated.