Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'how to hide pages'

Viewing 25 results - 226 through 250 (of 289 total)
  • Author
    Search Results
  • I’m creating a site using WP & BP and the Twenty Tens theme. The BP Compatibility gave me links to use for activity, members, groups, forums and register, but nothing for profile. I can’t figure out how to create the Profile link. (I also installed plug-ins to bypass WP profile and hide admin/dashboard—but the profile has never worked—for BP or WP. Help?
    http://www.teachertime123.com/

    David Carson
    Participant

    `bp_is_active()` checks if a BP $component is active – not whether members are registered but not activated. The `bp_account_was_activated` function is used in the activate.php template but isn’t appropriate here I don’t think.

    In addition to the BuddyPress Conditional Tags – https://codex.buddypress.org/developer-docs/conditional-template-tags/ – you might also look at WordPress Conditional Tags – https://codex.wordpress.org/Conditional_Tags – to see if there are any that will work for you.

    P.S. I just saw your other post.

    `
    This occurs due to my BuddyPress Auto Group Join plugin. How can I hide the not-yet-activated members from appearing on the Group Members page?
    `

    It seems like it would be better to modify the plugin(s) causing the issue instead of modifying the BP code. Maybe the plugin developers can assist.

    dslax27
    Member
    dslax27
    Member

    Hello,
    I’ve been working all weekend on this one and I just can’t seem to find an answer.

    *//PROBLEM: Users that have registered but have NOT activated their accounts show on the Group Members page (…/[bpressdirectory]/groups/[groupname]/members/). This occurs due to my BuddyPress Auto Group Join plugin (link below). How can I hide the not-yet-activated members from appearing on the Group Members page?

    **Failed attempt #1 (members-loop.php):

    `

      … [BUDDYPRESS CODE]

    `

    **Failed attempt #2 (members-loop.php):
    `

      … [BUDDYPRESS CODE]

    `

    Any idea where I went wrong?

    WordPress 3.0.4
    BuddyPress 1.2.7

    Plugins:
    – S2Member (http://www.primothemes.com/post/product/s2member-membership-plugin-with-paypal/)
    – BuddyPress Auto Group Join (http://twodeuces.com/wordpress-plugins/buddypress-auto-group-join) – This

    Mouchoirs
    Member

    I like the widget you recommended above. I’m wondering if you know anything about pagelines plaform. I was thinking, if it offers full buddypress functionality, I could utilize the registration widget along with the “hide primary bar” feature in pagelines. This would make the widget available on only the pages I desire.

    If I did this, do you know if there’s a way I can make every page of buddypress invisible to non-logged-in users? I could then simply have the registration and log in page visible to non-users. I’m currently using a privacy widget to hide all pages except login from non-logged-in users. However, I don’t see any way to select specific buddypress pages to choose to make private.

    Thanks again so much for your time.

    #100182
    techguy
    Participant

    Modify header.php in your theme. I think it’s wp_list_pages or something like that which lists the pages. Use is_user_logged_in() for the if statement to choose when to display the pages.

    #100163
    Ekine
    Participant

    @modemlooper Sounds great. (:
    Two more questions…
    When updating the theme, how can we maintain custom css changes without editing custom.css after updating?
    Is it possible to show the ad code (sidebar.php) only on certain wordpress pages. Because I would like to hide this ad code on most buddypress related sites.

    One more suggestion, how about adding ajax pagination for latest blog posts and or maybe ^^ make ’em sortable by date, most hits and most comments. (:

    See screenshot: http://i56.tinypic.com/9bazye.png

    #98945

    In reply to: buddypress bar

    pcwriter
    Participant

    @Tekuan_Coleman

    Gotcha! Here’s how…
    1- Enable “Hide Main Theme Nav”, “Add WordPress pages/menus”, “Add Buddypress components” and “Scroll with pages”.
    2 – Go to “Sizes & Position” and adjust the “Overall navbar width” to the width of your template.
    3 – Play around with “Vertical offset” and “Horizontal offset” until you get it positioned about where you want it.
    4 – Save settings.
    5 – Now go to “Appearance” > “Menus” and select the WP3 custom menu you want at “BP-WP-Navbar Menu 1”
    6 – Click “Save” at “Theme locations” and “Save menu”
    7 – Check your site and refresh a page.
    8 – Repeat, lather & rinse until you get it “just right”.
    9 – Have fun! :-)

    #98841
    kaelwithme
    Participant

    yeah, well i’m trying to look for a way. which i can’t find via plugins/admin since you should restrict/hide such navs on the BP page which are different from WP pages in a sense that they kinda don’t exist. they’re generated on the fly.

    do you by any means know what the equivalent of is_home() to the member profile page is?

    Here’s something I would like to share. This edit was done in the header.php file of buddypress to hide the Nav Bar from guests and displays WordPress pages only.

    <html xmlns='http://www.w3.org/1999/xhtml' >
    
    <meta http-equiv='Content-Type' content='; charset=" />
    
    <title></title>
    
    <meta name='generator' content='WordPress " /> <!-- leave this for stats -->
    
    <link rel='stylesheet' href='" type="text/css" media="screen" />
    
    <link rel='alternate' type='application/rss+xml' title=' | " href="" />
    
    <link rel='alternate' type='application/rss+xml' title=' |  | " href="" />
    
    <link rel='alternate' type='application/rss+xml' title=' |  | " href="" />
    
    <link rel='alternate' type='application/rss+xml' title=' " href="" />
    <link rel='alternate' type='application/atom+xml' title=' " href="" />
    
    <link rel='pingback' href="" />
    
    <body  id="bp-default">
    
    <div id="header">
    
    <h1 id="logo"><a href='" title=""></a></h1>
    
    <ul id="nav">
    <li class="selected">
    <a href='" title=""></a></li>
    
    <!-- wp-pages transferred here -->
    
    <!-- edit if else statement -->
    
    <li class="selected">
    <a href='//" title=""></a>
    </li>
    
    <li class="selected">
    <a href='//" title=""></a>
    </li>
    
    <li class="selected">
    <a href='//" title=""></a>
    </li>
    
    <li class="selected">
    <a href='//" title=""></a>
    </li>
    
    <li class="selected">
    <a href='//" title=""></a>
    </li>
    
    <!-- wp-pages edited from here -->
    
    <!-- to here -->
    
    <!-- edit if else statement endif -->
    <?php
    }
    //else
    else :
    {
    echo '<li><a href="http://yoursite.com/wp-login.php">Log In</a></li>';
    }
    endif; ?>
    
    </ul><!-- #nav -->
    
    <div id="search-bar">
    <div class="padder">
    
    <form action='" method="post" id="search-form">
    
    <input type='submit' name='search-submit' id='search-submit' value='" />
    
    </form><!-- #search-form -->
    
    </div><!-- .padder -->
    </div><!-- #search-bar -->
    </div><!-- #header -->
    <div id="container">

    Just replace yoursite.com with the URL of your site 🙂 Cheers!

    #96207
    Miko
    Participant

    I don’t want a landing page for visitors, I want normal visitors to see all of the usual pages & posts on the public part of the site. This is happening fine. What I want is for them to arrive on a nice page if they search for something that is on a hidden private part of the site. I am using Private Buddypress to hide members area (private profiles, forums etc) from the main marketing pages of the site ( WP pages and posts). The Private Buddypress plugin annoyingly redirects to the standard WP login screen (as you can see in the code from that plugin posted in my original Q). I do not like this, because it gives no explanantion to the user why they searched for something and arrived at a login screen. This is why I want to redirect to my custom 404 page, which I have modified to say that the item they are looking for is not found, or it is only visible to logged in members. What I want to know is how EXACTLY to modify the above code to get the redirect to point to the 404 page.

    The login screen is not helpful, and in fact it’s offputting/confusing because you have to be a member of our photo club to be allowed into the community – so we don’t accept public registrations. Showing a login screen makes it seem like people should be able to register somehow, when they can’t.

    #95235
    Roger Coathup
    Participant

    @dorothysulzmann

    No short cuts on jQuery – but it’s quite straightforward to setup a simple script like you’ll need: their site is good and full of useful examples: http://jquery.com/

    show() and hide() are basic jQuery – and there are plenty of animation options you can apply.

    Also, take a look in the WordPress codex re: wp_enqueue_script – their recommended way of loading javascripts.

    #95231
    dorothy sulzmann
    Participant

    Wow you know your stuff hnla! I get what you mean and will have a look at the jQuery show/hide bit – do you know where i can find this information?

    @questus5
    i found the details here for showing other profile groups – https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-show-multiple-profile-field-groups-on-register-php/

    Cheers for all your help guys!

    #95153
    Hugo Ashmore
    Keymaster

    @questus5

    Look at your bp admin section, you will see the custom profile link you use that to create new groups and fields, as long as a new group is created under the ‘Base’ level then it will appear on the registration page.

    @dorothysulzmann
    As a workaround I would move the three type selections labeled ‘Fan off’? to just after the primary details and use the tree types as just that to confer a user type to each member but also run a simple jQuery show/hide on the further groups so all are hidden and then a check is performed to catch the radio selection and the appropriate group revealed with perhaps a ‘none’ control selection default.

    The proper approach would be to complete a section and then pass the form control fields in a session or buffer to the next view to complete further sections but with BP that will likely start to get complicated, as techguy says there is no quick easy way to do this but with client side scripting it wouldn’t be that difficult.

    #15642
    fjrichman
    Member

    I’m having issues with indexes for everything http://www.thoughtsofthemasses.com/blogs/ for example. There’s a huge space that exists regardless of anything I’ve edited.

    I’m using the BuddyPress Template Pack Plugin to convert a WP Theme.

    Index PHP:
    `

     <a class="button" href="”>

    • <a href="”>
    • <a href="”>

    `

    CSS:
    `/*
    Theme Name: Andreas09
    Theme URI: http://webgazette.co.uk/wordpress-themes/wp-andreas09/
    Description: Highly customisable three column goodness.
    Author: Andreas Viklund and Ainslie Johnson
    Tags: orange, white, three column, flexible width, threaded comments, custom colors, buddypress

    andreas09 v1.0 (Dec 10th 2005) – An open source template by Andreas Viklund – http://andreasviklund.com. Free to use for any purpose as long as the proper credits are given to the original author.

    Ported to WordPress by Ainslie Johnson – Last updated 28/07/06
    */

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

    /* General Element Styling */

    body {
    background:#8b8b8b;
    color:#303030;
    font:76% Verdana,Tahoma,Arial,sans-serif;
    margin:0;
    padding:0;
    text-align:center;
    }

    a {
    font-weight:bold;
    text-decoration:none;
    }

    a:hover {
    color:#808080;
    text-decoration:underline;
    }

    p {
    line-height:1.5em;
    margin:0 0 15px;
    padding: 0px;
    }

    /* Captions and image alignment for wordpress */

    div.aligncenter {
    display: block!important;
    margin: 0px auto;
    }
    img {
    border-width: 0px !important;
    border-style: none !important;
    }
    div.alignleft {
    float: left!important;
    margin-right: 10px;
    }
    div.alignright {
    float: right!important;
    margin-right: 0px;
    margin-left: 10px;
    }
    .wp-caption {
    border: 1px solid #CCCCCC;
    text-align: center;
    background-color: #F8F8F8;
    padding-top: 4px;
    margin-top: 10px;
    margin-bottom: 10px;
    }

    .wp-caption img {
    margin: 0;
    padding: 0;
    border: 0 none;
    }

    .wp-caption p.wp-caption-text {
    font-size: 11px;
    line-height: 16px;
    padding: 5px 4px;
    margin: 0;
    font-family: Arial, Tahoma, “Lucida Sans”;
    color: #949494;
    font-style: normal;
    }

    p img {
    padding: 0;
    max-width: 100%;
    }

    img.centered {
    display: block;
    margin-left: auto;
    margin-right: auto;
    text-align: center;
    }

    img.alignright {
    padding: 4px;
    margin: 0 0 2px 7px;
    float: right;
    }

    img.alignleft {
    padding: 4px;
    margin: 0 7px 2px 0;
    float: left;
    }

    .alignright {
    float: right;
    }

    .alignleft {
    float: left;
    }

    /* End captions and image alignment */

    /*** Main container ***/

    #container {
    color:#303030;
    margin:0;
    min-width:770px;
    padding:0;
    text-align:left;
    width:100%;
    }

    /*** Header section ***/

    #sitename {
    color:#ffffff;
    height:90px;
    margin:0 20px 10px;
    text-align:left;
    }

    #sitename h1,#sitename h2 {
    font-weight:400;
    margin:0;
    padding:0;
    }

    #sitename h1 {
    font-size:2.4em;
    padding-top:20px;
    }

    #sitename h1 a {
    color: #ffffff;
    text-decoration: none;
    letter-spacing: 5px;
    }

    #sitename h2 {
    font-size:1.6em;
    }

    /*** Content wrap ***/

    #wrap {
    clear:both;
    font-size:0.9em;
    padding:0;
    margin-top: 5px;
    }

    /* Horizontal menu */

    #mainmenu {
    clear: both;
    width: 100%;
    margin: 0px;
    padding: 0px;
    }

    #mainmenu ul.level1 {
    border-top: 1px solid #fff;
    border-bottom: 1px solid #fff;
    }

    #mainmenu ul {
    background: #b0b0b0 url(images/menubg.jpg) center left repeat-x;
    padding: 0 0 0 5px;
    margin: 0px;
    border-bottom: 1px solid #fff;
    }

    #mainmenu li {
    display: inline;
    line-height: 25px;
    margin-left: -4px;
    padding: 0px;
    font-size: 0.9em;
    list-style: none;
    text-transform: uppercase;
    }

    #mainmenu a {
    padding: 6px 9px 6px 9px;
    text-decoration: none;
    border-right: 1px solid #B0B0B0;
    }

    #mainmenu li.current a {
    color: #000;
    }

    /*** Sidebars ***/

    #leftside,#rightside {
    margin:0;
    padding:0 10px 10px;
    width:165px;
    }

    #leftside {
    float:left;
    margin-right:10px;
    }

    #rightside {
    float:right;
    margin-left:10px;
    }

    #rightside img {
    border: 0px;
    }

    /*** Sidebar menu ***/

    #leftside h2, #rightside h2 {
    font-size: 1.4em;
    margin-top: 10px;
    padding: 5px 5px 5px 0;
    border-bottom: 1px solid #BEBFC3;
    }

    #leftside ul, #rightside ul {
    padding-left: 0px;
    margin: 0px;
    }

    #leftside li, #rightside li {
    list-style: none;
    }

    li#categories li a, li#archives li a, li.pagenav li a {
    background:#e8e9ea;
    border:1px solid #b0b0b0;
    display:block;
    margin-top:4px;
    padding:5px 4px 4px 10px;
    position:relative;
    text-transform: capitalize;
    width:140px;
    }

    li#categories li a:hover, li#archives li a:hover, li.pagenav li a:hover {
    background:#f8f9fa;
    border:1px solid #909090;
    color:#303030;
    text-decoration:none;
    }

    li#categories ul.children li a, li#archives ul.children li a, li.pagenav ul.children li a {
    font-size:0.8em;
    letter-spacing:1px;
    margin:3px 0 2px 10px;
    padding:4px 2px 2px 8px;
    width:125px;
    }

    li#categories ul.children li li, li#archives ul.children li li, li.pagenav ul.children li li {
    padding-left: 10px;
    }

    li#categories ul.children li li a, li#archives ul.children li li a, li.pagenav ul.children li li a {
    width: 115px;
    }

    li.feed {
    background: url(images/rss.gif) no-repeat left top;
    padding: 2px 0 8px 20px;
    }

    li#recent-comments ul li {
    padding-bottom: 5px;
    }

    li#recent-posts ul li {
    padding-bottom: 5px;
    }

    /*** Content ***/

    #content,#contentalt {
    background-color:#fafcff;
    border:1px solid #909090;
    color:#2a2a2a;
    padding:15px 20px 5px;
    }

    #content {
    margin:0 200px;
    }

    #contentalt {
    margin:0 200px 0 20px;
    }

    #content h1,#contentalt h1,#contentalt h2 {
    background-color:inherit;
    color:#606060;
    font-size:1.8em;
    font-weight:bold;
    letter-spacing:-1px;
    margin:0 0 15px;
    padding:0;
    }

    #content h1,#contentalt h1 {
    border-bottom: 1px solid #b0b0b0;
    }

    #content h2 {
    font-size:1.6em;
    color:#606060;
    }

    /* Archives/Links Page List styles */

    .archives li, .linkspage li {
    list-style: none;
    }

    .archives ul.children {
    padding-left: 10px;
    margin-left: 10px;
    }

    /*** Footer ***/

    #footer {
    background:#8b8b8b url(images/footerbg.jpg) top left repeat-x;
    clear:both;
    color:#000;
    font-size:0.9em;
    font-weight:bold;
    margin:0;
    padding:20px 0;
    text-align:center;
    width:100%;
    line-height: 1.5em;
    }

    #footer a {
    color: #d0d0d0;
    font-weight:bold;
    }

    /*** comments Form ***/

    #comment {
    width: 100%;
    border:1px solid #b0b0b0;
    }

    #commentform {
    width: 97%;
    }

    #author {
    border:1px solid #b0b0b0;
    }

    #email {
    border:1px solid #b0b0b0;
    }

    #url {
    border:1px solid #b0b0b0;
    }

    #submit {
    background:#f0f0f0;
    border:1px solid #b0b0b0;
    }

    #submit:hover {
    background: #e8e9ea;
    border: 1px solid #848484;
    cursor: pointer;
    }

    /* Image Display */

    .entry img, .entrytext img {
    border: 1px solid #b0b0b0;
    margin: 5px;
    padding: 5px;
    }

    .entry a:hover img, .entrytext a:hover img {
    border: 1px solid #505050;
    padding: 5px;
    }

    img.wp-smiley {
    border: 0px;
    margin: 0px;
    padding: 0px;
    }

    .thumbnail {
    background:#fafbfc;
    border:1px solid #b0b0b0;
    margin:0 0 10px 10px;
    padding:5px;
    }

    .left {
    background:#fafbfc;
    border:1px solid #b0b0b0;
    float:left;
    margin: 5px 15px 6px 0px;
    padding:5px;
    }

    .right {
    background:#fafbfc;
    border:1px solid #b0b0b0;
    float:right;
    margin: 5px 0px 6px 15px;
    padding:5px;
    }

    .noalign {
    background:#fafbfc;
    border:1px solid #b0b0b0;
    margin: 5px 5px 5px 5px;
    padding:5px;
    }

    /* Search Form */

    #searchform {
    margin-top: 10px;
    }

    #searchbox {
    background:#f0f0f0;
    border:1px solid #b0b0b0;
    margin:0 4px 0 0;
    width:160px;
    }

    #searchbutton {
    background:#f0f0f0;
    border:1px solid #b0b0b0;
    }

    #searchbutton:hover {
    background: #e8e9ea;
    border: 1px solid #848484;
    cursor: pointer;
    }

    /*** Comments Display ***/

    .postmetadata {
    background:#e8e9ea;
    font-size: 0.9em;
    border: 1px solid #b0b0b0;
    padding: 10px;
    margin: 0px;
    }

    ol.commentlist li {
    border: 1px solid #b0b0b0;
    padding: 10px;
    margin-bottom: 10px;
    }

    ol.commentlist li cite {
    text-transform: capitalize;
    }

    ol.commentlist li p {
    padding-top: 10px;
    }

    .alt {
    background:#e8e9ea;
    }

    /*** Text format ***/

    .intro {
    font-size:1.1em;
    font-weight:bold;
    letter-spacing:-1px;
    }

    blockquote {
    border: 1px dashed #b0b0b0;
    padding: 10px;
    margin: 30px;
    }

    blockquote p {
    padding: 0px;
    margin: 0px;
    }

    .small {
    font-size:0.8em;
    }

    .large {
    font-size:1.4em;
    }

    .center {
    text-align:center;
    }

    .category {
    border-bottom: 1px solid #b0b0b0;
    }

    .date {
    margin-top: -10px;
    padding-top: 0px;
    border-bottom: 1px solid #b0b0b0;
    }

    #page {
    border-bottom: 1px solid #b0b0b0;
    padding-bottom: 10px;
    margin-bottom: 10px;
    }

    /* Previous/Next Page Navigation */

    .navigation {
    margin: 0 0 20px 0;
    padding: 0 0 20px 0;
    border-bottom: 1px dashed #b0b0b0;
    }

    .bottomnavigation {
    margin: 30px 0 0 0;
    padding: 5px 0 30px 0;
    border-top: 1px dashed #b0b0b0;
    }

    .alignleft {
    float: left;
    text-align: left;
    }

    .alignright {
    float: right;
    text-align: right;
    }

    .post {
    padding-top: 0px;
    padding-bottom: 10px;
    margin: 0px;
    }

    /* Fix by Andy Skelton */

    .entry, .entrytext {
    overflow: hidden;
    }

    * html.entry, * html.entrytext {
    overflow: visible;
    height: 1px;
    }

    * html.entry p, * html.entrytext p {
    width: 99%;
    overflow: hidden;
    }

    .entrytext {
    padding-top: 0px;
    }

    /*** Various classes ***/

    .clearingdiv {
    clear:both;
    height:30px;
    width:1px;
    }

    .hide {
    display:none;
    }

    /* Widgets */
    .rsswidget {
    border:0px;
    vertical-align: bottom;
    }
    /*** End of file ***/.commentlist li li {
    list-style-type: none;
    }

    /* > Item Headers (Profiles, Groups)


    */

    div#item-header {
    overflow: hidden;
    }
    div#item-header div#item-header-content { margin-left: 170px; }

    div#item-header h2 {
    font-size: 28px;
    margin: 0 0 15px 0;
    line-height: 120%;
    }
    div#item-header h2 a {
    text-decoration: none;
    color: #777;
    }

    div#item-header img.avatar {
    float: left;
    margin: 0 15px 25px 0;
    }

    div#item-header h2 { margin-bottom: 5px; }

    div#item-header span.activity, div#item-header h2 span.highlight {
    vertical-align: middle;
    font-size: 11px;
    font-weight: normal;
    line-height: 170%;
    margin-bottom: 7px;
    }

    div#item-header h2 span.highlight { font-size: 16px; }
    div#item-header h2 span.highlight span {
    position: relative;
    top: -2px;
    right: -2px;
    font-weight: bold;
    font-size: 11px;
    background: #a1dcfa;
    color: #fff;
    padding: 1px 4px;
    margin-bottom: 2px;
    -moz-border-radius: 3px;
    -webkit-border-radius: 3px;
    vertical-align: middle;
    cursor: pointer;
    display: none;
    }

    div#item-header div#item-meta {
    font-size: 14px;
    color: #aaa;
    padding-bottom: 10px;
    overflow: hidden;
    margin: 15px 0 5px 0;
    }

    div#item-header div#item-actions {
    float: right;
    width: 20%;
    margin: 0 0 15px 15px;
    text-align: right;
    }
    div#item-header div#item-actions h3 {
    font-size: 12px;
    margin: 0 0 5px 0;
    }

    div#item-header ul {
    overflow: hidden;
    margin-bottom: 15px;
    }

    div#item-header ul h5, div#item-header ul span, div#item-header ul hr {
    display: none;
    }

    div#item-header ul li {
    float: right;
    }

    div#item-header ul img.avatar, div#item-header ul.avatars img.avatar {
    width: 30px;
    height: 30px;
    margin: 2px;
    }

    div#item-header div.generic-button, div#item-header a.button {
    float: left;
    margin: 10px 10px 0 0;
    }

    div#item-header div#message.info {
    line-height: 80%;
    }

    /* > Item Lists (Activity, Friend, Group lists)


    */

    ul.item-list {
    width: 100%;
    }
    ul.item-list li {
    position: relative;
    padding: 15px 0;
    border-bottom: 1px solid #eaeaea;
    }
    ul.single-line li { border: none; }
    body.activity-permalink ul.item-list li { padding-top: 0; }

    ul.item-list li img.avatar {
    float: left;
    margin: 0 10px 10px 0;
    }

    ul.item-list li div.item-title, ul.item-list li h4 {
    font-weight: normal;
    font-size: 14px;
    width: 75%;
    margin: 0;
    }
    ul.item-list li div.item-title span {
    font-size: 12px;
    color: #999;
    }

    ul.item-list li div.item-desc {
    margin: 10px 0 0 64px;
    font-size: 11px;
    color: #888;
    width: 50%;
    }

    ul.item-list li div.action {
    position: absolute;
    top: 15px;
    right: 0;
    text-align: right;
    }

    ul.item-list li div.meta {
    margin-top: 10px;
    color: #888;
    font-size: 11px;
    }

    ul.item-list li h5 span.small {
    font-weight: normal;
    font-size: 11px;
    }

    /* > Item Tabs


    */

    div.item-list-tabs {
    clear: left;
    overflow: hidden;
    margin: 25px -19px 20px -19px;
    background: #eaeaea;
    }
    div.item-list-tabs ul li a {
    text-decoration: none;
    }

    div.item-list-tabs ul {
    width: 100%;
    }
    div.item-list-tabs ul li {
    float: left;
    margin: 5px 0 0 5px;
    }
    div.item-list-tabs#subnav ul li {
    margin-top: 0;
    }

    div.item-list-tabs ul li:first-child {
    margin-left: 20px;
    }

    div.item-list-tabs ul li.last {
    float: right;
    margin: 7px 20px 0 0;
    }
    div.item-list-tabs#subnav ul li.last {
    margin-top: 4px;
    }

    div.item-list-tabs ul li.last select {
    max-width: 175px;
    }

    div.item-list-tabs ul li a,
    div.item-list-tabs ul li span {
    display: block;
    padding: 5px 10px;
    text-decoration: none;
    }
    div.item-list-tabs ul li span {
    color: #aaa;
    }

    div.item-list-tabs ul li a span {
    display: inline;
    padding: 0;
    color: inherit;
    }

    div.item-list-tabs ul li.selected a,
    div.item-list-tabs ul li.current a {
    background-color: #fff;
    color: #555;
    font-weight: bold;
    -moz-border-radius-topleft: 3px;
    -webkit-border-top-left-radius: 3px;
    -moz-border-radius-topright: 3px;
    -webkit-border-top-right-radius: 3px;
    }
    ul li.loading a {
    background-image: url( ../images/ajax-loader.gif );
    background-position: 92% 50%;
    background-repeat: no-repeat;
    padding-right: 30px !important;
    }
    div#item-nav ul li.loading a {
    background-position: 88% 50%;
    }

    div.item-list-tabs#object-nav {
    margin-top: 0;
    }

    div.item-list-tabs#subnav {
    background: #fff;
    margin: -15px -19px 15px -19px;
    border-bottom: 1px solid #eaeaea;
    min-height: 35px;
    overflow: hidden;
    }

    div.item-list-tabs ul li.feed a {
    background: url( ../images/rss.png ) center left no-repeat;
    padding-left: 20px;
    }

    /* > Item Body


    */

    .item-body {
    margin: 20px 0;
    }

    span.activity, div#message p {
    display: inline-block;
    font-size: 11px;
    font-weight: normal;
    background: #FFF9DB;
    border-bottom: 1px solid #FFE8C4;
    border-right: 1px solid #FFE8C4;
    color: #ffa200;
    padding: 1px 8px;
    margin-top: 6px;
    text-decoration: none;
    -moz-border-radius: 3px;
    -webkit-border-radius: 3px;
    border-radius: 3px;
    }

    /* > Directories (Members, Groups, Blogs, Forums)


    */

    div.dir-search {
    float: right;
    margin: -37px 0 0 0;
    }
    div.dir-search input[type=text] {
    padding: 4px;
    font-size: 12px;
    }

    /* > Pagination


    */

    div.pagination {
    margin: -15px -20px 9px -20px;
    border-bottom: 1px solid #eaeaea;
    padding: 10px 20px 10px 20px;
    color: #888;
    font-size: 11px;
    height: 16px;
    }
    div.pagination#user-pag, .friends div.pagination,
    .mygroups div.pagination, .myblogs div.pagination, noscript div.pagination {
    background: #f8f8f8;
    border: none;
    padding: 8px 15px;
    }

    div.pagination .pag-count {
    float: left;
    }

    div.pagination .pagination-links {
    float: right;
    }
    div.pagination .pagination-links span,
    div.pagination .pagination-links a {
    font-size: 12px;
    padding: 0 5px;
    }
    div.pagination .pagination-links a:hover {
    font-weight: bold;
    }
    `

    #91770
    Pagan Gwynne
    Participant

    1. Could you set this as a profile field ? For ex. A dropdown list added to the registration page where they state yes or no to a question on hospitality. If they answer yes they can be autojoined to the ‘yes’ group so everyone will know where to look for them.

    2. If you are running a WP multisite you could set up a blog called ‘work listings’ or something like that, allow everyone ‘author’ capabilities set up one page as a standardized form and another to show the results of the posted form set the excerpts to show 0 -zero- characters and you’ll have a multipost page with a listing of jobs. – There are a number of plugins that will autojoin users to specific blogs on a multisite –

    3. Same thoughts as with 2.

    5. If you do a search for plugins there are a few that offer events calendars. Right now I’m using ‘My Calendar’ which offers an easily customizable interface so that you can make it look like your main site.

    7. A simple page with a ‘donate’ button linked to paypal or whoever

    8. WP multisite does this. If you set it so that users can create a blog on registration they can name the blog anything they like, I don’t know if you can automate the process so that the blog-name field is pulled from their username, or you can have a strict naming policy, add some text to the reg form stating that only the username is acceptable for blog names and set the joining process under moderation so that you have to approve each that way each blog will be called registeredusername.mydomain.com for subdomain installs or mysite.com/regusername for sub directory install.

    4 & 6 I have no idea.

    As for the plugins most come with the ability to activate either for one blog or for network activation, using the plugin ‘exclude plugins’ you can hide the plugins from your users blogs or allow certain plugins but disallow others. For ex, I have a user that wanted the plugin ‘ephemeris’ on their blog, I installed it, allowed it for that site and they are now happily ephemerising awaywhilst other users aren’t even aware that the plugin exists (they don’t see it on their blogs)

    The plugins that I’m using I pulled straight from the WP plugin pages and so far they have all worked on my WPBP site without hiccup,

    Regards.
    Me.

    #90542

    In reply to: Introducing JobBoardr

    Michael Eisenwasser
    Participant

    I think €100 is well worth it for a good plugin. If the plugin means I can save a lot of time and get the results I need immediately, then yeah I’ll happily pay. My time and frustration are worth money too. If he spends 20 hours developing a plugin and I buy it for €100, I think I just got a great deal!

    I find this JobBoardr plugin particularly interesting because we had a similar plugin written for our site, easyoutsource.com. It’s a job hiring site for Americans to hire people in the Philippines as online workers. The big issue, as you’ve already discovered I’m sure, is how to separate the roles. We set up a custom field for workers and one for employers and made you pick your role on signup. The role is just a profile field you select on signup. Then on the site every function is dependent on which role you picked. Groups have been turned into jobs entirely. Employers can create groups and workers can apply to them. Another big issue we had was that employers always showed up in the search results. We wanted to display workers (members) and jobs (groups). No employers. So we had to get a custom plugin written (by the ever so talented R-a-y) to hide employers from search results.

    It’s interesting that you’ve set it up so that employers ARE groups and workers are members. Are your employers not also members? Do they have their own profile pages? How did you get this to work correctly?

    #90525
    pcwriter
    Participant

    .You could also try my plugin (he says with shameless self-promoting grin).

    See this post for the latest beta version: https://buddypress.org/community/groups/add-all-nav-links-to-bp-adminbar/forum/topic/updated-the-beta/
    Here are the user configuration options available in the admin panel under “Settings” > “BP-WP-Navbar”
    – Hide or display the main theme navigation
    – Hide or display the site name in your new adminbar
    – Hide or display the Login and Signup links in the adminbar
    – Hide or display the “Visit Random” menu
    – Select whether to display top-level WordPress pages horizontally or in a dropdown menu
    – Define the label for the dropdown in WordPress 2.x
    – If you’re running WP3.x, the plugin will fetch whatever custom menu labels you assign and display them in the admin bar along with all child pages in dropdowns
    – Define the label for the Buddypress directory dropdown (default = “Community”)
    – Define the font, font-weight and font-style for all menu items
    – Define ALL colors: navbar background, main and sub menu item backgrounds, border, text and hover colors too
    – Set the overall width of the navbar and of sub-menus
    – Set the height of all menu items
    – Adjust margins where required
    – Reposition your fancy new custom navbar anywhere you like, relative to your theme so it scrolls with your pages

    If you add categories to your custom menus in WP3.x, the plugin will pick them up and display them in whichever menus they are assigned to. Give it a whirl.

    #90401
    pcwriter
    Participant

    @jenyus

    Here comes some shameless self-promotion! Try the beta-version of my plugin: Add-All-Nav-Links-To-BP-Adminbar. You can add all your main navigation items to the bp-adminbar, hide your theme’s main nav, then customize your new adminbar just about any way you like, including repositioning the whole thing anywhere on your pages. Here’s a screenshot of the backend admin panel: http://i33.tinypic.com/2nvea8j.jpg

    You can download from my site here:
    http://nowrecovery.com/downloads/add-all-nav-links-to-bp-adminbar2.1beta.zip

    The current release is available here:
    https://buddypress.org/community/groups/add-all-nav-links-to-bp-adminbar/

    If you try it, please let me know what you think in the plugin’s forum :-)

    #89477

    In reply to: Hide Number of Friends

    PJ
    Participant

    Are you asking if there is a way to have a user’s friends only available to him or her? Adult dating sites and consulting groups/companies find the end users like a layer of privacy that doesn’t let site users see their friend connections. I dont know if it can be done in buddypress.

    You could go line by line through the theme to remove pages that display friends, but I’ve never tried to see if it would work.

    #88741
    Hugo Ashmore
    Keymaster

    Good spot, that’s why second eyes are vital, also the $hideMainNav doesn’t need to be globally scoped as the function sits outside pages() and the variable is already in the main page scope so no global required for it.
    Not sure how the process works for uploading plugins but would guess it hasn’t been approved yet?

    If I have a minute I’ll add the config variable for ‘Community’ link then you can run things through their paces when your back.

    #14188
    ndayakar
    Participant

    Is it possible to hide Groups widget in the blog page? BTW, I have only two pages at our buddypress installation. One is Groups page and other is Blog page. Could you someone please help me how to hide groups widget in the Blog page.

    Thank you,
    Dayakar

    #88615
    Hugo Ashmore
    Keymaster

    @pcwriter

    I’ve had to do a fairly extensive rewrite on the function for a number of reasons:

    1/ There was a significant degree of malfomed ul child nesting which prevents drop down aspects working correctly primarily I’ve removed the opening and closing UL elements as they are not required and cause issues.

    2/ Not sure how the wp_list_pages was intended to work but with the parameter ‘title_li’ declared as empty you correctly remove the wrapping elements but would need to add UL elements manually wrapping the function call for the dropdown to function correctly.

    3/ Added back in the wp_nav_menu function calls but wrapped them in a check to see if WP 3.0 is running i.e are the new menu available if not hide altogether.

    Also added a reverse check to remove the wp_list_pages function if using the new menus as there is little point in both and the new menu system serves better.

    4/ Changed region and menu top link names to ‘pages’ but this area is a fundamental issue as it cant be known what the user sets as menu names, ideally one shouldn’t hard code values but retrieve them from the admin menu area, but this proves far too hard to work out (asked a question on WP support but haven’t had a reply and I don’t expect one – sadly there is little codex documentation of any depth on the new menus.)

    This issue applies to the wp_list_pages as well as you can’t really pass any values for ‘include’ and ‘exclude’ as these values can’t be known so you ought to remove those values you have hardcoded (I have left them in).

    If I can get some guidance on how to fetch values from the menu backend view such as menu names then it will be possible to make the menus far more effective but have spent quite a while trawling through the core WP files for nav-menu and it’s not obvious and too time consuming.

    I have copied the revised code to this pastebin page, give it a check over, but don’t assume I have things all correct, run it as plugin copy 2

    http://pastebin.com/trUDaPEP

    #87275

    In reply to: hide menu/tab/link

    intimez
    Participant

    I currently have the entire line commented out but would like certain pages to show.

    Can anyone explain how this works?

    bp-themes/bp-default/header.php

    code not show but it’s line 79
    wp_list_pages( ‘title_li=&depth=1&exclude=’ . bp_dtheme_page_on_front() );

    #13816
    intimez
    Participant

    searched “hide tab” “hide menu” “hide link” and can’t find solution

    default theme list pages along with default link

    how can hide certain pages?

    example:
    Home | Members | Groups | Forums | Photos

    Photos = page = hide

    [wordpress3+buddypress1.2.5.2]

Viewing 25 results - 226 through 250 (of 289 total)
Skip to toolbar