Forum Replies Created
-
In reply to: Image alignment
Gotta be mikepratt and apeatling. Just guessing. lol. We were just discussing that on #buddypress irc.freenode.netJoin us.
In reply to: Add Friend – ErrorWhoops. You may have found the last one of these. This is the current line:
require_once( preg_replace('/(.*)/wp-content/.*/', '1', $_SERVER['SCRIPT_FILENAME'] ) . '/wp-load.php' );
This is what it should be:
require_once( preg_replace('%(.*)[/\\]wp-content[/\\].*%', '1', $_SERVER['SCRIPT_FILENAME'] ) . '/wp-load.php' );
I’ll put in a trac ticket. I wonder why I haven’t run across this? I use windows as a dev server.
In reply to: jQuery Problems@PerS you have experience with js? Andy is looking for some help in that area. Another pair of eyes : https://buddypress.org/forums/topic.php?id=847
In reply to: Default status : editor and not admin….There isn’t any configuration option to do what you want. You’ll have to customize wpmu or use a plugin if such a thing exists. Try searching the wpmu forums https://mu.wordpress.org/forums/ or over at
[SNIP] cancel all that.
As I was getting the url for wpmudev.org and their plugins area the front page has this:
http://wpmudev.org/project/default-user-role
This seems to set the default user role for new blog owners. Go figure.
!
In reply to: Members Section for Loggedin User is WSODWhat does the error log say?
In reply to: Understanding code trough BPDEV-PHPXrefNicola! Nice job. Thanks.
In reply to: Homepage working no other links workThe install docs tell us that we need to follow the directions in:
/mu-plugins/buddypress-theme/readme.txt
to get the themes in the right spots.
In reply to: Forum Flaw (no formatting)In the mean time : http://code.ourcommoninterest.org/2009/01/12/group-forums-fixes/
In reply to: jQuery ProblemsYou’ve probably got an older version of jquery loading after the bp stuff. What other plugin or custom jquery code do you have running? Two conflicting jquery libs cause this problem.
The widget titles are hardcoded at the moment. Which one do you want to change? Here’s the pattern for each:
Members widget – /mu-plugins/bp-core/bp-core-widgets.php
Lines 12/13 :
register_sidebar_widget( __('Members', 'buddypress'), 'bp_core_widget_members');
register_widget_control( __('Members', 'buddypress'), 'bp_core_widget_members_control' );Change ‘Members’ to ‘Whatever’
If you have them running already they will disappear from the backend and your theme. Just put put them back again.
In reply to: no links work at all (noob)Latest trunk r850 has fix for 404 directory problems.
In reply to: Thesis & Buddypress (HELP!?)Latest bp rev 850 solves the 404 problem. Disable all work arounds!
In reply to: Looking for cropper issue debugging helpHey Andy. Don’t know a thing about js, sorry. Firebug tells me that there is an ‘undefined error’ in the signup environment js. Somewhere. Weird that Firebug doesn’t know.
The same error occurs in the change avatar env, ‘undefined’. There is an additional err in the change av area. common.js is trying to instantiate a google Gears.Factory obj and can’t line 377.
It’s in a try/catch block so I guess FB is just being thorough.
I fooled with both of the crop tools in the signup and change av areas. Ya look at it in FB and lots of numbers are changing and whirling around maniacally. There’s a set of v1/v2 x/y pos nums that seem to be tracking ok. However there are numbers dynamicly changing that refer to the image being cropped as well. Height/Width. Look like they refer to the resultant cropped image.
In the signup area they seem to make sense. In the change av area they look brain dead. Like they have lost relationship with whatever is actually happening on the screen. They only make sense when you reposition the overlay image to top/left. Any thing else they get nutty.
Probably no help at all. You looked lonely here in a thread all by yourself.
In reply to: Personal Profile Forum@nicolagreco The readonly and hidden forums are already done. Two plugins by _ck_ do just that. I’m using those. The problem is getting the info about groups and group members in bp over to bbpress.
It’s not as simple as just including a wp or bp function. bp and bbpress might not be on the same server. They might not even be part of the same mu install.
XMLRPC is the path I’ve chosen. It fits in with the plans I have for bp, blogs and forums in the future.
In reply to: Personal Profile Forumtrent, I just gotta:
get all groups from bp
for all groups make readonly or hidden based on group type
for logged in bbpress user get user’s groups and alter access to specific groups
getting all groups
getting users groups
What I’m working on now.
In reply to: Logged In Page Setup, can I post this here?You might want to check with nicolagreco over at http://buddypressdev.org/ He’s doing alot of theme work.
In reply to: Personal Profile Forumlol. OK stop. Isn’t there already a ‘Burt’ cult? I know of at least one member.
It’s doable, just how is the question. Deep integration, xmlrpc, plain old sql from the wp database. Exploring.
In reply to: No tables createdSeveral people who are on 1and1 have had similar issues. They seem to have problems getting mu configured and bp running.
In reply to: wp-super-cache strategyBack to the is_404 thing. What we need is to tell wp that all is well. A bp_populate_wp_query() fn that fills out the $wp_query var with appropriate noises. Then when catch uri snags an url it can bp_populate_wp_query().
In reply to: wp-super-cache strategyYou guys owe me help refreshing the current page after gen’ing the bp menu bar.
In my ‘community blogs’ plugin I have a form that get’s post’ed. It’s really just a fake form that masquerades as a menu bar top level item. ‘Join! this Blog’, it gets post’ed which is the user saying yes I want to.
We return to the same code and when we return the user gets added to the blog and a new menu item gets hooked up in the place of the ‘Join’ link. Now we got a ‘Success!’ link to indicate that they are now a member of that blog.
I don’t want to just add the user and display ‘success’. I want to refresh the page so that they can see that they are now an author and that this is added to the ‘my blogs’ list in the menu bar.
I just can’t figure out how to do that without getting ‘headers already sent’ errors.
See why I’m playing with headers today?
In reply to: wp-super-cache strategyI’m sure there is a better way of doing things but:
if ( !$bp_no_status_set ) {
status_header( 200 );
global $wp_query; $wp_query->is_404 = false;
}Forces is_404() to be happy. If this is the problem then it’s up to you guys to make it work elegantly and withing the boundaries of acceptable wp behavior. I don’t have much experience playing by the rules or playing well with the other kids.
In reply to: wp-super-cache strategyWhen viewing the member profile $bp_skip_blog_check is null. So the above does happen.
When viewing a directory $bp_skip_blog_check is true, $bp_no_status_set is null so it does status_header(200). The var $pages ($bp_path) is plugin-template.
Then it does load_template() which gets us back to the is_404() question because it extracts the $wp_query->query_vars which have no validity since we aren’t in Kansas.
Template runs and $wp_query->query_vars are showing what? That wp doesn’t know anything about this page.
var_dump($wp_query->query_vars) shows everything is empty except a few things like ‘pagename’ and ‘name’ for member theme profile in the header.
is_404() happily returns true.
status_header(200) doesn’t seem to be enough to convince wp that all is well. What would?
is_404() just does return $wp_query->is_404 which isn’t even set.
In reply to: wp-super-cache strategySo the sequence is: (this is a question)
– user wants bp virt url
– catch uri does it’s thing, the header 200 isn’t sent
– bp starts gen’ing the page
– header query or super cache does is_404()
– we’re not in Kansas any more
– is_404 returns true about not being in Kansas
– page gets gen’ed
Is this logic correct or am I missing something as usual?
In reply to: wp-super-cache strategySo we return from bp_is_blog_page() and exit bp_core_do_catch_uri() at that point and then the check below of:
if ( !$bp_no_status_set ) {
status_header( 200 );
}Never happens if we are gen’ing a bp virt url. That our problem with 404’s?
In reply to: wp-super-cache strategyLooking at is_404() and it’s brethren. These things are part of the wp_query lib that:
* The query API attempts to get which part of WordPress to the user is on. It
* also provides functionality to getting URL query information.
When trapping an url and gen’ing a page based on that virt url we aren’t in wp any more. I see in bp_core_do_catch_uri() that first a check is made to see if this is a blog page. That doesn’t work. The workaround for not gen’ing 404s for directories is to create a wp page that is ignored. We get the title for the page and the directory itself and no 404.
Looking at bp_is_blog_page() I see that all it does is detect if this is a member page, news or a bp component page. Return true else false.
So bp_is_blog_page() returns true for virt urls.
