Search Results for 'buddypress'
-
Search Results
-
Given that you are delaying the release of BP until site-wide plugins are introduced into MU, it might also be an idea to wait until the WP version is also ready.
Although as anxious as anyone to see the official release, it occurs to me that any project only gets one shot at it’s 1.0 release and all the publicity that attends it. That one-off burst of attention can make all the difference to how much traction you gain in the long-run.
IF BuddyPress jumps into the spotlight as an MU-only project, that’s obviously going to be of great interest to people already familiar with MU but the average blogger is going to scratch his head and not get much further than the fact that BuddyPress isn’t for “normal” WordPress. Disappointed, he will return to his extensive collection of porn and ignore all future mentions of BuddyPress.
If, on the other hand, BuddyPress appears in the spotlight as a dual-release, with both a WP and an MU version, it will garner far more publicity, will be more obviously relevant to ordinary bloggers and will generally create a far larger splash, hopefully translating into greater momentum for the project.
Just a thought
It was a huge deal to get the multi-db plugin to be honest
The only other project out there that has a chance so far would be the HyperDB plugin from Automattic. It gives you the chance to use replication as well as split databases up, but doesn’t come with an automatic blog selection by hash or anything out of the box. I personally am dealing with the huge single database until 2.8 is released.Trent
lol Oh Ren… haha!
@brandtd, this is certainly possible. As a matter of fact, this should happen as default unless you change the width of the body or html elements themselves. This is because the “Buddy Bar” isn’t contained by anything that has a relative position attached to it.
In bp-core/css/admin-bar.css – Try…
#wp-admin-bar {
position: absolute !important;
top: 0 !important;
left: 0 !important;
width: 100% !important;
z-index: 1001 !important;
height: 26px !important;
color: #fff !important;
text-align: left !important;
background:url(../images/admin_bar_back.gif) #818181 repeat-x !important;
}@brian, duh I get what you’re saying now. If I can give some feedback about the Buddy Bar for a moment, I feel that it should be an all or nothing kind of deal. Either it’s always there for people to use, or it’s never there and people have to naturally find their profile area and do things from there. Toggling a whole new set of what are essentially just short-cuts and adjusting the entire layout of the screen, even if by 26px, provides for a moment of awkwardness from a user perspective. For the 3 seconds it takes for someone to think to themselves “Hey what’s that? Do I need it? What does it do? Oh gosh there’s tons of menus now? What is this stuff?”
Now if you’ve used WordPress.com or signed up for a Gravatar before, then the bar idea isn’t new. But for what I consider the core crowd we’re catering to by using BuddyPress as a social networking platform, if it isn’t uniformly worked into the design of the site from the beginning, it only serves to confuse.
Again, this is just my opinion. Not saying it’s right, and certainly not saying that there is a better way. Just saying…
/rant
Back on topic. In theory you could put a…
<body>
<?php if (is_user_logged_in()){ ?>
<div id="buddy-bar-buffer"></div>
<?php }?>In your header file, and attach the CSS to that, rather than to the body itself? That would then only show that buffer when the user is logged in, and once they are logged in, that buffer will push the body down (as styled by the CSS you will give it in your base.css).
Does that make sense?
Unfortunately, vBulletin decided that a vBulletin WPMU bridge was not in their commercial interests and locked the thread, despite 30 of their licensed users expressing an interest. The thread, http://www.vbulletin.org/forum/showthread.php?t=196906, remains readable but not new posts can be made and, therefore, can no longer be used to rally together all the vB users who would like to see it happen.
I swapped a few emails back and forth with vB and they took the time to explain their position. I don’t agree but I guess I can understand their panic; WordPress is one of the few Open Source products that has wiped out commercial products in it’s sector, blogging, and they’re desperately worried that there is no longer that much difference between their $180 product and the free alternatives.
There is, of course, nothing to stop any of you being a bit cheeky and starting your own threads on http://www.vbulletin.org/forum/, innocently asking why there isn’t a vBulletin WPMU bridge
Personally, though, I’ve deciding to transition away from vB – I’ll be keeping my existing vB sites going but, for new projects, I don’t see the point of buying any more vB licenses.
bbPress is pretty bad but I’m optimistic that they will improve over time, especially now that BuddyPress is advancing so quickly. I like the way in which, in BuddyPress, the forums are spread among the groups within the social network – it makes a lot of sense, sort of like wrapping each section of your forum in it’s own homepage, featuring the users who “hang out” in that section.
Awesome, will check it out today.
On an interesting side note, somewhere along the line I broke my connection from BuddyPress to bbPress again. Ha! I need to stop fidgeting with things soon I think.
Well, it could really go in a few different places. Let me take a look when I get to work to see where will work the best.
Here on BuddyPress, the “admin bar” has been nick named the “buddy bar.” It actually replaces the typical “admin bar” from a normal WPMU install.
The files for it can be found in the bp-core directory if you needed to modify it for any reason.
The buddy bar is actually loaded very last in the DOM, and it is absolutely positioned to top 0, so its essentially hovering over the body contents. Because there are at least two active themes at any given moment (home and member) you could either throw the css into homethemedir/css/site-wide.css, or all of the base.css for each theme.
But let me double check for certain.
