[@hnla Participant 15 years, 6 months ago]

First attempt sounded like you were worshiping at the high alter of the church of St BP of adminbar

[@hnla Participant 15 years, 6 months ago]

Taken from bp-default 1.3:

`
<?php
/*
* Template Name: One column, no sidebar
*
* A custom page template without sidebar.
*
* @package BuddyPress
* @subpackage BP_Default
* removed since notice hnla
*/

get_header() ?>

<div id="post-” >

<?php the_content( __( '

Read the rest of this page ?

‘, ‘buddypress’ ) ); ?>

‘

‘ . __( ‘Pages: ‘, ‘buddypress’ ), ‘after’ => ‘

‘, ‘next_or_number’ => ‘number’)); ?>
<?php edit_post_link( __( 'Edit this entry.', 'buddypress' ), '

‘, ‘

‘); ?>

`
Not sure if this is practical as it is from 1.3 but the principle is sound. You would need to ensure your custom markup – if any – was replicated in this page and change the top template notice to 1..28 this would then give you a selectable template for when you create any pages that don’t require sidebars. When 1.3 lands live you will also be able to use templates for regular BP pages such as registration as 1.3 uses pages for the main components.

[@hnla Participant 15 years, 6 months ago]

Very very old thread please create new ones rather than drag up threads which should really be read only.

This error is nearly always due to incorrect user/groups the server process doesn’t have access to perform actions on the folder and often it doesn’t matter what folder chmod perms you set also simply settling for 777 (wp-content should be at most 775 ) world writable is not wise or necessary and things really need dealing with on the server user/group level

[@hnla Participant 15 years, 6 months ago]

Yes and no, you would need to change the body class token body.register is particular to the registration page so you would need to do something like:
`
body.page-id-1215 #content,
body.register div#content {
margin-right:0;
padding:0;
width:100%;
}

`
page-id-1215 is the only unique identifier of that page.

However this approach isn’t really the best one, it would be better to be using a onecolumn-page.php template that has the sidebar removed as is provided in the bp-default theme then you would select that page template for you terms&conditions page and when 1.3 hits you would do the same for the registration page.

[@hnla Participant 15 years, 6 months ago]

`body.register div#content {
margin-right:0;
padding:0;
width:100%;
}
`

[@hnla Participant 15 years, 6 months ago]

Couldn’t see why that changeset link was coming up not found. Hard to spot wayward stray ‘full stops’ , hand typing it will get you everytime

[@hnla Participant 15 years, 6 months ago]

https://buddypress.trac.wordpress.org/changeset/3651

[@hnla Participant 15 years, 6 months ago]

shameless promotion

@naijaping you might also grab an old copy of bp-default pre 1.2 where all these arrows stem from you could use that as an example to follow

[@hnla Participant 15 years, 6 months ago]

No it is a background image. Use tools as mentioned (Firebug or Dragonfly for Firefox and Opera respectively if not using IE) to examine the CSS rulesets to understand how it’s achieved

[@hnla Participant 15 years, 6 months ago]

It should have been handled by something like stripslashes when redisplaying. The backslash is an escape character to prevent the ‘ being seen as part of the script syntax and tripping things up or entering characters into the DB that could be mischievous.

You don’t say what versions of things you are running but if latest you might want to enter a bug ticket on the trac system using your BP login credentials.

[@hnla Participant 15 years, 6 months ago]

Yep the feckless Safe Mode has kicked into life, (a feature to be removed in PHP if not in current RC then in soon to be future ones) guessing you are on a system with a control panel like Plesk,Cpanel, or directAdmin?

[@hnla Participant 15 years, 6 months ago]

Something is preventing something loading i.e styles, a vague response as that’s about all one can say really from a couple of SC

[@hnla Participant 15 years, 6 months ago]

Well they’re empty for starters By the looks of it those are dropdown rulesets. The selector sets resemble classic Suckerfish css rules. They’re descendant selectors along the lines of an anchor that has a parent or antecedent li that has a parent or antecedent ul that has a parent or antecedent li etc etc if all matches then apply ruleset – it would be a set of properties for an anchor that is nested at approx 3 levels deep in a dropdown.

[@hnla Participant 15 years, 6 months ago]

There is a conflict somewhere but the trouble with these module/plugin based applications is that there starts to become far too many conflicting styles floating around, CSS is a precise and fiddly language having to do far more complex operations with the DOM than at first is apparent, and the structuring of CSS is very crticle, the more styles that are being applied ( there are 17 stylesheets at work here unheard of or acceptable a few years ago) the harder it is to debug what’s happening.

