BuddyPress.org

Most probably the code you are using is trying to access logged in user’s data before init action. Since the current user is set on ‘set_current_user’ hook’ which is just before init, any function trying to access current user data should be called on or after init action.

Hope that helps.

Reference: https://codex.wordpress.org/Plugin_API/Action_Reference

This works:
https://wordpress.org/extend/plugins/remove-dashboard-access-for-non-admins/

Chouf1,

Merci pour ta réponse ! Je suis désolé, je continue en Français mais ça sera plus simple pour moi de comprendre et d’expliquer ma problématique… En fait, tu me conseilles d’installer BP User Profile Map (ce que j’ai fait, je passais avant par une solution codée à la main qui nécessitait une clé pour l’API de GG Maps donc je vais abandonner ça) et de laisser les utilisateurs rentrer eux-même leur pays manuellement lors de l’inscription ou de l’édition de leur profil ?

Cette solution m’a effectivement l’air séduisante mais pour les villes surtout, qui sont effectivement impossibles à toutes recenser. Penses-tu qu’il soit possible de dire au plugin de prendre en compte deux profile fields au lieu d’un (Ville + Pays) ? De manière à ce qu’il localise encore mieux, et pour éviter les erreurs (il existe des villes qui ont le même nom dans des pays différents).

Pour l’intégration d’une liste de pays dans BuddyPress, j’ai suivi le process décrit ici :
https://buddypress.org/support/topic/how-to-make-a-country-drop-down-list-in-profile-field/#post-147697

J’en suis à l’étape de copier coller une liste des pays du monde dans mon fichier CSV extrait de ma BDD, mais je bloque sur les ID par pays : dois-je les étendre simplement sous Excel ? J’ai peur en faisant ça de me retrouver avec un ID de pays identique à un ID d’autre chose de mon WordPress (ID de post, ID de catégorie ou autre)… ça serait problématique ?

Merci pour ton aide et désolé pour l’emploi du Français.

What theme are you using?

What version of BuddyPress?

See if this is your case: https://buddypress.trac.wordpress.org/ticket/4834

It is a known issue and some of the temporary possible solutions are mentioned on the ticket here.

Please have a look
https://buddypress.trac.wordpress.org/ticket/4252

Ok this isn’t perfect but it should work.

Go to ‘Appearance’ > ‘Editor’

On the right hand side select ‘style.css’

Scroll down to the bottom and right after the last }

paste this:

`
div#register-page.page {
height: 600px;
}
`

A better way would be to create a child theme (https://codex.wordpress.org/Child_Themes) and then paste this into the style.css of the child theme. This is because whenever you change your theme you will need to add this again for it to work.

My point was that as long as you have all the correct files backed up there is really very little risk.

I don’t see any particular reason that you would have any problems.

Regarding the update notice. That is strange. Do you get update notices on other plugins and WordPress?

Btw, is there any reason that you are not just upgrading to WordPress 3.5.1 and Buddypress 1.6.4? These are the versions that are the best tested and that you are most likely to be able to get specific advice for.

Regarding a manual update. Yes, just deactivate and delete (after backing it up of course!) the Buddypress plugin and then upload the new one and activate it.

I can’t imagine it will be all that bad 🙂

Actually what I meant to say is that a child theme is not required but if your modifying your theme files whether it be the “Responsive WordPress Theme” or some other wordpress theme to work with buddypress then my instructions are correct. @modemlooper your great but it is still best for people to make child themes even with BP 1.7 beta 1. Reason being for example is when they update their particular theme from wordpress or they made a lot of changes in the child themes style.css, header.php, or footer.php etc. In any other instance then I am correct. my case it was a plain Jaine wordpress responsive child theme and it work perfectly! We can’t discount the value of a child theme for update reasons so we need to get clear on this! Maybe I suppose with the compatibility layer it is now a wordpress.org issue but people do need to be aware of it when installing buddypress because its a little different now but its not rocket science either!

Hi @hsutliff

To take care of the second, there’s a plugin we’ve built aplugin, BuddyPress Media. Do check it out. It’ll sort out the uploading and sharing of media.

Regards.

Hi@evo252,

in the BP 1.0 branch there was a CSV based country field in xprofile.
https://buddypress.trac.wordpress.org/browser/branches?order=name#1.0/bp-xprofile/prebuilt-fields

Take a look in the code and see if you can build something for 1.6.4 or 1.7.

Since 2008, Google Map became a must have. And IMO it’s a better geoloc tool as a simple city/country dropdown witch only prevent end users from having to write themselves the name of their city and their country….
Doing this is much more complicated as you think. Over 160 countries on earth and millions of cities. What kind of server do you need to just store these informations and to make them work together ?

Typing country and city is the same effort as typing name and first name for the end user. Let them write and use something powerfull, existent and easy to use and show AND effort less for you too.

Spare your time and made it simple so far ! 😉
Give this plugin a try: https://wordpress.org/extend/plugins/bp-user-profile-map/

Or search another map plugin : https://wordpress.org/extend/plugins/search.php?q=map

@modemlooper its not required for the buddypress side of things but it is for the wordpress theme updates side of things unless you wanna loose the changes you may have made to the header.php, footer.php, functions.php, style.css etc.

@modemlooper But what if you have a wordpress theme like The Responsive Theme for instance and you want to make drastic changes to it. Wouldn’t it still be a better idea to make child theme? When I say child theme I mean just basically making a child theme for a wordpress theme not a buddypress theme.

As long as you make a child theme of the theme you are using with BP 1.7 beta 1 then the style.css and functions.php should still be fine when 1.7 is out. Since 1.7 has the compatibility layer building a child theme for a regular wordpress theme is all you need to do but if your going to modify any of the buddypress templates you will need to copy over
yoursite/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress into the root of your child themes folder.

I don’t see why you would have any problems.

The themes are made to work first with WordPress, then with Buddypress.

If you are worried just set up a test site and check them out on a site with WordPress and no Buddypress installed.

I hope this helps.

Hi, that is just what I (and think a lot of us) need. Nothing yet about the widget code?

P.S: In this moment I’m using BuddyBar widget (https://wordpress.org/extend/plugins/buddybar-widget/) plugin is not as good as @naijaping code but do its job. A god thing about this plugin is than give You a Log in form and after log in, it changes to something like @naijaping widget.

If you’ve found a bug in the code, please report it to https://buddypress.trac.wordpress.org.

Looks like it is achievable but not without its headaches and a considerable effort.

Found this article relating to what you ask, ‘I think’ …

http://alextheafrican.wordpress.com/2012/03/10/how-to-add-an-image-field-to-buddypress-extended-profile-fields/

Though I can not say how, secure/suitable it will be to current Buddypress versions, perhaps ask the guy who wrote it, if it is still a valid solution.

From a recent post by Boone this duplicate content may be related then to 1.7’s aggressive loading of styles, and scripts theme authors are going to need to add:

add_theme_support(‘buddypress’)

to their themes functions file, preferably hooked to ‘after_theme_setup’

but this will depend on how this theme has been configured to work with BP if at all?

http://bpdevel.wordpress.com/