Hi guigoz….pages should link to that url, since you are viewing a blog page…not a group page. So the url is correct, however your pagelayout should be identical as the BuddyPress theme. Not sure why you are having trouble with this.
Thanks Lemmy…the fix is in the latest release! I’ll have to take a look at that activity component in case it is turned off. Thanks for pointing that out.
Hmmm…unfortunately I mostly could not replicate many of the errors people encounter. I can only think it has to do with subdomain installs versus subdirectories. As is, I can’t support subdomain installs. If someone can find a fix so that it would work properly I’ll include the fix.
Please try 1.4.5 and see if you find any problems. I have not tested it on a live site, but as far as I can tell it works fine. I would appreciate some extensive testing.
Nope…it is not dead, but definitely on halt as I am involved with other projects as well. Unfortunately my development for BuddyPress runs in sync with the requirements of our local development for our organization. We are anticipating wordpress 3.0 release and content post types. P2 is category based. At the same time we have other issues that take priority, one of them being integrating outside networks such Facebook and External blogs.
I wish it was as easy as being able to develop full time, but it just isn’t the case. The project is still on track, but delayed.
That should give you all possible instances. Just code your slider in your bp-customs.php and use an add_action for your area of choice. Hope this helps.
Yellow notice at top in admin to “activate a BuddyPress compatible theme” remains present, even after child theme activation. Notice disappears when default BuddyPress theme is used.
@Ron R, @webfadds – Just add this to the style.css included in buddymatic, just below the other comments:
You right 21cdb…I do think a dropdown would be helpful at the profile uploading screen to at it to a certain group pool. But yes, within the group it should also be possible to add straight to the pool.
Yes jozik, it would be great to have a “default language” setting in the user profile settings page. Could you not stor a language id in the usermeta of that user? When logging in it would read out the language id and set the redirect accordingly? Just brainstorming here.
How do social network sites like Facebook do this? They have their language selector at the bottom of the page, is that cookie based you think? It is important to us, so we could sponsor this, at least some of it.
I think there must be some additional problems in your install as I’m not able to replicate those errors. I hope for you that when we iron out the WP_Error other things will fall into place as well as it is our only lead with this issue.
The work around for now is as follows, please test this and let me know if that works for you as well. Create the group as usual, but do not create a groupblog. Then visit the group admin and click “Group Blog”. Enable the groupblog and let it create a new blog. Don’t worry about the address we mention (we just show that as information anyway), we just never took subdomains into account, sorry about that. Check your wp-admin and notice the blog is now created successfully as a subdomain blog and the group will work accordingly.
This worked for me, if that works for you I’m pretty sure where it is going wrong and we will fix this in the next release.
Permalinks are also still an issue…if people can share code fixes releases will come quicker, just tight up a bit at the moment. However bugs have major priority and we will try to get it resolved asap.
Sorry for the trouble anointed. I’m pretty sure this only applies to subdomain installs on the group step create blog function.
The work around for now is as follows, please test this and let me know if that works for you as well. Create the group as usual, but do not create a groupblog. Then visit the group admin and click “Group Blog”. Enable the groupblog and let it create a new blog. Don’t worry about the address we mention (we just show that as information anyway), we just never took subdomains into account, sorry about that. Check your wp-admin and notice the blog is now created successfully as a subdomain blog and the group will work accordingly.
This worked for me, if that works for you I’m pretty sure where it is going wrong and we will fix this in the next release.
Permalinks are also still an issue…if people can share code fixes releases will come quicker, just tight up a bit at the moment. However bugs have major priority and we will try to get it resolved asap.
No upgrade path is needed. We don’t use tables and the metakeys we use are still still the same. There is one but hanging around we are still figuring out causing a WP_Error on some groups. I’m a bit busy juggling a few things at the moment so unfortunately development has slowed down a bit.
The current tagged version 1.4.4 is definitely not Beta and should be fine to install on your client site.
If there’s one MAJOR thing all my users struggle with is that WPML doesn’t remember the preferred language for the logged in BuddyPress user. I think that when the user logs in, he/she should be redirected to his preferred language. This should not be browser dependent as far as language sniffing goes, because many communities are filled with internationals living in other countries.
Rather it would be essential for the user to set their preferred language in their bp user settings. This is also better than cookies in case the user logs in from a different computer.
Agree with Andrea_r. Note that the oneclick install forum doesn’t have as much community support as far as plugins go as the standalone bbpress does.
At the end for forums I think nobody beats phpbb. So whatever your focus is as a site/communicty/group go with the best extensible available solution. If forums is your core look at forum software that gives you what you need. I would hold back for investing in a swissarmyknife, but fail at the one thing that is important for your audience.
