Search Results for 'buddypress'
-
AuthorSearch Results
-
November 2, 2009 at 5:23 am #55674
slicktig1
ParticipantThanks for the replies. Yup, both didn’t work with wpmu minus buddypress. I tried wp contact form which is working. thanks.
November 2, 2009 at 12:15 am #55662In reply to: gravatar.com / only in english language ?
Xevo
ParticipantThat’s because there is nothing we can do to help you on this forum, there is no german version and since Buddypress is not related with Gravatar, we can’t help you further on this forum. Try sending their support an email: support@gravatar.com.
Edit: I know that the world is bigger then my appartment, my girlfriend lives about 50 km from my appartment and I’m planning on going to Japan soon. So keep your bad opinions for yourself next time.
November 1, 2009 at 11:54 pm #55660In reply to: gravatar.com / only in english language ?
Xevo
ParticipantTell them to learn English? I doubt that Gravatar is gonna translate it’s site just because some people don’t wanna learn English..
They do have a french version of the site though..
I tried http://de.gravatar.com/, but that doesnt seem to work.
(They probably made a French version since It’s quite hard to learn English in France.)
Edit: Btw, Gravatar is not related with Buddypress, the only relationship they have is Autommatic.
November 1, 2009 at 11:32 pm #55658In reply to: wp-signup.php is a blank page
PH (porsche)
ParticipantFollow Up Questions:
I’ve left JJJ’s code snipet in.. (Will that conflict with anything?) —
– JJJ’s snippet is located in:
wp-content / plugins / buddypress / bp-core / bp-core-signup.php
– XEVO;s snippet is located in:
/ wp-content / themes / bp-sn-parent / functions.php
I’ve left both snippets in…
Any possible conflicts?
I hate touching “stock installations” at some point im gonna forget what I did, where.
November 1, 2009 at 8:50 pm #55647In reply to: Fatal error after upgrading to BP 1.1.2
ph23man
ParticipantI ran into this exact same error:
Fatal error: Cannot redeclare bp_activity_install() (previously declared in …/wp-content/plugins/buddypress/bp-activity.php:19) in …/wp-content/plugins/buddypress/bp-activity.php on line 52
If you have a failed upgrade, I recommend reverting to a “clean” backup of your files and database from before you upgraded Buddypress or attempted reactivation.
Here’s what I did to successfully upgrade from BP 1.0.3 to 1.1.2:
1. Switch to a non-BP theme, i.e. WordPress mu Homepage 1.6
2. Deactivate ALL plugins (you’d probably be okay by deactivating only BP-dependent plugins but I did this just to be safe)
3. Delete Buddypress plugin files (/wp-content/plugins/buddypress) via wp-admin or FTP, either is fine
4. Download the Buddypress 1.1.2 zip and upload the new files to your plugins folder
5. Activate Buddypress plugin in wp-admin
I can’t comment on what changes you have done to your install or what plugins you’re running but I had similar problems with the upgrade and the steps above allowed me to successfully upgrade BP.
November 1, 2009 at 8:46 pm #55645In reply to: Broken activity
arghagain
ParticipantI hope this post help some of smart people on buddypress.org to help me figure out an easy solution to this problem. http://premium.wpmudev.org/forums/topic/activity-broken-for-buddypress-112-and-wpmu-2852
November 1, 2009 at 8:05 pm #55642In reply to: Fighting Splogs
peterverkooijen
ParticipantChouf1, are you sure wp-login.php is even used in Buddypress registration?
Edit: Tried the code. I get an “Parse error: syntax error, unexpected T_ELSEIF”.
November 1, 2009 at 8:00 pm #55641In reply to: Fighting Splogs
peterverkooijen
Participantr-a-y, I’d like to try the .htaccess solution, but the instructions are very ambiguous:
# BEGIN ANTISPAMBLOG REGISTRATION
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .yourbpsignupslug*
RewriteCond %{HTTP_REFERER} !.*yourhomedomain.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) http://die-spammers.com/ [R=301,L]
# END ANTISPAMBLOG REGISTRATIONShould I leave the dots (.) and stars (*) around ‘register’ and ‘mywebsite.com’?! What would be mybpsignupslug if I have the registration form on my homepage as well as /register?
November 1, 2009 at 7:52 pm #55638John James Jacoby
KeymasterCan you confirm if this plugin works without BuddyPress activated? It might be the more strict MU kses that’s blocking the form.
November 1, 2009 at 7:46 pm #55635In reply to: wp-sigup.php and /register
Lucian Mihailescu
ParticipantHi guys,
Thank you for the fixes posted here. I tried these and it still don’t work for my WPMU.
My site is at:
When I click on Signup it goes to:
http://intercer.net/blogs/wp-login.php?redirect_to=http://intercer.net/blogs/blogs/register
When you click on Register link at the bottom of this page or if I type directly http://intercer.net/blogs/register, it takes you to the same page.
I tried the fixes on this page and the ones indicated in:
https://buddypress.org/forums/topic/wp-signupphp-is-a-blank-page
No luck yet. Not sure what I am missing.
Trusktr — you mentioned to “make sure you copy over the functions in the “functions.php” file from the bp-sn-parent theme to the “functions.php” file in your own theme. Without these functions, some things won’t work like member and blog listings as well as sidebar customization when using the “home.php” template. “
I have these problems too. I put the redirect code in “functions.php” in bp-sn-parent themse (which is the theme that I use). What do you mean when you say to copy the functions into “your own theme”?
Thanks,
Lucian
November 1, 2009 at 7:41 pm #55633In reply to: BuddyPress Spam
peterverkooijen
ParticipantMy spammers all sign up with .info email addresses. Is there any way to just block all .info?
Legitimate members should use normal .com emails, like normal people.
November 1, 2009 at 6:37 pm #55627gazouteast
ParticipantGenuine pause for thought – why does buddypress use a javascript image cropper to bring avatars down to size?
Why not use a simple auto-thumbnailer (there are many as plugins to standalone WP) and use css to control the sizes where they’re needed? Even WP has an autothumbnailer built into the media library – that’s why it creates 3 images on server for each one image you upload (which really bugs me – I KNOW what size I want to upload, I’ve already resized it locally BEFORE upload – quit re-inventing the wheel.)
Beddy-bies time for me, sleep needed, I’m getting way too cranky
Night all
Gaz
November 1, 2009 at 6:23 pm #55625gazouteast
ParticipantHi Jeff – key comment in this reply is the last line

