Forum Replies Created
-
All you need to do is post a friendly reminder every 24-36 hours if you do not get any response. A simple “Bump” posting will do.
I’m closing this thread as it is basically a duplicate thread. I’ve answered in the original one here.
In reply to: Sitewide Activity WidgetFirst of all, with the version of BuddyPress trunk that you have installed, you will now only have one activity table in your MySQL database. This table is wp_bp_activity_user_activity_cached.
I know that based on the private message you sent me, you have read this thread which details why this is the case. So, unless you added those tables back to the DB, I am surprised that you even have the other two activity tables in your DB. If the BP upgrade was successful, it should have automatically removed those two tables.
Trying to add those tables and their corresponding data back to the DB will do nothing. The BuddyPress codebase no longer references those other activity tables. They are no longer needed.
As for the Site Wide Activity widget, make sure that you log into WPMU’s backend and go to “Appearances > Widgets” and remove the Site Wide Activity widget and then add it back. Also, your widget will not show any activity until someone does something that gets recorded into the wp_bp_activity_user_activity_cached table.
In reply to: How To Aid Documentation ProjectLike all open source projects, BuddyPress is a community effort. Anyone can add to the documentation–the Codex–by visiting this BP link and creating a new Codex article, or adding to and/or editing an existing one.
Your help in documenting BuddyPress will be appreciated!
Tore, read this and see if that helps.
I would first search the most recent file you modified, making sure that you did not add whitespace before or after the php tags. It appears that that would be new-user.php. If you cannot find the issue in that file, then move on to the the next file you modified, looking for the same issue.
In reply to: When comes the 1.1?I declare this board to be European and shun the American date format! 30/09/09
Paul, exactly what do they call the 30th month of the year in Europe?
In reply to: Removing userbar and optionsbar from Profiles?I’m closing this thread as it deals with the exact same issue you posted several hours earlier. You can read my response in that thread.
https://buddypress.org/forums/topic/member-theme-remove-me-and-my-profile-columns
In reply to: When comes the 1.1?As DJPaul so succinctly states, BP 1.1 will be released when it is finished. The date in the roadmap or timeline in Trac is not written in stone. It most likely will be released some time in September but it could always be pushed out further if more serious bugs are discovered or Andy wants to add additional enhancements.
It is close, though, and if you want to get prepared you should be running a trunk version in your development environment. As always, you are discouraged from running the bleeding-edge version (which is trunk) in a production environment–a live site.
In reply to: group categories with bp-contentsI suggest that you contact Burt Adsit, the creator of that plugin, and ask for his assistance.
In reply to: Member Theme: Remove 'Me' and 'My Profile' Columns?How will your members gain access to their profile data–for editing–or their friends, groups, and messages, etcetera, if you remove the userbar?
I do not recommend this, unless you are planning to provide an alternate way for your members to access this data.
But, what you need to do to remove the “Me” column in the default BuddyPress member theme, is modify the userbar.php in your template file. To remove the “My Profile” column, you basically have to remove the xprofile navigation menu item that xprofile_setup_nav() invokes. The best way to do that is by creating a function in your bp-custom.php file that then invokes a remove_action() for the appropriate do_actions of that function.
Of course, if you remove the “Me” column it will automatically solve your issue of having the “My Profile” column being displayed. You will then have to come up with your own solution to just show the profile data for that given member. It can be done, but what you are asking removes so much access to BuddyPress functionality that I suggest you reconsider.
In reply to: No Profile Fileds after installationAs your issue seems to be with your provider, and not with BuddyPress itself, I’m going to set this thread to resolved.
By the way, if you are using a BuddyPress installing script and not using WPMU’s autoinstaller or simply doing a manual install yourself, you can run into a lot of issues.
In theory you should be able to upgrade from RC1 to 1.0.3 without a problem. What truly matters is the integrity of your database. That being said, when I have not upgraded a WP site for a long time, I prefer to upgrade in several increments.
But if you follow this course, you should be okay (of course, there are no guarantees):
- backup your database–the most crucial step
- deactivate any BuddyPress-specific plugins in WPMU’s back end
- then deactivate BuddyPress itself
- delete the buddypress directory
- download BP version 1.0.3
- follow the instructions in BP’s readme.txt file
- reactivate BP sitewide
Then you will most likely have to change your theme files to get them to work.
If all goes terribly wrong, you can always redownload the old tagged version 1.0-RC1 of BP from here, restore your DB from your backup, and then reinstall and reactivate the old version.
Of course, before deleting your current version of BP, it is probably a good idea to back that up as well. That way, if something goes awry and you need to revert, you know you have the exact same files you used before.
Also, make sure that you have backup copies of your custom theme files as well.
In reply to: No Profile Fileds after installationThat is strange behavior. If BuddyPress installed properly, there should be at least one profile field called “Full Name” located in a field group called “Basic”.
Can you verify that the BuddyPress xprofile tables exist in your database’s backend? Have you checked the PHP and MySQL error logs to see if there is any useful information?
There should be 19 total BuddyPress tables in your MySQL DB–this does not include any WPMU tables. Out of those 19, four of them are for profile data. Each of the profile tables has the word “xprofile” in the table name.
In reply to: Members Directory – Change Friends to ContactsThe “Add Friend” and “Cancel Friendship” buttons (as well as the “Friendship Requested”) are all controlled by bp_add_friend_button() in bp-friends-templatetags.php.
Just be aware that if you modify this code your changes will be lost the next time you upgrade.
In reply to: White Pages whenever Hitting SubmitI switched back to the original BP theme, it seems to work correctly there. Where do I have to start looking then?
Compare the default theme files with your custom theme files. Also, you could be missing code in your functions.php file. Copy the code out of bphome/functions.php and paste it into your themes’ functions.php file.
Another question, if I started to work with the trac files to modifiy the new theme structure from the scratch, do I have to fear more changes until the launch of 1.1 (just to the theme files?)
You should assume that the files in trunk will be modified more. Trunk is the bleeding edge. Changes are being made to those files daily–even the theme files.
Okay, your BuddyPress site is so far out of date that you have a lot of work ahead of you. Since you installed the pre-release version of BP, there have been five major upgrades.
Unfortunately, you upgraded WPMU before upgrading BP. It would have been better for you to get BP up to date before upgrading WPMU, but that is now water under the bridge.
To help you down this road, please read this specific post and all the links it contains:
https://buddypress.org/forums/topic/upgrade-confusion#post-21013
As far as using your custom theme, you will have to look at the default theme files in BuddyPress 1.0.3 and see what needs to be changed. The theme files have gone through many revisions since RC-1 was released five (or more)months ago.
And, just to be proactive, a very-major rewrite of BuddyPress will be coming out in the next several weeks. BuddyPress version 1.1 uses an entirely different theme architecture. You can read about that here.
In reply to: How to Re-InstallYou state in the thread that you link to above:
I had originally installed my wordpressmu under /wordpress-mu/ but then moved it to the root later.
By making that simple directory switch, you’ve basically changed your site URL structure and messed up the DB.
Read this entire WordPress Codex article, paying specific attention to the “Changing the URL directly in the database” section.
Always backup your DB before making any changes–installing new plugins, upgrading, altering code in files, altering data directly in the MySQL tables, etcetera. You never know when some seemingly trivial change might mess up your entire install.
In reply to: "Object doesn't support this property or method"Are there other errors in your server’s log files?
Are you using a custom theme? If so, switch to the default BuddyPress themes and see if the problem goes away.
<buddypress>Do I have to install some jquery thing before using buddypress?</buddypress>
No. BuddyPress does not load the JQuery library but WPMU does. Currently, WPMU uses JQuery version 1.2.6.
Do you have any plugins other than Buddypress activated? If so, try disabling them and see what happens. There could be a JQuery version conflict somewhere.
In reply to: White Pages whenever Hitting SubmitFirst of all, we have very little information with which to provide you assistance. What version of WPMU are you running? What version of BuddyPress?
Please reference this thread an answer the questions.
Finally, the message:
“Are you sure you want to do this?”
often indicates a nonce security failure message. It can happen if you have not updated the BP themes or are using a custom theme (i.e. any theme other than the ones that come with BuddyPress). Try switching to the default BP themes and see if the issue goes away. If it does, then you know it has something to do with the theme you’re using.
Jason, good stuff!
Thanks for your continued contributions.
In reply to: Upgrading WPMU from 2.7.1 to 2.8.4aYep, it’s always important to upgrade your production sites as soon as possible once an update comes out.
The site I was referring to in this post is one of my development sites on my localhost server. So, I don’t have to worry about security breaches as I do not have the site access any outside links. Of course, it also means that sometimes I am lazy and take quite awhile before upgrading it!
You really need to talk with GoDaddy’s technical support. They will help you find and interpret the error logs–and they should be able to help you determine if the mail server is not functioning properly.
In reply to: Upgrading WPMU from 2.7.1 to 2.8.4aSo you recommend going from 2.7.1 to 2.8.3 and then to 2.8.4a?
I do recommend this approach. Although if you–or someone else–goes directly from 2.7.1 to 2.8.4a, I’d like to know the results!
In reply to: give each blog their own buddypress?In reply to: Manually reset user id to higher number?That would be wp_users, but isn’t that ID used as a key (?) elsewhere in the database? Would it get “altered” automatically throughout the system?
No, in WPMU DBs, changing the auto increment field, or any other linked field, does not automatically propagate the changes throughout. The technical term for what you are referring to is referential integrity, with the specific subset of that called cascading changes.
With the MySQL engine, cascading changes (update or delete) throughout the DB only can occur if the tables in the DB have been set up as type InnoDB and the appropriate foreign keys applied. WPMU’s tables are set up as type MyISAM. Before assuming that this was/is a bad choice, when it comes to MySQL, there are pros and cons with each table type. A conscious decision went into selecting MyISAM table types for WPMU’s DB.
Now, with regards to the specific issue you are facing:
Although all the tables in WPMU’s DB have an ID field that is set to auto_increment, the ID field in wp_users is used to assign a unique ID to each registered member of your site. That ID field ties into the other tables in the DB, where necessary, by mapping to an appropriate field–but not to the auto incremented ID field of the other tables.
So, for example, the wp_user ID field forms a relationship in the wp_bp_friends table in two places–with the initiator_user_id and friend_user_id fields. Or as a specific example, wp_user ID field = 7 would form a relationship with the field in wp_bp_xprofile_data where the value of its user_id field equaled 7.
You are on the verge of potentially causing a very big, possibly fatal problem for your MySQL DB. Before doing anything, back up your DB and be prepared for the very-real possibility that you are going to alter the table relationships (break them) to such a point that your DB will not function anymore. You will then have to delete all the data in the DB tables and then restore the data from your backup.
You might even find yourself in the position of having to actually delete the entire DB and creating a new one from scratch. You’ will then need to restore from the back up. So you should also make sure you have a copy of the DB settings in WPMU’s wp-config.php file as you will have to recreate the new DB exactly to match the settings found in that configuration file.
In reply to: Moving to another domain (changing the wpmu domain)https://codex.wordpress.org/Changing_The_Site_URL
But before you do anything, fully back up your WPMU MySQL DB ( https://codex.wordpress.org/Backing_Up_Your_Database )
