No, really. I *know* BP doesn’t touch or do anything with XMLRPC. If it’s causing a problem, it’s a symptom of something else. e.g. things like load order, or something like that.
Ok, here we go again 
loop.php -> http://pastebin.com/hY4QRvdS
loop-page.php -> http://pastebin.com/3e3KVhuh
loop-single -> http://pastebin.com/awtQMxpZ
I greatly appreciate your help man, and hope this can be solved asap.
Peace xxx
Happy Thursday @mercime! Here are links to the following issues I mentioned in the first post, and I hope they help!
1) http://shenow.org/featured-women/member-directory/members-2/neyloeza23/ – When you put the link in your browser, you’ll see conversations by this member and just under each one is a “View” link. The “view” button is working in chrome, but not in firefox or IE.
2) When a user is mentioned on the activity page, they receive an email with a link to take them directly to the conversation…for example: http://shenow.org/activity/p/2270/ (you do not need to be logged in) The link works in Google Chrome, but it does not work IE or Firefox.
I’m using Firefox 15.0 and IE 9.0 – I know it’s not just me as I’ve had complaints from users about the links not working for them either.
I look forward to seeing what you think/find!! Thanks @mercime
You would *think* BP doesn’t touch XMLRPC at all, but here’s the scenario…
Pre BP 1.6x – works fine. Windows Live Writer connects and works. JetPack can connect.
Post BP 1.6x – With BP activated, Windows Live Writer cannot post to WordPress. You have to disable BP before JetPack will connect correctly – gives error about XMLRPC. So, something that BP is doing when enabled, locks XMLRPC.
I’ve reported this to the JetPack folks and they are checking into it.
Thank you, I suspected that was the case.
BP doesn’t touch XMLRPC *at all*. It’s probably coincidence and will hopefully resolve itself whenever the route issue is fixed.
I have no experience with IIS so unable to help further; at least we proved it’s not the canonical redirects causing trouble.
Gave it a shot, but had no affect. Same issue. If I could get the profiles issue resolved (too many redirects), I can circle back to the others. It’s just strange that Buddypress “locks” the XMLRPC file.
@benzine your page.php has `get_template_part( ‘loop’, ‘page’ )` so do post the code for loop-page.php in pastebin.com as well
Created ticket for the duplicate forum posts issue above https://buddypress.trac.wordpress.org/ticket/4524
SKParticipant
@mercime Thanks a bunch. Looks good on the face of it. Will try.
I’ve gotta say, though, that it is a bit irritating that many BP plugin contributors don’t upload screenshots. By contrast, for WP, I find most plugins do have screenshots.
Oh, well, I guess I can’t complain in that they are giving away their time and effort for free. It’s just that it would be nice if thousands of others didn’t have to put in too much additional time and effort in order to decide whether they want the plugin or not…
SKParticipant
@boonebgorges Thanks for the reply. I hope you will keep this alive, and maybe even merge this into BP core. From my perspective it’s one of the most important plugins for BP.
fyi the buddypress error is that replying to a private message iframes the site in the reply box!!!
I’ve asked my JS guy to look at it, and his reply is:-
“hmmmm sorry no -its some deep bug in the JS of buddypress. Google it? lol.”
@sooskriszta check out https://wordpress.org/extend/plugins/buddypress-media/ by rtcamp; not to be confused with the other BP Media hosted on Google
@sooskriszta The plugin works fine. It’s not abandoned – I need to keep it updated for a client – but I don’t have plans to do the necessary testing for regular release in the near future. The “not ready to be used message” is mainly intended as a “use at your own risk” warning.
@loubas The BuddyPress default theme supports custom menus. Create a menu in Appearance > Menus and name the Home page to Welcome.
SKParticipant
SKParticipant
@boonebgorges Knock, knock!
@mahdiar the culprit was the `display: block;` added in .`button span`
`.button span {
border-radius: 5px 5px 5px 5px;
border-top: 1px solid #FFFFFF;
display: block; // REMOVE THIS LINE
}`
Remove `display: block` and you’re good.
You might also want to change
`div.activity-meta {
margin: 18px 0;
}`
to
`div.activity-meta {
margin: 0 0 18px;
}`
so that the `activity-meta` div is aligned with `activity-header`/avatar
SKParticipant
@modemlooper I am grateful to the BP team. Doesn’t make my request unreasonable.
@rogercoathup Bated breath, etc
== I’m not using a custom theme, I’m using the buddypress template pack ==
@substrato Not clear. What theme are you using? Site URL?
– Only use the BuddyPress Template Pack plugin when you want to make your WP theme compatible with BuddyPress. So if you’re testing/using the BuddyPress Default theme, you do not need to use the BP template pack plugin.
– Creating header-buddypress.php and sidebar-buddypress.php is appropriate for some themes and inappropriate for others, all depends on the HTML structure of the theme.
What custom code are you running? Anything in bp-custom.php if you have one? Or in your theme’s functions.php, or any utility plugins? Have you changed any BuddyPress core files at all?
In wp-admin > Settings > Permalinks, what are your Permalinks set to?
What does the URL of a blog post look like?
Hey mercime, thank you so much for taking the time to have a look at my problem.
Indeed, I completed all the steps prior to installing buddypress but still I’ve got css problems. Though, I manage to solve some of these, this one still persists (I also will have to work on the other broken pages though). So, here we go for the requested pages codes:
1. Header.php -> http://pastebin.com/scmezbUj
2. sidebar.php -> http://pastebin.com/ZyTj63gq
3. page.php -> http://pastebin.com/muiYt3Gy
4. index.php -> http://pastebin.com/h81KkPBM
5. footer.php -> http://pastebin.com/1Mm813G9
Thanks a million for your valuable help. I’m eager to learn how to solve these sort of issues
Thanks for confirming.
I’ve discovered BP 1.6.1 has a problem with topics not appearing in group forum lists when WP is set up to use a persistant object cache. I’m using the APC object cache plugin, and I’m 99% confident it’s occuring on one of our production memcached environments, too. Investigating.
https://buddypress.trac.wordpress.org/ticket/4522
We did add canonical redirections in BP 1.6. I don’t see why this would affect IIS and not, for example, Apache. To see if it was the canonical redirects, put this in your bp-custom.php file:
add_filter( ‘bp_do_redirect_canonical’, ‘__return_false’ );
If you don’t have a bp-custom.php file, see https://codex.buddypress.org/extending-buddypress/bp-custom-php/