So, if your source image is smaller than 150 on at least one of its dimensions, you could have issues with creating the large avatar. If it is smaller than 50 on at least one of its dimensions, you could have issues with creating the small and large avatar
So what happened to css basics?
e.g.
maximum-width; 150px
note the use of maximum-width as opposed to width – or is that not available in javascript ? (genuine query as I don’t know js coding at all) – also, note the dimensions I gave in reply to Xevo way back up the thread.
it may be that your server is running too old of a version of the GD image library
possible, though highly unlikely with this particular host – I’ll check with them though.
never use the auto-upgrade feature when upgrading WPMU or BuddyPress. It is simple and quick enough to manually upgrade them and it gives you more control and assurance that it is done right.
Side topic response, but – I’m 2,000 miles from the closest of my servers (Singapore) and 8,000 from the main one where the install is running a deadline, and 12,000 from the US hosts that I also use heavily. It is NEVER quick to manually download the package, extract it and upload it from here – assuming the locals can keep the electric on for more than an hour at a time, and the internet connected for two consecutive minutes – that’s why the auto-upgrader was such a godsend when it arrived in 2.5 Having said that, I’ve noticed some very consistent differences on it with UK and US hosts – both the auto upgrader and the plugins/theme direct download to site and upgrades, work flawlessly on US hosts and never ask for FTP login. On UK hosts, they all always ask for FTP user login from wp-admin, and greater than 50% of the time they fail to complete all expected on-screen steps. I’ve also noticed that UK hosts tend to override the timeout preventions built into WP, which US hosts do not do. ….. don’t get me started on the pricing differences either – LOL
Are you on a shared or dedicated server? Talk with your hosting firm to see if there is some javascript-based application that the hosting firm has running on your server that could be interfering with the basic JS operations in WPMU
It’s a shared server, but a reseller account – half way step between shared and VPS as in limited main accounts per server but with dedicated RAM per reseller account and so on.
The background js / mootools question is a good one that I’ll fire at them.
On the UK install, I’ve tried every possible config right down to the barest of bones – even to the point of deleting (not just deactivating) all plugins and themes and dropping all tables created by any plugins – still problems persisted.
It got to the point a couple of hours ago that I finally had enough and made liberal use of the Ctrl+A and Del keys
Pffzzzzzt – zap – gone – empty domain space. I’ll be nuking the database in a minute or two as well, then uploading from scratch and starting again in the morning (1:00am+ here now) after letting the dust in my head settle after spending the whole weekend scouring the WPMU and BP forums trying to resolve this.
I’ll also be starting with a WPMU install that has no periods in its directory and folder names – i.e. NO ” blogs.dir ” style of names – I am convinced that is a major source of some problems related to images, just as I am convinced that the user blog folder tree goes way to deep for Google search bots to follow it all the way to the bottom – and that’s gonna hurt SEO.
As I said up a bit, I’ve nuked the install (and the test installs) and will make a fresh start tomorrow … to mis-quote a famous movie line –
“I love the sight of deletion in the evenings” ~ Major Lee Pistoff, in aPressolypse Now
LOL
Gaz
November 1, 2009 at 5:54 pm #55624In reply to: Existing blog doesn't show up in BuddyPress
Paul Wong-Gibbs
KeymasterNovember 1, 2009 at 5:51 pm #55623Paul Wong-Gibbs
KeymasterNo, I don’t. I haven’t seen these plugins discussed with BuddyPress on this forum before, either.
You probably need to talk with the author to check if they are compatible with WPMU and BuddyPress.
November 1, 2009 at 5:49 pm #55622Paul Wong-Gibbs
KeymasterNo, but it’s been well discussed that WordPress and BuddyPress do a relatively poor job dealing with i18n issues.
November 1, 2009 at 5:48 pm #55621In reply to: Fatal error after upgrading to BP 1.1.2
Paul Wong-Gibbs
KeymasterFunction redeclaration warnings are usually in this case because you have a BuddyPress-specific theme, or a plugin which requires BuddyPress. You need to make sure you have no plugins active that use BuddyPress, or any code in files such as bp-custom.php etc.
November 1, 2009 at 5:35 pm #55619In reply to: Docs on buddypress.org?
Xevo
ParticipantFor wp wiki, you have to use the backend editor, since it’s officialy made for single wordpress. But since you have to/can make a different theme for the blog, you could try making it front-end.
Edit: I found an easy solution for this as well, there’s a front end editor plugin.
https://wordpress.org/extend/plugins/front-end-editor/screenshots/
November 1, 2009 at 5:27 pm #55618In reply to: Docs on buddypress.org?
21cdb
ParticipantDo users have to log into the wordpress backend in order to write a wiki post, or is there kinf of frontend editor?
November 1, 2009 at 5:17 pm #55617In reply to: BuddyPress Multilingual
still giving
ParticipantCongratulations. You should be hired and paid by Automattic right away.
Multi-lingual webapps should be the default.
Let’s work to encourage multi-language social networking.
Looking forward to a 1.1 release.
November 1, 2009 at 4:43 pm #55613In reply to: Existing blog doesn't show up in BuddyPress
still giving
ParticipantYes. Logged in and posted. Posts show, blogs don’t.
November 1, 2009 at 4:25 pm #55611Jeff Sayre
ParticipantOkay, I’ll add a few thoughts and ask a question or two here as well–in no particular order of importance.
- When describing the avatar-uploading behavior in point 2 of your your OP, you state that:
the cropper tool fails to grab the image and displays only a black 88px x 16px background “bar” in the avatar viewer.
That behavior can indicate one or more issues. Here are a couple.
First, it could mean that one of the dimensions of your image file is too small. By default, BuddyPress sets the small avatar at 50 by 50 and the large avatar at 150 by 150. So, if your source image is smaller than 150 on at least one of its dimensions, you could have issues with creating the large avatar. If it is smaller than 50 on at least one of its dimensions, you could have issues with creating the small and large avatar. You will see black for any missing pixels, meaning that the cropper has to add pixels to bring the image size p to the minimum required dimensions
Second, it may be that your server is running too old of a version of the GD image library.
- In your post just above this one, you talk about using the auto-upgrade feature for WPMU. I never use the auto-upgrade feature when upgrading WPMU or BuddyPress. It is simple and quick enough to manually upgrade them and it gives you more control and assurance that it is done right.
- You mentioned that you do not have any additional BuddyPress plugins installed and activated but that you do have a couple of WPMU plugins activated. When trying to figure out issues with your setup, you need to distill your environment down to the lowest, common denominator. That means deactivating all plugins except BuddyPress and using the default BP theme. So, although you only have the Akismet and Default Blog Settings plugins activated, I would suggest deactivating them when trying to figure out what is going wrong.
- Are you on a shared or dedicated server? Talk with your hosting firm to see if there is some javascript-based application that the hosting firm has running on your server that could be interfering with the basic JS operations in WPMU. For instance, a MooTools-based application that has a conflict with the jQuery framework used by WPMU. Although this is a very slight possibility since you’ve indicated this behavior has happened on three different hosts.
November 1, 2009 at 3:13 pm #55609In reply to: Having trouble changing an Avatar with POST method
hadar
ParticipantI just looked at the php error log (which was not generated on the production host) and it has the following error in it:
[01-Nov-2009 10:12:23] PHP Catchable fatal error: Object of class WP_Error could not be converted to string in /var/www/html/wp-content/plugins/buddypress/bp-core/bp-core-avatars.php on line 264
November 1, 2009 at 3:10 pm #55608In reply to: Having trouble changing an Avatar with POST method
hadar
ParticipantI just jumped through a ton of hoops to set up a Virtual Machine running CentOS to install a fresh WPMU and BuddyPress (2.8.5.2 and 1.1.2) behind APACHE this time (instead of NginX) to test the Avatar change, and watch the RewriteLog in Apache to see if I had a logic error in NginX.
Even under Apache2, when I try to upload a new Avatar, it fails with the same 404. Looking at the Apache Rewrite log, I see that the URI gets rewritten as follows:
/{DocumentRoot}/index.php
The parameter is “members/admin/profile/change-avatar/” (but I actually see that the leading “/” was stripped, but the log doesn’t actually show what’s passed). It has to be passed, because index.php alone does bring up the site homepage correctly…
November 1, 2009 at 11:32 am #55600In reply to: Removing default Avatars from Blog Listing View
John James Jacoby
KeymasterYou can create a custom home theme and replace the blog avatars with a default image of your own if you’d like. And choosing the creator is obvious to you, but might not be what someone else wants. The creator of the root blog is the admin account, but I always create a new user right away and use that new user as my active account.
When you first install WordPress and see the default theme, is your first response to say “it’s obvious the sidebar should be on the left side.” The default BuddyPress themes are designed to include all of the functions of BuddyPress to guide everyone into how to customize the use of them to do what you want and look how you want it to, just like the included WordPress themes do.
Sure, people have made ultra elaborate theme frameworks, but don’t expect that to come bundled in the BuddyPress core. You’ve got options if you don’t like what you see, so explore them.
- When describing the avatar-uploading behavior in point 2 of your your OP, you state that:
-
AuthorSearch Results