If I remove the styles that you have applied to custom.css and add back my test example it does work so is suggestive that there is a syntaxical error in the rules somewhere but trying to debug minified styles is not really possible.

Check over that style sheet carefully in it’s unminified state and look for missing ‘;’ or ‘}’ also the habit that minifying has of removing all white space is actually bad practice and shouldn’t be done there should be white space between properties and values and selectors and opening ‘{‘ especially given there were tricky bugs that crashed parsing of styles in earlier browsers.

[@hnla Participant 15 years, 6 months ago]

yeah the patch is knowing how to correctly configure a production server!

The advisory is in error to an extent and in reporting it as such demonstrating a hole in someones skills base?

I always want to see error notices on my development sites, never though on production sites and set it as such.

[@hnla Participant 15 years, 6 months ago]

Closing this year old thread.

Theme announcements may be made in:
https://buddypress.org/community/groups/buddypress-themes/

[@hnla Participant 15 years, 6 months ago]

Closing this thread -newly created group for community theme promotions can be used to promote and group together offerings at:
https://buddypress.org/community/groups/buddypress-themes/

[@hnla Participant 15 years, 6 months ago]

Doh you spoiled the game. Hints were required, hot or cold etc

[@hnla Participant 15 years, 6 months ago]

Thought this would be a fun game so compared two readme from plugins showing as ‘Not tested’ Against my own little effort of little worth that does not show the warning, ruled out nearly every possible cause as one or other of the plugins showing warnings didn’t match on say order of == Installation == sections or omission of sections e.g one missed == changelog ==

As for tested up to I tried to be helpful with BP version number so that probably rules that out. The only common aspect the two plugins have that mine doesn’t that I’m left with is the ‘Donate link’ line? Is that the cause?

[@hnla Participant 15 years, 6 months ago]

You can wrap in something like:
`

‘other menu stuff here’

`
has_nav_menu() looks to see if a menu has been assigned by an admin to a menu region configured by yourself and if so will display it.

Or equally you could use the fallback parameter in the wp_nav_menu array to access a function and place all the older menu stuff in that within functions.php?

[@hnla Participant 15 years, 6 months ago]

What versions are you building for? Personally I would not be building layouts based on earlier versions If you were building from bp trunk then the menu is now changed to use wp_nav_menu with a fallback if the user has not implemented custom menus in the dashboard to using wp_list_pages controlled from bp-default functions.php

If you need or want to use the older style bp header menu then you could wrap the links in an if is wp_nav_menu then display wp_nav_menu else display older BP nav links but I’m not sure there’s a point to that.

[@hnla Participant 15 years, 6 months ago]

Also I would suggest that this is possibly somewhat redundant code? dropdown menus are available either with wp_nav_menu or the fallback wp_list_pages

[@hnla Participant 15 years, 6 months ago]

Insufficient information for a meaningful response

Are you saying that a class selected is not applied to the markup? or simply that there are no rulesets to apply any styling to that class.

[@hnla Participant 15 years, 6 months ago]

for the record I have just done this with your page and it works as expected!

`
/*
WOO CUSTOM STYLESHEET

---

Instructions:

Add your custom styles here instead of style.css so it
is easier to update the theme. Simply copy an existing
style from style.css to this file, and modify it to
your liking.

*/
#activity-stream .activity-content .activity-inner {background: red;}
`
Use this stylesheet they provide for most of your customisations rather than squirting them into the head.

[@hnla Participant 15 years, 6 months ago]

@LPH20005 I would strongly suggest not adding CSS in this manner, it may seem convenient but adding styles in the head of a document is bad practise for anything but the simplest adjustments, adding styles to the head is only used for particular and precise reasons where an external stylesheet is not able to help. Your head section of the page breaks a basic rule of keeping to an absolute essential minimum entries and in fact contains twice or three times as many lines as your actual content and search engines will probably never get to your content to start indexing (may not be a concern though) Head styles are not cached, a particular point of external files is that they are cached as separate objects speeding up page requests.

These frameworks are naughty in encouraging this level of customisation in this manner, with a little more work and advanced coding it ought to be possible to write the changes out to a file.

Try and edit your style file directly adding the rules to the bottom to see if you can effect the change desired, other than that there is too little technical info to go on to puzzle why the style rules are not being applied.