[@hnla Participant 15 years, 8 months ago]

A one column template page has been added to the default theme files for 1.3.

[@hnla Participant 15 years, 9 months ago]

But that’s the point about Diaspora, Diaspora is less about an actual social networking site such as might be created with BP and more about demonstrating the proof of concept that is ‘Decentralised Social Networking’, it and others are trying to find a way through to the goal of not having YOUR data ‘Owned’ by anyone but yourself. BP did much to counter the issue many had with the likes of Ning ‘Owning’ your data, but from the users point of view you are still locked into ONE site and there’s the other issue of countless accounts, logins etc with their data strewn around disparate sites, and would like to simply create one account that holds your social profile and you allow sites to access that as you wish.

There is a – apparently – small? but rising dissatisfaction with the likes of Farcebook, I don’t think Diaspora is setting out to compete with Farcebook but simply prove that decentralising is possible.

Talking of all this what ever happened to SocialRiver? trumpeted and heralded by WPMU blog as the next greatest thing , supposedly with support for BP, has that simply died? Judging by their blog it feels like it, however there has been a post recently, first since July , saying close to beta release!.

[@hnla Participant 15 years, 9 months ago]

Theres a difference between adding to an established theme, and creating a standalone theme which is what it sounds like wooThemes is referring to and yes they’d be right, BP has yet to tackle this area of theming.

N.B your link is borked!

Fixed ‘http://’ is required for for external links

[@hnla Participant 15 years, 9 months ago]

No it’s far more likely to get lost here actually If posted as a ticket on trac it has to be reviewed by a core developer and they are the only ones that can apply patches or at least commit patches – if people have the skills they are at liberty to fix the issue and supply a patch with their ticket and that will be reviewed by a core dev and committed if tested to work.

But yes to a degree it may be read here by someone that might have a clue as to the cause and they might have a look at it, but the ticket ensures it won’t get overlooked.

[@hnla Participant 15 years, 9 months ago]

before everyone just redirects me to the buddypress trac to report the issue, *just read what the problem is*

Ok will do, now can you post it on trac please

[@hnla Participant 15 years, 9 months ago]

If you are talking about the adminbar (very top) then the template plugin references the file from the bp-default theme in the buddypress plugin directory but you can disable that file and code your own styles or place a copy of the file in your themes folder and add an @import call to it in your style.css, then changes will be preserved when you update BP (that can be a good or bad thing depending on the changes)

[@hnla Participant 15 years, 9 months ago]

@Chaotic_Cannon You are forcing mercime to follow and respond to two threads on the same topic while trying to get you to focus on one; note the links posted! Please stop this it’s bad board nettiquette, choose one thread (likely this one given the direction of the questions) and stick to it.

[@hnla Participant 15 years, 9 months ago]

A SC isn’t going to be much use to someone trying to help you with coding issues

You simply have styling issues and need to work through the stylesheets adjusting where necessary you may or probably have still to ensure that the markup in BP files copied to your wp theme match to the WP theme files if you have ‘alignment’ issues.

Above all if you need help with code you will need to let coders have sight of code, a link to the site – if it’s up live – would be best.

[@hnla Participant 15 years, 9 months ago]

Sorry it doesn’t really give me anything to go on, I would suggest trying to get everything back to the original default folders, ensure template pack is correct and that it’s using stylesheets i.e they haven’t been turned off in the dashboard options.

What was suggested before should have worked, that it didn’t suggests other factors involved that I’m not aware of.

If you really want you could go a step further and copy the actual adminbar rulesets and paste them into main style.css at the bottom see if the styles kick in then.

[@hnla Participant 15 years, 9 months ago]

try:
xprofile_get_field_data()

There have been quite a few threads on th subject of xprofile data so also have a little search as I’m not sure what parameters you’ll need to feed through, other than ‘field name’ or it’s ID ‘8’

[@hnla Participant 15 years, 9 months ago]

Simple approach (guess I was overthinking what you were after ) if you don’t want the sidebar whatsoever when viewing an account/profile view would be to remove the sidebar call altogether.

in:
member/single/home.php

comment out the sidebar function thus:
` `

Then you’ll probably need to adjust your styles for that specific page.

[@hnla Participant 15 years, 9 months ago]

Just use a conditional check to see if displayed user == to logged in user, you can see those sorts of conditions at work if you look through profile pages for views that only show for the actual profile user or items that only show if you are logged in, then simply compare the two to see if they match ‘==’ you can then wrap the sidebar call in that conditional check to only show it if that condition is not met ‘!==’

