Forum Replies Created
Ian @ CloudFlare has dealt with the bug and pushed a new version to the plugin directory, my testing confirms that the error no longer occurs.
Nice, fast response from those guys, very impressive.
Thanks Paul and hnla.
I guess that means they could extend it to BP if they wanted to – they’re probably just not yet ready to work out what they would charge; Ma.tt has stated that the lack of support for MS is largely a billing issue. Hopefully they’ll cover the full gamut soon after they come out of beta and have a better idea of what their actual costs are. VaultPress would certainly be a no-brainer for the owner of any active BP site.
I, too, commented and voted it up.
BuddyPress integration is currently ranked as the 8th most voted for suggestion.
Obviously, more votes will help persuade the Janrain developers that such an integration is worth their time, so, please do comment and vote if you want to see this happen.
HTML emails are a lot more likely to end up in your user’s spam folder, you’d really need some way to be sure that he had added your address to his contacts before you could risk HTML. At the very least, set the first few emails that each users gets (especially any address confirmation emails) as plain text.
Hi Paul, I trust you have fully recovered from Kilkenny by now.
You mention in trac that you’re not getting much technical detail about each install; as it happens, this problem has cropped up on a BP install on my purely-experimental, not-at-all-production, mucking-about server, you would be very welcome to ssh in as root or login to WHM – EasyApache makes it pretty easy to see what is and is not installed.
I also have that new ServerBuddy server analysis plugin installed, lists various settings and permissions in a pleasing enough manner.
The site where this crops up for me is:
… and, just to be clear, it isn’t a problem for me, this install will be getting wiped anyway, I just thought it might be an interesting and accessible example of the problem in the wild.
So, what’s happening is that the image URLs are missing the “wp-content/” part:
Images are appearing in pages as, for instance,
… when, of course, they should be
This is BP 1.2.3 on an MS WP 3.0b1, so, there is no Settings > Miscellaneous to attempt the Full URL path magic trick you suggested above but it is a pretty clean, recently installed CentOS + WHM box, standards settings, it might be useful in figuring out why the paths are getting mangled.
Again, this a purely experimental site and server, I didn’t actually expect to get BP working properly on a beta WP anyway, don’t worry about breaking anything, just let me know if you think it might be useful and want me to send you the passwords.
@Andrea and @JJJ, thanks for the suggestions, I’ll play around with the permissions but I suspect that’s not it, simply because it hasn’t been a problem when uploading the stable version of BP in near identical circumstances. Also, yes, other plugin do appear and can be activated.
Getting an install up and running with trunk would be useful in giving me a headstart on working out how close that version of BP will be to doing what I need, but it is not an absolute necessity.
Actually, at this stage, I probably need to bit the bullet and do a regular SVN install like everyone else – if it turns out that using that route solves the problem, I will post here to tell others who might run into the same problem.
@aekeron – thanks for replying. The test posts I was referring to were actually made on TestBP.org, not my own installation, so, I cannot check the database. Does “hide_sitewide” relate to a setting I can control via my TestBP.org blog’s dashboard?
@nexia – Thanks for responding. I should clarify that the installation is on a remote server, I only mentioned my use of OS X 10.6 in case it was possible that unzipping the files there before uploading them might have caused some sort of weirdness.
@Brajesh – I have several instances of the stable release of buddypress running on the same server, under several different domains, no problems with any of them. The only difference this time is that I am using the buddypress trunk files rather than the stable files.
Thanks for clarifying that the trunk can be installed from the downloaded archive, I suspected that shouldn’t be a problem.
The use of a Mac to initially download the files before uploaded them to my CentOS/WHM server should be immaterial, unless doing so have so sort of affect upon the files as they pass through.
For the use case I have in mind, I am very interested in how blog posts appear in the activity stream.
At around 15:45 GMT, I made a test post on one of my testbp.org blogs:
… but it did not appear in the activity stream on the testbp.org homepage, not even with the stream filtered to “Blog Activity Only”.
I noticed that the most recent blog post appearing in the stream was written 3 days, 19 hours ago – could it be that there is a substantial delay before blog posts appear in the stream?
I also noticed that the blog post has not appeared in my own profile page’s stream either.
It might be the case that, when I set up the blog, there might have been some option I took that renders all of that blog’s posts private, which might be preventing them from appearing in the streams, but I can’t remember doing so and, now, I cannot find any option to make all posts public.
I think Matt mentioned a figure of 10 million users (as opposed to blogs) a few months ago.
Some further details:
OS X 10.6
Google Chrome used to visit http://trac.buddypress.org/browser/trunk and to select the zip file at the bottom of that page.
Archive Utility used to unzip the file.
I placed the BP files in a freshly downloaded local copy of MU 2.8.6, mostly in wp-content/plugins but with the two BP theme folders going into wp-content/themes.
Transmit used to SFTP the whole lot up to my server.
Terminal used to make permission changes.
The above steps have worked every time when using the current version of BP.
This time, however, the MU installation went smoothly but there was no sign of BuddyPress on the plugins page.
I double-checked that all the expected folder and files were in wp-content/plugins. I also copied them into mu-plugins, in case that made a difference … it didn’t.
IS IT THE CASE that the trunk can only be installed via SVN?
If so, why is the zip made available?
I would greatly appreciate any suggestions.
Brajesh, thanks for the suggestion.
Unfortunately, I am logged in as site admin, so, that is not the cause of the problem.
It would be really good to see some sort of integrated video commenting – I believe that, for certain use cases, video commenting could be extremely useful but, so far, it has been hampered by clueless implementations (Seesmic, Viddler) which forced users to jump through registration hoops before they can actually record their message, killing the medium before it even had a chance to catch on.
As far as I can see, Kaltura does not currently offer any sort of video commenting but I think it would be a really could fit with the way in which you are trying to push the communal aspects of video.
I think Mark Jaquith recently said that the WP/MU convergence was expected to be completed by 3.0 or 3.1, so, that would be in either 3 or 6 months time.
Not really so very far away, I think.
Please do let us know how Milan, the developer, responds. GD StarRating is a pretty major plugin, it would be a great pity if it was incompatible with BuddyPress.
@Peterverkooijen – thanks for posting your code
With regard to this thread as a whole, I would like to suggest that the moderators reconsider the practice of marking a feature request thread as resolved on the basis that someone says that they are going to make a plugin.
If we accept that the function of such threads is to make the community of developers aware that that user demand for certain features exists, that function is undermined if it appears that the demand has been met. This thread was marked as resolved three month ago on the basis that Nicola had kindly volunteered to convert Phlux0r’s existing code into a plugin. Like most of us, Nicola overestimated the amount of time he had available and the work was not done. This would not be problem except that marking the request as resolved causes other developers to presume that the request has been resolved.
I would like to suggest that moderators resist the temptation to mark threads as resolved before they have actually been resolved because, although it does give a good impression of progress, it leaves the actual need unaddressed, it leaves the request in limbo. It would be far better to leave it wide open and, even if someone says they have plans to write a plugin, encourage other developers to also apply themselves to the problem.
Alternatively, create another label, possibly something such as “Allocated”, to signal that a plugin is being worked on but, if after a month there is no sign of actual progress, open it up again.
Interesting, I’ve always thought that signing in with an email address is more elegant that usernames – your email address is unique and you are definitely going to remember it, whereas your preferred username may not have been available when you signed up and, now, you have to remember what you chose instead.
How hard would it be to have email-as-username added as an option?
Yes, I believe bbPress is already improving quite rapidly; while it has nowhere near as many features as vB, my instinct is that the combo of BuddyPress + bbPress is actually more useful overall, especially when you consider how the forums are spread out among groups, giving a more intuitive and “lighter” feel.
bbPress 1.0 should be released with the next week or so (it is currently on RC1) and it’s development has been given a boost by the resources Automattic are pouring into their new commercial service, TalkPress.com.
Upcoming bbPress improvements include easier integration with WP and MU, which will be a huge relief. If the massive WordPress community starts to swing behind bbPress, we can expect some pretty good plugins to emerge, whereas I believe vB’s community of voluntary plugin developers has already started to hemorrhage. Certainly, the fact that they are closing all threads mentioning BuddyPress suggests they feel threatened by it.
@nicolagreco, good to hear that this extremely useful plugin is almost ready, please let us know when it is fully cooked
Ah, thanks Andy – I forgot to activate buddyPress-enable, and I didn’t have the very latest version of PHP.
Installing bbPress is, by far, the trickiest part of assembling a BuddyPress site.
Andy, did you get the email I sent you yesterday?
I think I spotted the three “t”s mistake.
Any suggestions on this?
All I need is to be pointed in the right direction.
And here is a thread suggesting there should be a way to report inappropriate content, which could be good functionality to combine in one plugin along with Favorites functionality, as they are both forms of the same thing, tagging items: “Report This” feature