[@hnla Participant 16 years, 3 months ago]

If you narrow your browser you will see the issue, links set out this way only work in fixed width layouts or at least where the min overall layout width is greater than the links, At min layout width and max width as set the links haven’t enough room, start adding plugins that add links to the main set and the problem gets worse, this adjustment allows a bit of room to breath.

[@hnla Participant 16 years, 3 months ago]

Last few things just to stop the main links from wrapping and bunching up.

Add these lines:

#header h1 {bottom:30px;}
ul#nav {max-width:80%;}

Although to be honest width is probably better as IE6 doesn’t understand min-* property

[@hnla Participant 16 years, 3 months ago]

That’s better one thing though: At the moment copying and pasting from this site doesn’t work as characters are being converted, where I set out a series of em dashes it translated those to hyphens I think or vis versa manually edit the comment I made and replace that long line with your own dashes or remove altogether.

[@hnla Participant 16 years, 3 months ago]

are made within the new folder by copying the default files and altering them?

Yes and no. You can approach things in a few ways – first, and as I’ve seen that you have done, is to inherit the original files then you could add further styles after the @import statements as I’ve shown one post above.

you can copy ALL _inc/css/*.css files to your theme and edit them directly then your @import path would be simply (_inc/css/default.css)

This does mean that if the BP default theme is updated and changes made to the themes CSS your theme will not get them.

Lastly use nufink and do it all oneself big job, long time!

[@hnla Participant 16 years, 3 months ago]

Try this which should work:

/*
Theme Name: TSS
Theme URI: http://www.thescratchingshed.com/themes/tss/
Description: TSS custom
Version: 1.0
Author: TSS
Author URI: http://www.thescratchingshed.com/
Template: bp-default
Tags: buddypress, two-column, blue, white
*/

/* Inherit the default theme styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );

/* Inherit the default theme adminbar styles */
@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );

/* Begin custom styles

---

*/
/* change primary sidebar width to 300px */
div#content .padder {margin-right:300px;}
div#sidebar {width:300px;margin-left:-301px;}

[@hnla Participant 16 years, 3 months ago]

BTW there was a typo which wouldn’t have helped matters in my original post where I described an ‘ID’ it should have been a ‘class’; my bad!

Should read:

div#content .padder {margin-right:300px;}

[@hnla Participant 16 years, 3 months ago]

That doesn’t sound correct, if you follow the instructions given on the child theme codex page then you will have a stylesheet that references the original default.css you do not want to create a duplicate of it, you make your changes in the new child theme stylesheet, that’s the one that calls default.css with a line that should look like this:

@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );

[@hnla Participant 16 years, 3 months ago]

Is that ‘Line 4’ custom? I don’t see it in a functions file for a 1.2.5.2 I’ve just test upgraded.

Generally – and it’s not advise necessarily to follow – I have never had an issue with upgrading the WP portion of a site and don’t tend to bother deactivating any plugins; I do though take a backup, ALLWAYS, on production sites prior to proceeding.

[@hnla Participant 16 years, 3 months ago]

If you are making changes to styling you do NOT have to reinstall BP from scratch, it’s simply not necessary.

You should be making changes to a child theme; are you using a child theme? If not follow these instructions here:
https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

If you are making the changes I described earlier then you enter them in the newly created stylesheet file and they act as an override to the default styles that are pulled in to this stylesheet file.

If you follow this procedure you change nothing about the default styling that can’t be reversed by either simply deleting your new ruleset styles from the child stylesheet file or wrapping them in comments to kill them:
/* #content {these styles cease to be read} */

Give things another go but this time if it doesn’t work don’t reverse things leave it up live if you can and I’ll look and see where you have gone wrong.

[@hnla Participant 16 years, 3 months ago]

If the actual snippet of code was parsed / rendered then it sounds as though you didn’t surround the code in the required PHP tags i.e:

<?php
remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_login_menu’, 2);
?>

You do not really need to use a plugin and that suggeststhat it removes the entire adminbar? is that what you want?

[@hnla Participant 16 years, 3 months ago]

When you refer to a child theme it refers to the ability to create a new blank folder within the ‘theme’ folder this would be considered a ‘Child theme’ if it simply had a stylesheet residing in it’s root /top level that stated it was using the files from a particular parent theme, what then happens is having selected this theme – which now would appear in your dashboard themes page, – WP examines the stylesheet information at the top of the file and finds that it instructs WP to look for files in a particular theme as being the main theme files to use; however the clever trick is that WP first knows that it must look in your child theme for necessary files FIRST! and if they are not found THEN look for the necessary file in the stated parent theme, thus you do not have to have any files in your child theme as WP will use the parent files, but you can add new CSS rulesets to the stylesheet living in the child theme and these will be read and acted on (that stylesheet references the parent CSS stylesheet files through the @import rule first and then reads on for any additional rules you have added below the @import calls)

If you do not want to make any changes to BP-Default theme then you simply activate that theme as seen in the theme page in the dashboard. When members create a blog then those blogs should use the twentyten theme or whatever other themes you choose to download and make available (Note that you decide what themes are available to members via the ‘Super Admin >Themes’ page only the themes that you select ‘yes’ to are available to member blogs so to avoid them attempting to use the BP-Default on user blogs you ensure BP themes are not selected)

