Are you using subdomains? bp-groupblog is not responsible for creating ugly subdomains. It mimicks the group name. Most likely you are using sub-domains, which I have not tested the plugin with and you’ve created a group called ‘example’, however you have gone back and forth in the creatrion steps of the group and created a group named ‘example857057604’, since bp will add a random number after group names that already exist. Also the error you get with the cannot modify header information stems from moving back and forth between the steps of the creation proccess, which we are aware off.
Also, you sound a little frustrated, I’d like to point out that all these plugin are released by people volunteering their free time and a lot of it. You can always right your own plugins.
Yes, I am using sub-domains. No, I did not go back and forward.
If the plugin does not work with sub-domains … <i>which, let’s face it, are pretty core to WPMU</i> … then I suggest that it would be good practise to add a block, warning or at least instructions during the setting up process which prohibits the use of the plugin.
There is nothing in the readme either.
‘example’ and ‘example.com’ is just the usual ‘example’ computerspeak not the actual name used.
The header error as above happen on the first and every attempt at blog creation, not going back and forward.
I went forward until the white error page. I could neither go back nor forward. When I came out of the plugin set up, I discovered that it had partly set up the blog on the home page (<i>but that other elements of groupblog did not work of it did not work</i>). It stalls on stage 3.
I also found that previously made groups (<i>made before the groupblog installation</i>), did not have a blog and I could not make a blog for them.
As for the rest, see my perfectly polite and helpful comments … here.
Can I also say, for the future, it would be a really great feature if, when removing the plugin, it removed (or gave the option to remove) all the changes it made to one’s database.
Its a really great idea but perhaps … in all fairness … you should reduce it from a 1.0 + release for just now until it does work?
Consider that these problems might be specific to your setup. I use bp-group blogs with sub-domains and have no problems (and no errors) creating and adding blogs to groups (created before and after install of plugin). The plugin works as advertised for me.
This error has been fixed in 1.2.4. The problem was with the introduction of setting a default groupblog theme in the backend. Now we set the default as wordpress would upon installation, so it doesn’t choke when you do not select an initial theme.
We never came across this error, since we already selected a groupblog theme, once you do that you’ll never be able to reproduce that error. If you do, please tell us step by step how to reproduce and what your ‘saved’ settings are in the groupblog wp-admin section.
@nonegiven did you ever resolve your group-blog issue?
I had the same warning messages after installing some other plugins that were not WPmu compatible.
After Deleting these erroneous plugins, we were able to delete the warning messages at least.
However @MariusOoms we are still having issues with group blog creation that you may be able to assist with.
We installed Only the latest Buddypress and Groupblog Plugins in a test site.
We are able to create Groups just fine,
but are still getting this error in the Group Blog Tab…
Catchable fatal error: Object of class WP_Error could not be converted to string in E:TESTSITEwp-includeswp-db.php on line 488
Any ideas on what we may have overlooked or what we should look into and address to resolve this error.
Please let me know.
Your good assistance is greatly appreciated.
– Jeff –
.
Hi, I’m having enormous difficulty with this plugin. I’m pretty much a newbie to buddypress. I have the default theme installed, and the latest version of BP, and of the BP Groupblog plugin. My host company just added a Wildcard DNS, thinking this would solve the problem which is that, each time I try to create a group blog, I come to the error page “Oops! This link appears to be broken”.
Now, a few hours after the Wildcard DNS was added, I’m still getting the error message, and I still cannot create a group blog for any of my 3 new groups, which have all decided to act very strangely now. I can’t see them listed on the sidebar widget any more. My BP site is only a couple days old, all we’ve done is allow new members to join at Contributor level, and we have a few members who are at Editor level but are instructed not to touch or do anything at all to the site, just join the groups I’ve created.
I am really struggling with this, and I need to get it done before we lose our group on 20th July when Ning starts charging.
Any assistance will be hugely appreciated.
Helene
Have you tried emailing the developer directly?
The only prob im having is creating a blog from groups>example_group>admin>groupblog – if you select a existing blog, all goes fine. When you select to create a new blog I get the following error though it does create the new blog despite the error msg.
Warning: Invalid argument supplied for foreach() in F:Programmesxampphtdocswordpresswp-contentpluginsbp-groupblogbp-groupblog-admin.php on line 23
Warning: Cannot modify header information – headers already sent by (output started at F:Programmesxampphtdocswordpresswp-contentpluginsbp-groupblogbp-groupblog-admin.php:23) in F:Programmesxampphtdocswordpresswp-includespluggable.php on line 890
