Shape the future of Social networking with WordPress: Join Project Midnight Sun! The next generation platform for community building with WordPress!

BuddyDev

Search

Replies

  • Keymaster
    (BuddyDev Team)
    Posts: 25472
    Brajesh Singh on in reply to: Categories for media #12936

    Hi George,
    Thank you.

    Now, I understand it. Listing is more complex than expected as we will need to honour the media status too.

    I am looking at some approaches(we can limit to logged in/public) and will get back to you with the correct.

    The two approaches I am considering is

    1. using pre_get_posts but specify tax arguments to force the status
    2. Or using MPP_Media_Query

    I am not sure which approach should we go as the first won’t need modification of template but second will be more intuitive(needs theme template modification though).

  • Keymaster
    (BuddyDev Team)
    Posts: 25472
    Brajesh Singh on in reply to: [Resolved] Upload has stopped working? #12935

    Thank you.
    Glad that you found it.

  • Keymaster
    (BuddyDev Team)
    Posts: 25472

    Hi Ken,
    We are using google doc viewer for it.

    If the update is not showing the preview, I will suggest disabling the doc viewer and making the doc files just attachment.

    You can do that by following this
    https://buddydev.com/mediapress/tips/how-disable-google-doc-viewer-mediapress/

    Regards
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 25472

    Hi Richard,

    The above css is updated css with media query and it won’t apply on small screen devices. Try replacing the old css with it and then clearing cache etc.

    It should work(Let MediaPress use the original css on mobile).

    Regards
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 25472

    Hi Richard,
    There are multiple ways to achieve it.

    We can use css media query for the same.

    For example, here is how we use the old css to target viewport with min-width:980px

    
    @media screen and (min-width: 980px) {
        .mpp-lightbox-content {
            width: 90%;
            display: flex;
            height: auto;
            min-height: 400px;
    
        }
    
        .mpp-lightbox-media-container {
            flex: 1;
            width: auto;
        }
    }
    

    You can customize it as you please.

    Hope that helps.

    Regards
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 25472
    Brajesh Singh on in reply to: [Resolved] BuddyBlog privacy (not) #12921

    Hi Richard,
    Please ask the plugin developer on how to allow excluding some part.

    You can test for BuddyBlog component using

    
    
    if ( bp_is_current_component( 'buddyblog' ) ) {
    
    }
    
    

    Another option will be to make the blog posts as part of the site blog instead of separate by user.

    Regards
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 25472
    Brajesh Singh on in reply to: Categories for media #12920

    Hi George,
    I am sorry I had left early yesterday and was not able to assist.

    There are a few things I will need to know:-
    1. How are you enforcing the privacy?
    2. What is the name of the taxonomy that you are using.
    3. Are you using the same taxonomy for attachment and other post types too?

    Please let me know and I will assist.

    Thank you
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 25472

    No problem.
    Thank you for the update and marking it as resolved.

  • Keymaster
    (BuddyDev Team)
    Posts: 25472

    Hi CapCa,
    Welcome to BuddyDev.

    In your case, member types seems to be a much better option. Use member types to create mutually exclusive groups of users and then you can use xprofile_query to easily display the list of users from the complementry type based on the current user’s member type.

    Your approach for creating a normal profile field with the options will work too but won’t be as efficient as using member type in this case.

    Bets Regards
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 25472

    Hi Richard,
    I am trying to recreate this too. If I am able to do it I will post a solution. If you are able to find a reason, Please do let me know. It is possible if the allowed status is not supported by the component(say ‘public’ status is not supported by members component).

    But I am not sure if that is the case(as you are mentioning that it is working for some of the users).

    regards
    Brajesh