BuddyPress.org

@pcwriter “It does everything you want a dropdown menu to do, and it does it all automatically behind the scenes.”

That’s what my problem is though, it does too much and all behind the scenes. From a design stand point, when I’m trying to figure out programs like wordpress or buddypress I try to break everything down to its most basic state so I can completely control things, so I can make a website function around an attractive user friendly design instead of limiting my design to the functionality I am stuck with because I can’t figure out what is going on hidden behind the scenes. It would be great if there was a buddypress codex with individual lines to generate single links to each page.

@rickkumar

Yup, I’m there… and here: https://codex.wordpress.org/Writing_a_Plugin

@Jens Wedin @alanchrishughes

I was looking for a way to include all navigation links in one navbar. Jens’ code snippet is brilliantly simple. Thanks!
The only drawback is you have to add links manually to get them to appear in the adminbar.

I’ve modified the code (borrowing inspiration from a snippet previously written by @David Lewis) so that:
1 – all “standard” BP Directory links appear automatically in their own dropdown;
2 – all BP plugin directories (Links, Gallery, etc) are automatically added to that dropdown;
3 – all WP pages are added automatically to the adminbar;
4 – all added WP pages respect whatever page order is set in the WP-Dashboard.

The code is here: http://pastebin.com/8FJmcgRF

To ensure that unwanted pages DON’T show up in the adminbar navigation (password-protected, Thank You pages, etc), install the Exclude Pages plugin:
https://wordpress.org/extend/plugins/exclude-pages/

as the follow is not entirely inclusive, i have posted it with a password p=events

http://www.countingrows.com/event-calendar-for-wordpress-with-gravity-forms/

This topic answered in this bp.org thread and wp.org forums

@ri-kun – answering you in wp.org forums – WP 3.0 multisite must be enabled

Very often with errors in either scripting or markup the reported point of error is not necessarily where the actual problem starts from it’s just where the validation finally fails to be able to parse the logic.

You are saying ‘IF’ something then do something and we are waiting for that to be finished, however you are only showing a snippet of code out of context which does mean one can only base things on what is shown.

looks like you have lifted the code that is used for the ‘if no widgets run the add widgets error markup’ that is really used more for distributed themes, the ! ‘not’ operator is useful for saying if these functions don’t exist and can’t be called then fallback to this following markup/script. Your code as written needs endif;

You can write the dynamic sidebar call in a more straightforward manner?

if ( function_exists(‘dynamic_sidebar’) )
dynamic_sidebar(“Profile Groups Area”) ;

The WP codex page gives more info:
https://codex.wordpress.org/Function_Reference/dynamic_sidebar

Howdy,

I find the same issue – almost a full screen of deprecated function notices and the like, my site is entirely unusable. Of course, as you point out, one can disable the debug function – but since I am developing sites and plugins, I find the debug to be extremely valuable…

Any roadmap on when those errors might be cleaned out? Any way a guy can help?

Thanks

https://wordpress.org/extend/plugins/login-lockdown/

The key thing that hnla refers to is the user login name. Google tells you instantly how to change this in the database, for example http://www.goldfries.com/websites-blogging/wordpress-change-admin-login-name/. Note if you are running WordPress MS then there will be another field you need to update.