BuddyDev

Search

Replies

  • Participant
    Level: Enlightened
    Posts: 51
    Alex on in reply to: Multiline texfield has no limitation for characters #52816

    I switched the value field from longtext to varchar at the xprofile data field in MySQL. Then it cuts off everything which is longer than the given limit no matter JS is switched on or not.

    Is this the way to go? I mean you are more into buddypress than me. If this change leads to other problems than plz tell me.

  • Participant
    Level: Enlightened
    Posts: 51
    Alex on in reply to: Multiline texfield has no limitation for characters #52815

    Maybe we have a misunderstanding.
    Have a look at this:
    https://ibb.co/SrCSz5k

    In the buddypress core there are code to put out a shorter version of tinymce with less items at the toolbar.
    Check class-bp-xprofile-field-type-textarea.php
    Anyway, I could also use the wordpress bio field which is a multiline textfield only without the editor.

    Meanwhile I found a solution for the tinymce editor which is javascript driven unfortunately. This means a user can switch it off, then has the normal textfield back and can write thousands of words and crash the layout.

    So let me ask again, is there any PHP solution for this texfield (multi-line text box or bio textfield) to limit the characters which beeing saved?

    Regards Alex

  • Participant
    Level: Enlightened
    Posts: 51

    Any ideas to solve this issue? List all users but not in alphabetical order…

  • Participant
    Level: Enlightened
    Posts: 51
    Alex on in reply to: Question to the Buddypress Conditional logic Plugin #52327

    Sorry, to ask once more.
    No way to add some code wich is like “bypass submit for a field which is required and hidden”?

    I saw conditional logic like that at the register pages from Gravity forms which sync to Buddypress xfields but to get this plugin just for that feature is beyond my budget.

  • Participant
    Level: Enlightened
    Posts: 51

    Thanks for providing a workaround and letting me/us know that this i a WordPress issue.