If you decide that you do need to make changes to BP-Default theme then you would create a folder under ‘Themes’ name it ? ‘my-bp-default’
to the folder you add the requisite stylesheet and now you can move files as required from bp-Default original folder to your new folder and edit them as you wish, or simply create new rulesets to style elements which you place in the new stylesheet file. BP/WP now looks at your new child theme for any files that it must use in preference to the same versions that might reside in the original theme folder.

Apologies if the above covers ground you already understand.

[@hnla Participant 16 years, 3 months ago]

It is assumed? is it :puzzled: actually it’s just irritating No reason for it not to be on the adminbar, I have placed a series of dashboard links as users are not going to be interested in having to type the url all the time. Adminbar is in need of a overhaul!

[@hnla Participant 16 years, 3 months ago]

Find :
div#content #padder – increase margin-right to 300px

#sidebar change width to 300px and margin-left to -301px

However it looks as though you are using the default theme and changes like this should be made to a child theme in as much as you create a new theme directory and set up a new stylesheet that calls the default.css and other files but allows you to add override styles into this new styles.css.

Edit/ just noticed that your are actively editing / changing your theme layout so my earlier advice may or may not hold good

[@hnla Participant 16 years, 3 months ago]

Have you followed the thread on the Ning importer, Boones still I believe actively thrashing out the workings of this plugin; I seem to recall some mention of splitting the json file or something to get around issues

[@hnla Participant 16 years, 3 months ago]

Allowing users to register and create new blogs is under Super Admin > Options

[@hnla Participant 16 years, 3 months ago]

Do you refer to the links in the adminbar at the top of the layout? If so then you can remove them both by adding this line:

remove_action(‘bp_adminbar_menus’, ‘bp_adminbar_login_menu’, 2);

To a ‘bp-custom.php’ file in the plugins directory

[@hnla Participant 16 years, 3 months ago]

Your site definitely does not look as though it’s set up correctly, ‘blogs’ should list all your member blogs not direct to a 2010 undefined blog.

I would suspect that .htaccess is not setup correctly and /or the necessary wp-config changes required for MS added. When you set up the MS network did you follow all the steps exactly and add the new lines shown to you for .htaccess and wp-config? I have messed around with a WP 3.0 subfolder install but cannot replicate what you are describing or that I saw occurring on your site, however removing the .htaccess files does mean that subfolder sites resolve to main site index so I suspect this is the issue.

In case plugins are playing a part in the issue, it might be best to disable/deactivate all but those absolutely necessary i.e BP then see if things change, if they remain the same , compare your .htaccess file to that which should be shown under tools > network in the main dashboard.

[@hnla Participant 16 years, 3 months ago]

Not sure about that one, have a vaugish idea but it’s probably better asked of @r-a-y or @djpaul or one of the others

[@hnla Participant 16 years, 3 months ago]

Odd, definitely made one, perhaps didn’t save ??!!

[@hnla Participant 16 years, 3 months ago]

Well a background image is a styling issue rather than what I showed earlier.

One approach you coulfd take is to open up /groups/single/home.php find the #item-header div ~ line 9
<div id=”item-header”>

change it to this:

<div id="item-header" class="”>

That will now output the group name/slug as a class token for all the groups item-headers.

You can now add a rule set to style a specific background based on this unique class – something like:

#item-header.my-group-slug {background: url(../images/jpg.jpg) no-repeat 0 0;}

if you want the background on a nested element then just add to the selector group the child elements:

#item-header.my-group-slug #item-header-content {}

Not sure about the blank tab requirement I’m afraid.

[@hnla Participant 16 years, 3 months ago]

Not sure the extent of the customisations that you want to do but you could try this approach:

Using:
<?php if(bp_is_groups_component() && ‘my-group-name’ == bp_current_item()): ?>

to wrap sections of the single groups views e.g I’ve used this to wrap the group-header.php #item-header-avatar and #item-header-content to allow for custom markup followed by an :else to render the normal markup. You could use this principle on various sections of a group view?

N.B. If copying code directly check the quote marks are correct and not copied as back ticks.

[@hnla Participant 16 years, 3 months ago]

@djpaul
Paul I locked this thread as it was a duplicate as I made note of. I responded to the other here:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/setting-up-access-to-admin-correctly-for-a-bp-network-site/

[@hnla Participant 16 years, 3 months ago]

What, if any, plugins are you using? what versions of WP & BP are you running.

When you say user of ‘Main’ site what exactly do you mean, all members are subscribers to the main blog that runs BP. When you say that they can ‘see your admin’ how are you establishing that fact; if for instance you, logged in as ‘Super Admin’, go and visit the backend/dashboard of a user blog from the ‘Sites’ list you will see the Super Admin menu, but not if you log in as the real user. If behavior is different than this it sounds like you have plugins or customisations at work?

[@hnla Participant 16 years, 3 months ago]

Great stuff, the validator will help to identify problems, but don’t get frustrated trying to correct all errors or warnings it may report; to some extent due to the nature of third party plugins and WP you will find errors introduced that simply prove too awkward to fix without going into the core plugin files to fix things, mostly these will be minor errors that browsers will attempt to correct. There are a few bad ones I’ve seen recently though such as style tags being incorrectly added into the document ‘body’ element when the tag can only ever exists in the ‘head’ at least though you will be warned of the issue and can choose to track down and correct or live with if not causing total layout failure.

[@hnla Participant 16 years, 3 months ago]

It’s not a plugin If you have the latest WP V 3.0 then you can enable it as Multi Site and let users create blogs. head over to the WP codex for a guide on getting this done.