BuddyPress.org

More a WP MS question than a BP one can you not use the ‘Recent Site Wide Posts’ widget?

Just a case of checking carefully through the various backend screens, look at super admin > options at the bottom there is a check box to allow administration menus with a single selection for plugins.

You’re pulling in the original one, if you made changes in a copy then they won’t be applied.

path is :
_inc/css/

if you copied the default structure to a child theme.

Are you sure your @import paths are correct, are you actually calling the right adminbar.css? There are only a few rulesets that will govern these dimensions, Firebug is a extension for Firefox that will allow you to observe which rulesets are applied to an element when you hover the element in the viewport.

Then have you adjusted the min/max widths in adminbar.css?

try, rather than using !important, removing/ changing the offending ruleset in default. If you have copied default over to your child theme you are better of removing / adjusting styles in it than overriding. If you drop back to using default theme it will pick up the original styles.

You’re probably being foxed by this naughty little ruleset in default.cssline 60
#wp-admin-bar .padder {
width:90% !important;
}

The new menus have oversights, out of interest do we know what if any changes may be implemented for nav menus in 3.1 if there are it would make sense to add that patch to the mix for testing – given that 1.3 will release after 3.1?

Patch added: https://trac.buddypress.org/ticket/2691

I can try 🙂 haven’t used Tortoise to create patch before. You agree though, on the depth param?

Well logic would dictate to some extent simply replicating the adminbar styling more or less.

the opportunity should be taken though of getting rid of the graphics and replacing them with versions that aren’t 1×1 and if adding hover it should also be matched with :focus

Not sure of the point in posting these comments on this support site really, think you really need to direct these to the authors site, if you’re post has been deleted inquire privately of them as to why

Had intended on looking in detail at new menu arrangement but have had a really problematic time running 1.3 on a clean relatively fresh and mainly unused WP 3.0.1, not sure what the issues are at this moment but not feeling the love for these new page approaches to the main components as they hang […]

no ‘display:none;’ please, left:-999em; / left:0;

What are intending on doing for users having to still use IE6 ?

edit// 🙂 ok scrub that modemlooper has sorted it. I’ll take a look in the morning, the new menus have a draw back at the moment in not doing nested dropdowms so not sure how you’ve forced that behavior, I implemented them in pcwriters plugin using a top level li element as exists for adminbar […]

To go about doing this would require fairly advanced PHP skills and experience with the BP API, it’s not a straightforward task. Not sure if anyone has attempted this, think it’s been discussed or touched upon briefly before Not sure this does make sense though would it not result in possibly a very bloated xprofield […]

If you can’t upload files to BP album that is the same issue as if I’m not mistaken it uses the WP mechanism for uploads, and in fact this suggests a test that ought to be run to see if WP is able to upload files, so with BP deactivated try running the site as […]

You might try re-uploading the 1.2.6 files but via FTP this time and see if that makes a difference -failing that you may need to roll back to 1.2.5.2

It would be more like this:

if (bp_get_profile_field_data(‘field=thefield’) == ‘string’) :

Covered quite often on the support form; standard answer is to rename the plugin via FTP or SSH , this will force deactivate the plugin and should allow you access again. Likely reason for this happening? Too low a PHP script memory limit.