Forum Replies Created
I have noticed this problem too.
A fresh setup …5min WordPress install, add BuddyPress Plugin etc etc…
I can not yet confirm if it only occurs for hotmail users (yuck) and it needs more testing!
But here are some obscured excerpts from my mail logs…
Node1 webserver and BuddyPress:
`Oct 19 13:02:42 node1 postfix/smtp: D67EA2802A: to=, relay=192.168.###.###[192.168.###.###]:25, delay=40, delays=0.33/0.01/0.05/40, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 5967C292C1)`
Relayed to my Mail Server at Node2:
`Oct 19 13:02:43 node2 postfix/smtp: F2173292C4: to=, relay=mx3.hotmail.com[22.214.171.124]:25, delay=0.23, delays=0.01/0.02/0.08/0.12, dsn=2.0.0, status=sent (250 Queued mail for delivery)`
I have a pretty good knowledge of Linux and webservices, but this indicates the mail was sent to hotmail… but the user in question never received it – not even in their spam box.
My servers even have a correct SPF text record in the DNS but so far it seems all the hotmail sign ups are not being seen by the end user.
I can only guess that st00pid Microsoft’s hotmail is sending them into a black hole – perhaps they have got fussy about the confirmation link or something?
Even though it would seem it is not a BuddyPress problem, perhaps some tests should be done to find out why this happens (to be honest, I hate hotmail – but a lot of people use it).
If it is something todo with the confirmation link, then maybe there is some kind of work around?
It will be interesting to hear peoples thoughts on this!
Yes BP is designed to work on $blog_id = 1 but there is no reason you can’t copy the widgets and create your own.
Perhaps in future versions of BuddyPress, you will be able to set where you want BuddyPress to be hosted along with the ability to set widgets as global or single blog.
(we also would like to let our future users use some of the widgets – but are working on a few other bits and pieces atm – I might create a patch when I free up some time)
I have searched the forums to answer this question with no success – but I hope I am not repeating a topic.
I really like everything about BuddyPress and its users – social networking for social people, I think I speak for everybody when I say ‘ask your question anyway and someone will try and answer’
Yeah… only just looked into it myself…
i see a
above the function and
Im not with it today… heavy night last night…
so yeah… subversion merge… )
Create your own theme… or copy and edit the default BuddyPress Theme:
<?php include_once (TEMPLATEPATH . '/userbar.php'); ?>
<!--MY GOOGLE AD STUFF HERE-->
<?php include_once (TEMPLATEPATH . '/optionsbar.php'); ?>
Then just edit the css to format nicely
Although WordPress / MU use its own WP authentication methods, I would state that LDAP will never be a plugin module for BuddyPress.
BuddyPress is a plugin for Social Networking – asking it to deal with authentication is like wanting your office document application to play mp3’s.
Authentication however – within WordPress / MU is pluggable and if there is a plugin out there that supports LDAP, then give it a go as BuddyPress will only check if you are logged in or out and has nothing to do with authentication.
Revision 571 seems to have fixed the problem here too, I am glad that WordPress action hooks go a little further than I realised.
I just seem to have a problem with random blogs throwing a 404 on the main site now… but as its the weekend, not had chance to look any deeper.
Good work Andy
Which ticket is it? can you paste a link?
But – Confirmed.
I had the same problem sending an invite using Revision 570 – the main blog’s admin email address received it but the invited person did not.
I’m not entirely sure on the 1st revision I installed when I discovered BuddyPress, but that seemed to fail sending invites entirely.
I have been doing a little more digging into this problem and the same bug effects:
For instance, you have a post on your main blog called ‘testing BuddyPress’, and someone creates a group called ‘test’ – each time you try to access that group, WordPress will magically use its rewrite rules class and send you to the post entry.
To start with, I thought it may have been a WordPress bug, but no… its WordPress’ default behavior.
It seems that currently BuddyPress is doing its own URL rewriting and then WordPress takes over to convert domain.com/anything/you/like/except/THIS to find ‘THIS‘ as a possible candidate for a place to be.
I have no experience using the correct methods of plugging into the WordPress rewrite rules structure and I am still getting familiar with the ins and outs of BuddyPress – but I hope to keep people posted on my findings.
Firstly, https://codex.wordpress.org/Function_Reference/WP_Rewrite makes it sound simple to utilise the correct and preferred WordPress ways of doing things correctly.
Secondly, If this is the case – it is a good job this has been spotted early because I have a feeling that fixing BuddyPress to use the above would require some core changes.
For anyone interested in the way WordPress looks at its URL’s, paste the following into the <body> of your test theme’s header.php
<?php global $wp_rewrite;
The important part to look at is
[rules] => Arraythat has no mention of blogs, groups or members.
I will continue getting to grips with BuddyPress internals and reporting my findings…
I hope this has helped someone getting closer to fixing!
OK, I have submitted a better patch to allow complete customisation of the admin bar using add_action() WordPress hooks.
It also has log in and register and is available from https://trac.buddypress.org/ticket/174
Please Note, this patch will possibly not work if used on top of the previous patch, so make sure you have the original core files installed first.
I will look into adding a couple of actions for people to hook their plugins into.
I have submitted a patch:
adds Log In and Sign Up (only if enabled registrations)
*adds* …there is also some info there for creating your own custom admin bar.
Thanks for the reply,
I will continue to look into the cause and effect of this strange behavior too, but in the mean time I have renamed my offending post and all is well once more.
I have BuddyPress set up both on locally and a live server so I am able to test/tweak/hack etc
Here are some things I will test to try and replicate this.
- Create a post called Blogs [something] on the main site so the slug reads blogs-[something]
- Create a similar post on a fake users blog with a similar name/slug of that above.
I tried to duplicate this on [myblog].testbp.org but all seemed normal, so I have a feeling it will only happen on the main blog.