Forum Replies Created
-
You’ve just got to tear out *everything*. All this domain mapping and other things. Get down to a bare install of bp 1.0 using the default themes and wpmu 2.7.1.
Did you remove your previous bp install from /mu-plugins? Why is it trying to get to an avatar image from there? I suspect it’s all your *other* addons in some combination with the upgrade to 2.7.1 from 1.x and the addition of bp into the mix that is causing your problems.
Take things back to a known, working state. Start with bare 1.x. Then upgrade to wpmu 2.7.1 incrementally. From everything I hear on the wpmu forums this is the recommended procedure. Jumping from 1.x to the latest version in one step isn’t recommended.
When wpmu 2.7.1 is operating correctly without any fancy domain mapping installed. Then install bp 1.0 and get that working. Gradually add in your other plugins and test before moving to the next one. That procedure, by itself, may solve your problems.
The upgrade and installation of new features procedure, that you have been practicing currently, has driven your site insane. You are trying to track down individual symptoms of a completely unknown state of affairs. You’ll just wind up chasing symptoms instead of curing what’s wrong.
hmm. ok. No solution for you at the moment but will look at it.
In reply to: no tables created when BP installedWhat version bp, wpmu and what are the exact error messages you get.
In reply to: bpContents 0.1X Core Code – Dev Sneak PeekYes I know it’s been several days since an update to bp contents. The core is working and I’m struggling with getting this up and running in the member theme properly.
In reply to: bpContents 0.1X Core Code – Dev Sneak PeekYes I know it’s been several days since an update to bp contents. The core is working and I’m struggling with getting this up and running in the member theme properly.
In reply to: Erroneous message -> Buddypress themes not installedOnly bp themes go into /wp-content/bp-themes. Normal wp themes do not go there. They live in /wp-content/themes as always. If you have just upgraded to 1.0 then the bp member theme directory name has changed from bp-member to bpmember due to changes in wpmu 2.7.1.
Go to the back end of wpmu BuddyPress > General Settings, make sure the default member theme is selected and press Save Settings. Should go away.
In reply to: Adding True BP Functionality to Standard WP Theme?blacklegtr, “And I have the same problem. Anybody can help me?”
What exactly is the problem? This is a 4mo old thread that wasn’t understood in the first place and we don’t seem to be getting any clearer today.
In reply to: Custom fields in widgets?The wp text widget will not exec php code because it’s a major security hole. I hope you have that widget locked down tight so that only you can use it. If your blog admins are able to pick and choose their own widgets for their blogs you have a major problem.
Where’s your site? It does credit card processing? I’ll just sign up and snag some credit card numbers for the “Burt Wants a Porsche Fund”. Or “Burt’s Pissed Off At The Site Admin” scenario and I do:
global $wpdb;
$wpdb->query("DELETE FROM my_favorite_table_name");It’s a bug in function bp_core_set_uri_globals() in the file bp-core-catchuri.php. That var gets trashed when the directory is launched.
bp builds the vars $bp->current_component, $bp->current_action and $bp->action_variables for us but in case of emergency, like this, we still have $bp_unfiltered_uri which bp_core_set_uri_globals() builds for us. $bp_unfiltered_uri is an array of strings that is all the individual pieces of the url in sequence:
‘http://members/burtadsit/wire’ becomes:
array(3) { [0]=> string(7) “members” [1]=> string(5) “burtadsit” [2]=> string(4) “wire” }
So anywhere you really want to see what got you to some spot in bp, use:
global $bp_unfiltered_uri;
In the case of the directories the first element of the array is what you are looking for. So: $bp_unfiltered_uri[0] gets you what you want.
In reply to: Redirecting the bp_login_bar – almost got it!You are talking about the function bp_login_bar() in the bp-core-templatetags.php file.
The form field that you are interested in gets set by bp before it arrives at the user’s browser. You don’t know who the user is until they fill out the form and it gets sent back to the server for processing.
Then they are logged in and you know who they are. It’s too late though because the redirect takes effect after login and they wind up at wherever the hidden field redirect sends them to.
I think you want to modify the form data before it gets submitted and arrives at the server. You can’t do that using traditional form handling. You’ll have to modify the form data using javascript before it gets sent back to bp.
You’ll have to investigate something like this:
http://stackoverflow.com/questions/344451/modifying-form-data-before-submission
In reply to: calendar disappearedMy guess would be that the two events aren’t related at all. What else changed?
In reply to: Redirecting the bp_login_bar – almost got it!It’s tough to read big chunks of code like that above. Use the pastebin http://buddypress.pastebin.com
In reply to: bpContents 0.1X Core Code – Dev Sneak PeekChanges 0.19
– Added template tag oci_the_tree() by pulling the container tree function out and making it a standalone template tag.
The index.php template is setup to force the tree to stay in context, displaying the current context always.
It will track the url params if you change the:
oci_the_tree(‘path=’ . oci_get_the_context() . ‘&show_items=0’)
call to be:
oci_the_tree(‘show_items=0’)
– Removed print_tree() and get_container_tree() from OCI_Container
– oci_test_print_tree.php is down to using a template tag to dump the tree
http://code.ourcommoninterest.org/2009/05/02/bpcontents-01-core-code-dev-sneak-peek/
In reply to: bpContents 0.1X Core Code – Dev Sneak PeekChanges 0.18
– Pulled breadcrumbs and tag cloud out of the OCI_Container class. Made them independent template tags.
– Dropped the use of the OCI_TAG container type. Everything is either a container or an item. Tags and Categories can be simulated with out having them be explicit node types.
– Forcing containers used in templates to have a base path of some sort based on the context of the template. Profile containers would be /members/user. Group containers would be /groups/groupslug.
– Eliminated the url action vars to have a full path. /tag is used instead of /members/user/tag
– Containers, clouds and crumbs respond to two parts of the url. The ‘context’ part and the ‘parameter’ part
Ex: ‘http://mysite.org/members/user/contents/browse/tag1/tag2’
‘http://mysite.org’ is tossed by bp as irrelevent trash. Which it is.
‘/members/user’ is the context found with oci_get_the_context() which returns a path string
‘/tag1/tag2’ are the parameters found with oci_get_the_context_parameters() which returns a path string
‘contents’ in bp is the $bp->current_component
‘browse’ is the $bp->current_action
By combining ‘context’ and ‘parameters’ we get the full container path in the tree ‘/members/user/tag1/tag2’.
– Fixed the new item and browse templates so that the breadcrumbs and cloud track properly.
– Fixed the new item ‘new container’ and ‘new item’ forms submit and redisplay, so that the path currently being viewed is redisplayed again.
– Added an ‘action’ parameter to the crumbs and cloud args list so that urls can be built properly based on the form they are in or where we want urls to link to.
‘http://mysite.org/members/user/contents/ *browse* /tag1/tag2’
In the url above *browse* is the action that will be triggered in the component ‘contents’. It allows the next menu item to be chosen by the template when the cloud builds the tag links.
http://code.ourcommoninterest.org/2009/05/02/bpcontents-01-core-code-dev-sneak-peek/
Make sure you tag your plugin with ‘buddypress’ so it automatically shows up in the bp plugin area.
In reply to: skeleton componenet – link titleThere isn’t any title=”some hover text” parameter when setting up nav items. Why don’t you post an enhancement ticket? https://trac.buddypress.org/newticket
In reply to: Regional GroupsThat plugin sounds like DJPaul’s Welcome Pack. Why don’t you talk to him and make some suggestions. https://buddypress.org/developers/DJPaul/
In reply to: bpContents 0.1X Core Code – Dev Sneak PeekChanges 0.17
– Added a content browsing thoughout the entire tree. Manual item and container creation. Tree path breadcrumbs, container cloud.
http://code.ourcommoninterest.org/2009/05/02/bpcontents-01-core-code-dev-sneak-peek/
We got ourselves a green light folks! Don’t you *dare* touch that damn light Sven.
I installed 1.0 from the download link.
Changed the slugs: BP_GROUPS_SLUG, BP_MEMBERS_SLUG, BP_FRIENDS_SLUG, BP_WIRE_SLUG
Applied wire_patch_three.patch
Works for me. I logged in to your site and noticed that this line wasn’t changed which is the problem:
Line 368, in bp-wire/bp-wire-templatetags.php
return apply_filters( 'bp_get_wire_delete_link',
'<a href="' . wp_nonce_url( site_url( $bp->groups->slug . '/' . $uri . '/' .
$bp->wire->slug . '/delete/' . $wire_posts_template->wire_post->id ),
'bp_wire_delete_link' ) . '">[' . __('Delete', 'buddypress') . ']</a>' );Your install still says ‘wire’ in the delete url instead of ‘pinnwand’. Looks like the patch wasn’t fully installed? This is on: http://sven-lehnert.de/
Change line 368 to be $bp->wire->slug instead of $bp->{$bp->current_component}->slug and it’ll work. See the difference in the two lines here: https://trac.buddypress.org/attachment/ticket/723/wire_patch_three.patch
Hey, I’ll go test it again with a fresh install. My dev install does what it thinks I want it to do sometimes. It’s eager to please. It wants to be a production install.
In reply to: This is why you are building a BuddyPress websiteHere’s another reason:
http://www.baekdal.com/articles/Management/market-of-information/
Delete wire post where? I tested that too. We’ve got:
1) Profile wire on the member profile home page
2) Profile wire in Me > Wire
3) Group wire on the group home page
4) Group wire in Group > Wire
They are all working for me with:
bp 1.0 trunk (1.0 should be fine too)
default bp member theme
BP_GROUPS_SLUG, BP_MEMBERS_SLUG, BP_WIRE_SLUG changed
wire_patch_three.patch
Where isn’t it working?
OK. See: https://trac.buddypress.org/ticket/723 with the latest workaround with your problem fixed also. ‘wire_patch_three.patch’
Howdy. Hmmm. I know it works with changes to the group and members slugs. I never looked at changing the wire slug itself. Going to go poke around.
