Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'wordpress'

Viewing 25 results - 18,901 through 18,925 (of 22,650 total)
  • Author
    Search Results
  • sueme
    Participant

    All I need now is for the ‘Home’ link in the header to point to mysite.com it currently points to mysite/wordpress

    Anyone know how I change this?

    The bp theme header shows

    <div id="header">

    <h1 id="logo"><a>" title="<?php _e( 'Home', 'buddypress' ) ?>"><?php bp_site_name() ?></a></h1>

    <ul id="nav">
    <li<?php if ( bp_is_front_page() ) : ?> class="selected"<?php endif; ?>>
    <a>" title="<?php _e( 'Home', 'buddypress' ) ?>"><?php _e( 'Home', 'buddypress' ) ?></a>

    So presumably (says she with little knowledge) I need to change this to something else?

    sueme
    Participant

    When I go direct to mysite.com it goes to my correct homepage and the default homepage tag is highlighted, but if I actually click on that tag it takes me to the mysite/wordpress folder list. weird!

    Craig Sunney
    Participant

    Actually I am trying to solve the same situation…only with more access levels Free Bronze, Silver and Gold.

    I do have role manager running access to pages nicely via wishlist member…..and I need something to bridge to protect forums by role.

    sueme
    Participant

    I have checked the above instructions. I’m using the above code and my site is sorted except for the ‘Home’ Page.

    All my links, BuddyPress and the pre-existing WordPress links all open on the correct page except the ‘Home Page.

    I’m using BuddyPress default theme and when I activated it. it created a ‘Home’ tag that goes straight to the Mysite/WordPress folder and lists its content.

    I’ve created a static ‘Home’ page, and this to has created a ‘Home’ tag in the header that does actually go to the home page.

    So, currently, I’ve got two ‘Home’ links in my header, an incorrect one taking me to a folder list, and a correct one taking me to my home page.

    Is there a way of getting rid of the default home page, just leaving me with the new one I’ve created?

    r-a-y
    Keymaster

    With the above code snippet, your BP pages should actually go to mysite.com/BPpage.

    If you did not use the code snippet above, your BP pages would reside at mysite.com/wordpress/BPpage.

    So if BP wasn’t running correctly before the snippet, there’s something larger going on.

    I think you should double-check these instructions again:

    https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

    sueme
    Participant

    The Homepage link previously went direct to mysite.com and all my pages or blogs were at mysite.com/pagename.

    Now all the new BuddyPress pages go to mysite/wordpress/buddypresspage That’s OK

    All my previous pages and blogs still go to mysite/pagename That’s OK

    The only problem is my ‘Homepage’ which was showing my most recent blogs but now shows mysite/wordpress

    To be honest, I don’t know what would have happened if I’d gone to mysite/wordpress before, because nothing ever went to it!

    Just worked out that if I change ‘Settings – Reading’ to ‘Static Page’ instead of ‘Latest Posts’ then the ‘Home’ Link will go to it, so will use that as a work around for now. Would still like to get my home page back to ‘Latest Posts’ though.

    r-a-y
    Keymaster

    Kind of hard to debug without seeing your site and theme code.

    Did your homepage link previously direct to mysite.com?

    Also, before adding the above code snippet, what happened when you went directly to mysite.com/wordpress?

    #71094
    Kye
    Participant

    @ Andrea_r

    Yeah I realise that now after having a play with it

    I inadvertently asked a similar yet different question in another thread, perhaps it could be considered a half way for this also. It involves using the domain map plugin and then adding the following to the wp-config.php:

    Allow BuddyPress to function on multiple blogs of a WPMU installation, not just on one root blog:

    define ( ‘BP_ENABLE_MULTIBLOG’, true );

    It wouldn’t give each site its own buddypress, but it would let you share the one install.

    I’ve not actually tested all this but it seems logical.

    I know there also use to be a plugin that allowed you to be an oid provider, the WP directory shows its last update as 2007 though so not sure how viable an option that would be.

    https://wordpress.org/extend/plugins/mu-open-id/

    #71093
    jillsays
    Member

    Correct. We can not get past the registration page. I find it incredibly odd that you can, and the 10 of us can not. I’ve cleared the cache, but that doesn’t matter because I have tried from multiple computers. I also have friends trying from multiple states in the USA. I’ve also tried from my iPhone. Not one of us can get past the initial registration page because it refreshes itself.

    I just did a fresh install of Buddypress up on another WordPress blog that is running 2.9.1 and we are having the exact same problem.

    Can anyone shed any light on this odd behavior?

    #71078
    r-a-y
    Keymaster

    Increase your PHP memory limit then.

    Read this:

    https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

    Increase your limit to 128MB or higher.

    #71074
    nagoonline
    Member

    This is the error I am getting:

    Fatal error: Allowed memory size of 262144 bytes exhausted (tried to allocate 122880 bytes) in /home2/cwcreati/public_html/noramoc/wordpress/wp-settings.php on line 129

    #71069
    gregfielding
    Participant

    @Djsteve

    This seems like a buddypress flaw, not a wordpress or mu issue.

    Perhaps if buddypress can’t read the wpmu blocked domains, maybe BP needs it’s own domain banner.

    #71068
    djsteve
    Participant

    This has been a wordpress mu issue for a while off and on.. I discussed an idea about at mu forums:

    https://mu.wordpress.org/forums/topic/13982

    [blockquote]

    I too have noticed that even putting domains in the block list seems to not stop future registrations. Here is a thought of mine.

    MAYBE a spammer actually signs up 100 new accounts, and then only activates one a day. So even though we have added his domain to the ban list for signups, he still has 99 more that have been signed up, but not yet activated?

    If this is the case I would like to see MU add core code that checks to see upon activation if the domain they originally used to signup has since been banned, and then prevent them from activating if it has.

    Just a thought, not sure if this is the case – but it may be worth looking into.

    [/blockquote]

    It was suggested that I add this suggestion to the trac, ( https://core.trac.wordpress.org/ )

    but I really don’t know how to use that thing…

    not sure that it is a buddypress specific issues, but I DO believe that the spammers are looking for buddypress phrases when compiling their lists of sites to hit…

    #71061
    Sam Steiner
    Participant

    I’m having 300 spam registrations a day and having to mark them all as spam manually 15 in one go in the user list. The plugin wordpress Hashcash (updated today to 4.5.1) should now work for BuddyPress registration but it stops EVERYBODY from registering.

    David Lewis, one week later, is your solution still working for you?

    #71057
    sueme
    Participant

    I’m currently running an active site, and having followed the instructions in https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory I’ve got all my files in a mysite/wordpress file with everything in the wordpress folder but the index.php and .htaccess files in the home directory. that’s given the whole of my site a mysite address rather than a mysite/wordpress address.

    This sites been up a while and works well, but I’m having trouble getting BuddyPress to work on it. Whatever I try, I seem to end up with half the site still on mysite (whilst everything in mysite/wordpress is coming up unobtainable); or half the site on mysite/wordpress (whilst everything in mysite is unobtainable).

    There’s quite a bit of activity on the site, so I don’t want to start from scratch, but I would like to get BuddyPress on it. Has anyone worked out how to do this yet?

    I tried the solution at https://buddypress.org/forums/topic/permalinks-setup-with-wp-intalled-in-subdirectory-and-indexphp-in-root?replies=23#post-45920 (which is marked “Resolved”) but it didn’t work for me.

    sueme
    Participant

    Didn’t get a reply so I tried it anyway. It didn’t work for me.

    1. The top of my page displayed the following message function my_bp_override_core_domain() { $domain = get_bloginfo('url'); return $domain; } add_filter('bp_core_get_root_domain','my_bp_override_core_domain')

    2. The buddypress folder still opened as mysite/wordpress rather than just mysite.

    #71051
    rich! @ etiviti
    Participant

    Expected behavior as activity commenting and forum discussion are separate. (only a one way tie-in when a new post/reply is made and the content is sent to the activity stream). You can disable activity commenting on forum posts/topics and blogs postings.

    I updated

    https://wordpress.org/extend/plugins/buddypress-group-forum-extras/

    which now includes an activity subplugin -> will pull in activity comments made to a topic post (no reply ability but at least someone can see the conversation from the stream)

    #71049
    gaysurfers
    Participant

    Hey Pigi, I have the same problem, i don’t Know how to “Set my members.php to use “BP_Members_Filter” instead of “BP_Core_Members_Template””

    I don’t understand where i can find “members.php” file.

    is ‘BP Member Filter’ plugin not compatible with wordpress 2.9.2 ??

    #71048
    mcrustk2
    Participant

    Im having a very similar problem.

    I have installed WordPress MU & Buddypress on a sub domain:

    http://site.mydomain.com

    When I login I can click on ‘My Account’ if I click ‘Edit Profile’ I get a 404 error. Any of the other my account options such as change signature or change avatar works OK.

    Also noticed that if using the Album+ plugin, when I click upload a picture it does the upload but then immediatly shows a 404.

    Assume this is related in some guise to the subdomain. Maybe WordPress/Buddypress is best left on the root?

    Just installed:

    WordPress MU 292

    BuddyPress 123

    IIS6 (Hosted/Helm) PHP 5

    #71042
    MrMaz
    Participant

    @stwc, foxly

    That defect was fixed in the 0.3 branch a while back, I just haven’t put out a point release yet.

    https://plugins.trac.wordpress.org/changeset/215107/buddypress-links/branches

    #71027
    foxly
    Participant

    @Andy Peatling – Very sad to be in hall of shame :( :(

    1) Version 0.1.6 of BP Album+ that is posted on the WordPress plugin repository checks that BP is installed exactly as you have specified. Can you be a bit more specific about the defect?

    2) I completely agree that current_user_can() is a better way to check for permissions in various plugin operations; and we will switch to the new function at the next BP Album+ release as per your request. In the meantime, why is using is_site_admin() so bad? Doesn’t current_user_can() just pass the call to is_site_admin() ?

    /**

    * Whether current user has capability or role.

    *

    * @since 2.0.0

    *

    * @param string $capability Capability or role name.

    * @return bool

    */

    function current_user_can( $capability ) {

    $current_user = wp_get_current_user();

    if( is_site_admin() ) <—- *NOTE*

    return true;

    if ( empty( $current_user ) )

    return false;

    $args = array_slice( func_get_args(), 1 );

    $args = array_merge( array( $capability ), $args );

    return call_user_func_array( array( &$current_user, ‘has_cap’ ), $args );

    }

    ^F^

    #71022
    foxly
    Participant

    @21cdb – Its open on my workstation right now, getting written. I’m just checking over some of our source files right now to make sure all of our functions properly deal with the situation that was causing the defect in BP Links. Then it’s back to work on the multiple album capabilities.

    I would guess perhaps 2 or 3 days more work before we post another beta.

    Following that, we’re going to be doing all our dev work through the WordPress SVN, so you’ll be able to download updated files like …every night, if you want to.

    We are currently working on:

    1) Multiple albums for each user

    2) Album-based workflow. Basically a copy of Facebook’s Photo app.

    3) Albums for groups.

    While FaceBook is a good start, nobody has ever implemented an effective albums for groups application before, so there is no “gold standard” for us to copy. You can greatly accelerate the development process by helping us design one.

    We use something called a “user story” to describe BP Album+ from different points of view:

    http://en.wikipedia.org/wiki/User_stories

    Can you guys write a user story from the point of view of:

    1) An administrator

    2) An anonymous user off the Internet

    3) A logged-in member viewing their own profile

    4) A logged-in member viewing a friend’s profile

    5) A logged-in member viewing a stranger’s profile

    ^F^

    #71014
    foxly
    Participant

    Regarding problems with the BuddyPress Links plugin… ;)

    Found the defect.

    The problem is being caused by two blocks of code inside the BPLinks plugin that do not account for the situation where the BuddyPress administrator disables “friend” capabilities for the site.

    When friend capabilities are disabled, calling the friends_check_friendship() function will crash the user thread. We handle this problem in BP Album+ by wrapping all calls to this function in a function_exists(‘friends_check_friendship’) statement, only calling the function if it is enabled.

    This is a sneaky, subtle defect that could easily be missed during testing; fortunately, BPLink’s clean, well-documented source code made it easy to isolate and correct the problem.

    Here’s a simple patch:

    1) In “bp-links-classes.php” at line 650

    REPLACE:

    if ( $link_owner_user_id && $link_owner_user_id != $bp->loggedin_user->id && friends_check_friendship( $link_owner_user_id, $bp->loggedin_user->id ) ) {

    $status_opts[] = self::STATUS_FRIENDS;

    }

    WITH:

    if (function_exists(‘friends_check_friendship’)) {

    if ( $link_owner_user_id && $link_owner_user_id != $bp->loggedin_user->id && friends_check_friendship( $link_owner_user_id, $bp->loggedin_user->id ) ) {

    $status_opts[] = self::STATUS_FRIENDS;

    }

    }

    2) In “bp-links-core.php” at line 1128

    REPLACE:

    return friends_check_friendship( $user_id, $link->user_id );

    WITH:

    if (function_exists(‘friends_check_friendship’))

    return friends_check_friendship( $user_id, $link->user_id );

    else

    return null;

    ============================================================================

    WordPress MU 2.9.2

    BuddyPress Version 1.2.3

    BuddyPress Links Version 0.3.2

    BP Album+ 0.1.8 beta

    ^F^

    #71013
    foxly
    Participant

    @stwc – Found the defect.

    The problem is being caused by two blocks of code inside the BPLinks plugin that do not account for the situation where the BuddyPress administrator disables “friend” capabilities for the site.

    When friend capabilities are disabled, calling the friends_check_friendship() function will crash the user thread. We handle this problem in BP Album+ by wrapping all calls to this function in a function_exists(‘friends_check_friendship’) statement, only calling the function if it is enabled.

    This is a sneaky, subtle defect that could easily be missed during testing; fortunately, BPLink’s clean, well-documented source code made it easy to isolate and correct the problem.

    Here’s a simple patch:

    1) In “bp-links-classes.php” at line 650

    REPLACE:

    if ( $link_owner_user_id && $link_owner_user_id != $bp->loggedin_user->id && friends_check_friendship( $link_owner_user_id, $bp->loggedin_user->id ) ) {

    $status_opts[] = self::STATUS_FRIENDS;

    }

    WITH:

    if (function_exists(‘friends_check_friendship’)) {

    if ( $link_owner_user_id && $link_owner_user_id != $bp->loggedin_user->id && friends_check_friendship( $link_owner_user_id, $bp->loggedin_user->id ) ) {

    $status_opts[] = self::STATUS_FRIENDS;

    }

    }

    2) In “bp-links-core.php” at line 1128

    REPLACE:

    return friends_check_friendship( $user_id, $link->user_id );

    WITH:

    if (function_exists(‘friends_check_friendship’))

    return friends_check_friendship( $user_id, $link->user_id );

    else

    return null;

    ============================================================================

    WordPress MU 2.9.2

    BuddyPress Version 1.2.3

    BuddyPress Links Version 0.3.2

    BP Album+ 0.1.8 beta

    ^F^

    #70990

    In reply to: plugin errors

    Paul Wong-Gibbs
    Keymaster

    @nagoonline: you have asked this in another post, and we have answered. Do not double-post.

    EDIT: Also, sending me a private message is not going to get you a reply any quicker. You could have searched Google to resolve this issue, as it’s a common WordPress “plugins broken my site” question.

Viewing 25 results - 18,901 through 18,925 (of 22,650 total)
Skip to toolbar