[djoep]

so sorry to hear that but thanks for the reply.

[djoep]

Sorry, but I believe you have missed the point of the original post. Please read this entire post before responding. It’s a little long, but not that long.
Neither the original poster, nor I, had any complaints about the operation of installations we had made ourselves. What was being asked, was whether there should be concern due to the obvious problems on the buddypress website itself, not our own installations.
We, the user community, have no way of knowing, other than by asking, if the problems on this site are due to use of an old version of BuddyPress, use of an unreleased version of BuddyPress, use of a broken theme for BuddyPress, or perhaps even maybe they have nothing to do with BuddyPress at all. However, problems that show up on this site beg the question as to whether or not as yet unseen problems might show up on our installations. So, when we ask… “why do I get a white screen when I click on page 2 of the buddypress support forum” this should not be considered a criticism of BuddyPress or it’s developers… it’s merely a question.
We, the user community, would like to have some idea of what we’re getting into. I personally feel fairly comfortable with getting into the guts of most php applications, but I do not have the ability to get into the guts of the implementation of this site so there is no way for me to answer my own question.
For those that are responsible for implementation of the site, I still don’t see any reason whatsoever for offense just because someone points out a defect and asks regarding its cause. If the people responsible for the implementation of this site are too busy to look into it, fine. I can completely relate to that. If the site is built on an obsolete platform that is not worth troubleshooting, fine. I can completely relate to that as well. If the site is built on a platform that is in development and as yet incomplete or unstable, fine. I have no problem accepting that. What I do have difficulty with is being told that merely pointing out the defective behavior on this site, and being told that it is offensive to ask about it.
So have I made myself understood that I am not complaining about BuddyPress software, I am just asking what it is that is causing the buddypress.org website to behave in obviously undesirable and perhaps unexpected ways.
joe

[djoep]

Sorry, but I believe you have missed the point of the original post. Please read this entire post before responding. It’s a little long, but not that long.
Neither the original poster, nor I, had any complaints about the operation of installations we had made ourselves. What was being asked, was whether there should be concern due to the obvious problems on the buddypress website itself, not our own installations.
We, the user community, have no way of knowing, other than by asking, if the problems on this site are due to use of an old version of BuddyPress, use of an unreleased version of BuddyPress, use of a broken theme for BuddyPress, or perhaps even maybe they have nothing to do with BuddyPress at all. However, problems that show up on this site beg the question as to whether or not as yet unseen problems might show up on our installations. So, when we ask… “why do I get a white screen when I click on page 2 of the buddypress support forum” this should not be considered a criticism of BuddyPress or it’s developers… it’s merely a question.
We, the user community, would like to have some idea of what we’re getting into. I personally feel fairly comfortable with getting into the guts of most php applications, but I do not have the ability to get into the guts of the implementation of this site so there is no way for me to answer my own question.
For those that are responsible for implementation of the site, I still don’t see any reason whatsoever for offense just because someone points out a defect and asks regarding its cause. If the people responsible for the implementation of this site are too busy to look into it, fine. I can completely relate to that. If the site is built on an obsolete platform that is not worth troubleshooting, fine. I can completely relate to that as well. If the site is built on a platform that is in development and as yet incomplete or unstable, fine. I have no problem accepting that. What I do have difficulty with is being told that merely pointing out the defective behavior on this site, and being told that it is offensive to ask about it.
So have I made myself understood that I am not complaining about BuddyPress software, I am just asking what it is that is causing the buddypress.org website to behave in obviously undesirable and perhaps unexpected ways.
joe

[djoep]

How anyone could find “hey did you know blah blah is broken on your site” offensive is baffling to me! It has nothing to do with being a programmer or not. It’s like someone pointing out that your shoe is untied or fly is open. The civil response is “thank you for telling me”.
I have in the past though worked with people who were so sensitive about any criticism whatsoever that they did not want their “issue tracking system” called anything like that or “bug tracking” or “defect tracking” etc. I think they wanted it to be something like “topics for conversation”. Having users confronted with a white screen is not a defect, it’s a topic for conversation
I hope it all works out. buddyPress seems to have some real potential.
joe