[@hnla Participant 15 years, 9 months ago]

It’s simply a case of understanding the weight of selectors, now you have an id on the ul you should be able to weight the selector set in your favour i,e:

#avatar-block-inline li.item-avatar-online a img {}

if necessary add classes to the a or img elements

changing the class names as I have may well have removed some of the styling that was being applied so you may not have the issue you did, but also may have to style anew as it were.

[@hnla Participant 15 years, 9 months ago]

For starter it’s a list of items, so a good start would be to rewrite the markup using appropriate semantic elements, in this case a ul construct:

`

• <a href="”>

`
Try not to add inline styling, it’s only used by scripting and shouldn’t be used when it can be avoided, style the elements using the id and classes in your stylesheets.

To get a horizontal list either float the list elements or display:inline-block. If floated you’ll need to add clearing to the parent ul i.e overflow:hidden, if using inline-block and you want to center the images add text-align:center to the parent ul.

[@hnla Participant 15 years, 9 months ago]

Path will be wrong ../ is a directory notation that instructs to move one level up to find a file, if both files at same level then simply state the file name

[@hnla Participant 15 years, 9 months ago]

And you have installed the Suffusion BP template pack plugin and gone through that process, checked permalink settings, or at least revisted the permalink page to force a refresh; any other issues with links?

[@hnla Participant 15 years, 9 months ago]

It might be physically there but clearly the path to file is not correct or at least that’s the way it looks, simple test move the file into your child theme and add an @import call to the style.css in child root.

Somewhere those ‘unrelated’ changes must have been related in some way not apparent.

[@hnla Participant 15 years, 9 months ago]

If you can pull up the Apache default page then the machines network config must be correct so the issue can’t lie there can it.

This sounds more as though you haven’t configured vhost containers correctly or simply set the httpd.conf directory to that of your blog home instead of /var/www/html or /home/user/ or however Ubuntu configures things.

If you have written redirects or custom re-write rules then comment them out until you have things working ok. WordPress handles all the rewriting necessary and as long as owner/group perms are set correctly then WP will create the .htaccess and write the rules necessary to it, if not simply copy the provided example ones when you try and set permalinks.

[@hnla Participant 15 years, 9 months ago]

Hmm first thing I would do is deactivate anything BP and simply ensure that your system and WP is correctly able to send emails or that you have configured email dns correctly. Host isn’t Bluehost is it ?

[@hnla Participant 15 years, 9 months ago]

Yep It references the original issue #2293, and I recall the latter ticket now , probably ought to have been addressed at an earlier version though!

So I would suggest for immediate workaround my suggestion of displaying favourite only to logged in user if also displayed user? or wait

[@hnla Participant 15 years, 9 months ago]

One possible fix or workaround might be to remove ‘favourites’ from public screens i.e only display this if logged in user is equal to displayed user.

imho a lot of a members account/profile information is essentially private to them, I do not really need to see another members favourite list.

[@hnla Participant 15 years, 9 months ago]

There have been issues with ‘Hidden Groups’ and leaking of group activity in general to the wider site, I raised a ticket on one major flaw a while back but sounds as though a further ticket might be required.

To get this ‘fixed’ you will need to raise a ticket on the trac system please detailing steps to re-create and versions you are using, this way a core developer will get around to testing this and prioritizing the ticket for attention. You can log in to the trac using your BP credentials.

Edit// Can confirm, marking a topic as ‘favourite’ does display this piece of data to site members who are not members of the hidden group, they can navigate to members profile and check members ‘favourite’ listing, they can also mark that item as a ‘favourite’ for their own listing. In all other respects previous issues appear ok and cannot see the hidden group or it’s data elsewhere nor can I, as non joined member see that ‘favourite’ topic in any further detail. WP 3.* / BP 1.2.6

[@hnla Participant 15 years, 9 months ago]

Plugins extend BP and provide much of the functionality required such as this. Always have a hunt through the plugins list.

This one should suit purpose:

‘buddypress-restrict-group-creation’

[@hnla Participant 15 years, 9 months ago]

Need to be a little more explicit with info please. You added extended xprofile fields, with new group or under the base group? What versions of BP and WP are you running? Are you using a custom theme? If you are can you try deactivating it and using the BP-default theme and verify whether the same problem still manifests.

[@hnla Participant 15 years, 9 months ago]

Just adding it as you posted, it’s more a grimace though!