Forum Replies Created
-
I wanted to take a quick moment and let everyone know our issue has been resolved. What seems to have gone awry was a suPHP configuration that was correctly allowing WordPress side uploads go through with permission 644, but not Buddypress. We run a VPS, so I had the provider’s technicians reconfigure the suPHP settings to allow both WordPress and Buddypress uploads to automatically be set to permission level 644. As of now, things seem to be running smoothly.
So if you’re running a VPS or anything else where you can control the suPHP and PHP settings, be sure to give them a look and ensure they’re behaving as if they were running a shared hosting setup. By default, they are not as open as WordPress and Buddypress need to operate correctly.
Hi Mercime–I just gave your suggestion a go and with only WordPress and Buddypress running with the bundled Buddypress default theme, the avatar upload error still occurred… Do you happen to know if there is any server-side configuration that needs to be in place for the avatar uploads in specific? I’ve also asked our web hosting company to look into the error as well to see if they could see anything on the server side… It’s quite peculiar, because all the other media upload areas work just fine…
Hey Paul–I just now noticed also that the image that gets uploaded is always incorrectly cropped as well. It seems to be automatically cropping to the bottom right section of all photos (large and small)… Very strange as it was not doing this for months before! Is anyone out there experiencing these same troubles with the avatar uploads? I’ve been experimenting with all the other ways to upload images (through the media uploader, from within posts, as well as using the BP Album+ plugin) and all of them work perfectly. It’s seemingly isolated to the buddypress avatar uploads. Thanks in advance for any advice anyone could give me!
Interestingly enough, WordPress-side media uploads work just fine. Correct permission is assigned with those uploads, and also with BP Album+ (both come through at 644). It seems to be isolated to the avatar uploads in Buddypress only. The avatar uploads, but comes through at permission level 600. The file owner and group are the same as all of the other files uploaded as well, so it’s not a file ownership issue that I can see…
Hey Everyone,
I wanted to give everyone an update as to the troubles I was experiencing and how they were resolved.
First–the email problem seems to have been fixed with the SMTP plugin. Thanks again mercime!
The Parse error and warning message we were receiving have been rectified by a server-side fix. We run a VPS with Lunarpages and come to find out a component called suPHP was not installed (suPHP is apparently what shared servers run, and seems to be pretty important in ensuring the basic functionality in WordPress and Buddypress actually works by allowing web users to write to the directories without changing the directory permissions to the dreaded, unsecure 777). By installing and setting up suPHP in addition to running PHP 5.2.11, the parse errors, warnings, and image uploading permission problems have been fixed, as well our WordPress-writable file/directory permissions are functioning perfectly at 755 and more sensitive file permissions are at 644.
So overall, most of the fix was rooted in our VPS not running suPHP and needing to get it installed and configured correctly.
I hope this helps someone else out there experiencing the same problems as we were!
Hi mercime–thanks for your advice! The SMTP plugin works great for the forms.
We are still experiencing the parse error and the warning messages though. I uploaded all fresh files for both WP and BP and the same errors are still coming up when someone tries to sign up for our site. We’re running php 5.2.11, I double checked the syntax of <?php and there's no space in there, and I reviewed the referenced lines of code in the error messages and cannot find any back slashes or missing pieces…
I did also notice that our ability to upload images to our media folder is no longer working as well… Has anyone else experienced these sort of “bundled” errors with the new WP updates?
I saw another user was experiencing the same parse error as we were, and made a manual change to the functions.php file–but I’m incredibly hesitant to touch that as the install was working perfectly before the recent updates/move to new web host. Plus, for our setup, alteration of the functions.php file is overkill and shouldn’t really be needed (from what I can tell).
OH–for reference, we’re running a VPS with Lunarpages. Anyone out there have any potential advice for us?
Thanks again!