BuddyDev

Search

Replies

  • Participant
    Level: Master
    Posts: 279
    NikB on July 9, 2019 at 6:15 pm in reply to: [Resolved] BuddyPress Xprofile Member Type Field – Description #24005

    Thank you so much Brajesh! Works like a dream (and translated easily too) 😉

    Warm regards
    Nik

  • Participant
    Level: Master
    Posts: 279
    NikB on July 8, 2019 at 10:17 am in reply to: BuddyPress Xprofile Custom Field Types – translation #23945

    Thank you Brajesh.

    I’ve downloaded and updated the .po and .mo files but when I use WPML to search for the strings I’ve manually entered for “Use this field to write a text that should be displayed beside the checkbox:” eg. “I confirm that I have read the T&C” they’re still not showing up.

    Although the description for that same field DOES show up under the domain “Buddypress Multilingual”.

    Again, I will admit that I’m new to translation so admittedly I may be missing something obvious.

    I’ll look out for the release anyway.

    Warm regards
    Nik

  • Participant
    Level: Master
    Posts: 279
    NikB on July 8, 2019 at 8:00 am in reply to: BuddyPress Xprofile Custom Field Types – translation #23940

    Brajesh… you are an absolute star!

    I was wondering if I could manage to tweak the code somehow but I’m really too new to translations to make that an easy task 😉

    With many thanks in advance and yes please do let me know when the update is ready.

    Warm regards
    Nik

  • Participant
    Level: Master
    Posts: 279
    NikB on July 5, 2019 at 7:33 am in reply to: BuddyPress Xprofile Member Type Field – Translation #23864

    Hi Brajesh

    Thank you so much for giving this a bit more thought!

    I’m not sure I 100% understand what you’re saying(!) but if I’m understanding correctly that this would mean keeping the membertype key and label the same (regardless of which language they were using) that could definitely work.

    I’ll investigate the gettext filter a bit more to see if I can figure it out (I’m assuming this would need to be done in code?) although obviously if you do have time to give an example, that would be hugely helpful (eg. for simplicity’s sake, let’s say the site is in English/German and membertypes could be Visitor/Besucher OR Teacher/Lehrer).

    Regards
    Nik

  • Participant
    Level: Master
    Posts: 279
    NikB on July 4, 2019 at 7:10 am in reply to: BuddyPress Xprofile Member Type Field – Translation #23810

    Thank you so much Brajesh.

    > member types are not translatables(they are user categories and has user associations).

    I have to admit, this is the part that was troubling me too as it could have a knock on effect in all kinds of ways. I think I may suggest to the client that they keep the member types in just one language (and explain what they mean in other languages). Sometimes the simplest ways are the best 😉

    Regards
    Nik

  • Participant
    Level: Master
    Posts: 279
    NikB on May 22, 2019 at 11:42 am in reply to: Activation if already activated #23136

    Thank you as always Brajesh.

    And yes, if I understand you correctly, simply modifying the text on the activate.php to advise that if they have problems they may already be activated is probably a good (and the simplest!) solution.

    Interestingly, looking at the function bp_core_activate_signup, it LOOKS as if it should be checking and returning a different error if ‘The user is already active’ but it’s really not such a critical issue either way for me to try and figure out why that’s not triggering 😉

    Always appreciate your insight and many thanks again.
    Nikki

  • Participant
    Level: Master
    Posts: 279
    NikB on May 7, 2019 at 10:49 am in reply to: [Resolved] BuddyPress Custom Xprofile Fields – Datepicker #22857

    Hi Brajesh

    So sorry, I’ve investigated a bit more and I think it’s a theme-related issue as I was displaying a customised registration form via a shortcode on a page (which is a feature of the WPLMS theme).

    Showing the “standard” Buddypress register form works fine so it’s not a fault with your plug-in. I’ll play around with the theme a bit more or just create my own customisationsed register form without a shortcode if really necessary.

    Apologies for wasting your time and thank you for letting me know about the Buddypress datebox. It’s always surprised me that it works that way and I’ve always wondered if there’s something I’m missing so good know it’s not just me 😉

    Warm regards
    Nikki

  • Participant
    Level: Master
    Posts: 279
    NikB on May 1, 2019 at 2:31 pm in reply to: User Approval #22717

    Hi Brajesh

    Many thanks for getting back to me so promptly and if, as it seems, there is no other obvious/easy way of handling things, I think I’m inclined to agree with your suggestion.

    That said, I guess there would be no harm in disabling the initial email that gets set out from the Buddypress Registration Options plug-in (whilst keeping the activation email). I can probably work that out for myself although if you happen to know of an easy way… 😉

    Warm regards
    Nikki

  • Participant
    Level: Master
    Posts: 279
    NikB on February 12, 2019 at 7:23 pm in reply to: [Resolved] Mediapress Actions/Filters #20866

    Just to say I’ve fixed this by adding if ( did_action( 'bp_activity_after_save' ) === 1 ) though still no idea why it was saving twice 😉

    Either way… no further assistance required on this for now.

  • Participant
    Level: Master
    Posts: 279
    NikB on February 11, 2019 at 4:41 pm in reply to: [Resolved] Mediapress Actions/Filters #20831

    Hi Brajesh

    Unfortunately hooking to bp_activity_after_save is triggering twice and therefore I am getting duplicate emails sent out.

    Not very helpfully, I can’t post my code right now but if you have any suggestions as to what might be happening or a work around, I would be hugely grateful.

    Note: I’ve tested the entire code with a different hook (ie. wp_ulike_after_process) which I know only works once and it all works fine so I don’t think it’s the code itself that’s the issue, perhaps just the wrong hook…

    Warm regards
    Nikki