2. All kinds of advice to no avail (i.e. putting code at top of .php file, removing forward slash before root, etc. etc.

3. Company programmers where I host did test on different server using basic WordPress and bbPress and attained exact same results. Not a directory issue, not a database issue, not a server issue. They also tried other methods/versions of the “require_once” code but kept getting same errors.

That looks like php and then the characters after the “PHP” look like what happens when you paste fancy quotes from a copy of a website. Maybe the opening quotes are similar and causing similar trouble.

Your include statement should be something like:

require_once('../wp-load.php');

If your bbPress installation is in a directory one level below WordPress (i.e. the ../ goes UP one level to find wp-load.php). You can also use a full path there instead of the relative path. In that case, it would look more like:

Thank you for the link. I/We followed it twice, and several other links/instructions prior to posting the issue. Also, the web hosting provider (a programmer) followed the instructions. The instructions seem to be accurate; we’re just trying to figure out the “hidden” issue. What is strange, is that integration IS working; i.e. “bbPress integration” plugin is installed and active in WordPress. And “WordPress Integration” plugin is installed and active in bbPress. No issues.

It’s only when we attempt DEEP integration the problem arrises. And that the web hosting provider (programmer) is getting exact same errors, on different environment, servers, etc. is not encouraging. More details in my response to Chris (following this one). I REALLY appreciate your help.

Here is line 65 code EXACTLY as entered in bb-config.php, on different attempts. Only difference between the two is “/..” Nothing has been altered…I copied these lines directly from the bb-config.php file adding/changing/hiding nothing. As-In, they are direct cut and pastes.

Warning: require_once(/home/content/08/123456/html/website/forum/wp-load.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/08/123456/html/website/forum/bb-config.php on line 65

# 4. This is how the command line(s) appears exactly as entered inside the bb-config.php file. I copied it from the bb-config.php file without changing anything:

*/

define( ‘BB_LANG’, ” );

require_once(dirname(__FILE__) . ‘/../wp-load.php’);

?>

# 5. Random Thoughts:

a. Important: I don’t/didn’t want to combine bbPress and WordPress locations/databases so I have bbPress and WordPress on separate databases (same server). That said, I notice in the WordPress Integration “settings” (within bbPress) The “User Database table prefix” is set to “wp_”. The bbPress Help line/instructions below the field entry reads, “If your bbPress and WordPress sites share the same database, then this is the same value as $table_prefix in your WordPress wp-config.php file. It is usually wp_.”

I was instructed to enter “wp_” but am beginning to wonder if that is incorrect since the bbPress and WordPress are on separate databases. If incorrect, there are no suggestions of what line/text to enter in that field (“bb_”?). Just sharing.

b. Silly thought?: WordPress 3.0.1 came out 24 hours before my attempt to Deep Integrate, and was installed, wondering if something has changed in the WordPress 3.0.1 .php files that makes this a “new” issue; therefore requiring an updated deep integration code line. Not blaming WordPress…just sharing the experience.

Warning: require_once(/home/content/08/123456/html/website/forum/wp-load.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/08/123456/html/website/forum/bb-config.php on line 65

That is because the file is not located where you are saying it is located. What is the full filesystem path to the wp-load.php file?

That’s the first thing you need to resolve – how to include the file, based on where it’s located.

It’s really a simple error of trying to include a file that is not located where you are telling bbPress it is located. Have you tried including it as explained here?

You can just hard code the full path to the file there and not worry about it unless you change hosts or directories. To prove that it works, just include it like that and I think you will find that it works once you know and use the actual path to the file.

If you’re worried about changing directories or hosts at some point, you can always use a relative path (with the ../ in front) so long as you use the right path. So far, you have not.

Do you have shell access on the host with something like SSH? If so, finding the path to the file will be easy. If not, you can still find it based on the error messages you’re getting and the structure of your site.

Is this the first time the page has come up blank rather than showing an error? If so, I think you’re getting closer.

Method # 2 above is not correct: you need the filename to be quoted. That’s why you’re getting a parse error.

In method # 1, I think the file is actually there and including it is causing some other problem (a conflict between function names or re-declaring some function.)

If you log in with FTP and look at the directory listing, can you see the relationship between where wp-load.php is and where your forum is? Can you post a screenshot of that file listing showing the location of wp-load.php and the bbpress folder?

Also, do you have access to any error logs? The blank screen is a 500 Internal Server error, which should be logged somewhere. It would be interesting to see what the error is. It might actually show that wp-load.php is being included properly (I think it is) and then there is a conflict between functions.

Are ultimately doing the same thing. Method 2 here is going “up” one directory. Method one here just spells out the whole path. Both are including the same file and both are giving the white screen, which means there is a 500 Internal Server Error being logged somewhere. We need to see what the error is.

The first problem was the path to the file was incorrect (with some methods.) The problem is now that you are actually including the file, it’s erroring out. We need to see that error.

Looking at the two images, you now have the correct location of wp-load.php. It’s up one level from the forum directory. But we’ve already established that. Now to see what the error actually is when you include that file.

That’s coming from your theme. Try switching to the default WordPress theme and see if the error is still present.

I can’t download a copy of the Pagelines theme, so can you post the lines from about 50 to 65 in this file:

/wp-content/themes/iblogpro4_dev/core/globals.php

At least from line 53 to line 61, but I suspect there may be some conditional around it and need to see the whole context. If you want, you can email me that file at chrishajer [at] gmail [dot] com as well. Looks like you will need to try and declare that function only if it isn’t already declared. This would be a modification to the WordPress theme file.

But, try the default WordPress theme and see if integration works, or gives another type of error.

The problem here is that the WordPress theme is from Pagelines and the bbPress theme is too. It looks like both themes have a function called pagelines_localize() and when deep integrating, you get an error since the function name is already in use. The function name should be changed in bbPress probably, or removed (since you probably don’t need it in both places, when you are integrated.) Also, since these are paid themes from the same company, it seems like they should have already heard about this problem, but if not, should be willing to help resolve it.

Didn’t pagelines used to come around here? I remember their avatar I think.

Without being logged in, all you can see is the first post. But a search for pagelines_localize brings up that topic, with 4 voices and 11 posts. I think the support should be carried on there since it does not appear to be a problem with bbPress but with the Pagelines themes.

HUGE help and about what I feared. Not slamming Pagelines, but you can see the issues on the forum you linked to above. They suggested deep integration issues, etc. only to realize they hadn’t given me the proper files to begin with. A lot of my time…poof!

Alright. I’m off. You have done more than enough and I will post such at the Pagelines forum.

Looking at the theme files, the function pagelines_localize is only declared once, but with deep integration, it’s trying to be redeclared. So, wrapping the function in a conditional should work to prevent it from being declared again.

Ok so I’ve got my instance running on Deep Integration but I’ve got a few errors. For one, the headers call but no title displays. Also, I am unable to set how the sidebar is registered. Any thoughts or any help?