[djoep]

It’s simple enough to set up a separate install on a live host, you just can’t put both in the root directory, right?
I personally like doing all my initial install, configuration, development and testing using a local install, but before I go live I also like to try it out in the production server environment.
joe

[djoep]

On a similar thread I was told that there was some sort of “retrofit” going on and that I should check the buddyPress demo site.
I checked the buddyPress demo site and there was absolutely no information regarding the buddyPress forum bugs. However, the thread I started got locked so I could not respond.
Might be worthwhile putting your comments over on the wordpress plugin forum for buddyPress so people know what they’re getting.

[djoep]

hmmm… I think I might consider a completely separate install under a sub domain or separate path so I could also experiment with a completely different set of plugins, wordpress versions (like 3.3 beta), as well as themes. I am not familiar with MU to know if you can have such independence, for example, having two versions of buddypress installed at the same time.
joe

[djoep]

hmmm… if it were me, first I’d try disabling all other plugins and selecting the twentyeleven theme before activating buddypress. then select the buddypress default theme, then activating the other plugins one at a time.
If all that works, I’d then create a child theme for the theme I wanted to use with no content other than the required style.css bare bones file. Then I’d use the buddypress template pack to modify my child theme to be buddypress compatible and finally, activate the modified chiled theme.
good luck,
joe

[djoep]

this is still a problem. Is it a universal buddypress problem or just buddypress.org?
I go to this forum page at:

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/

then click the “2? for page 2 up by the “who’s online”.

I get a white screen and it acts like it’s trying to connect forever.
interMike’s issue is not relevant.

[djoep]

To be specific, I go to this forum page at:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/

then click the “2” for page 2 up by the “who’s online”.

I get a white screen and it acts like it’s trying to connect forever.

One odd thing is that if I copy the link address from the “2” link and put it in the address field for the browser, it seems to work. Maybe some sort of AJAX problem???
joe

[djoep]

Does no one else see this problem? I have tried on both firefox and safari just in case it was a browser or plugin related issue but both act the same.
On this forum I can not get to page 2 (or any other page) of the postings! The screen goes white and buddypress.org never comes back again.
joe

[djoep]

Also regarding 1.5 -> 1.6

1) I understand that 1.6 will be using bbPress 2.x plugin for group forums. Is this correct? If so, will it be using bbPress in such a way that bbPress forums, topics, posts, replies, and comments will be stored as custom WP posts?
2) I can’t seem to figure out where one might read about 1.6 so this may be obvious to others, but is there any chance that 1.6 will also implement buddypress groups, activities, etc as WP custom posts rather than in BP specific db tables?
Thanks very much,
joe

[djoep]

@r-a-y Thank you! It does help a great deal. Searching the source is OK, but is there perhaps a dictionary of template tags and their meaning somewhere?
joe

[djoep]

Which begs the question… when if ever is is_single() true in bp 1.5 and what should be used instead to test for pages where text areas might appear?

[djoep]

whoops! found it, fixed it, behavior was due to plugin testing for “is_single()” which apparently was false for all of the buddypress pages.
joe

[djoep]

I posted something that might be helpful over on the bbpress forum. WARNING, it is NOT simple! It is not without possibility of hazard. I would strongly recommend that you do all of your trial and error in a development environment, not on your live site!!!
Why have both group forums and site wide? I think it makes a lot of sense in some cases. For example, a site wide forum can have a completely hierarchical structure without regard for any group. At the same time, a group can carry on a conversation that would be of no interest to the larger population. So a knitting group could have hundreds of posts about yarn, needles, etc, that are not visible on the site’s forum while the site’s forum could have announcements, talk about the local community, etc that are of general interest but not associated with any particular group.
BTW, it appears (to me) that the “site wide” option installs the bbPress 2.0 plugin which uses wordpress custom post types, custom taxonomies, etc, while the group forums appear to use a version of bbPress 1.x that uses separate db tables. I could be mistaken in this.
joe

[djoep]

If you change the name of the plugin folder, through cpanel or by other means, wordpress will automatically deactivate the plugin and you should be able to get back to wordpress. I had the same thing happen with a theme.
joe