Support Forum ยป User Profile

Forum Replies Created

Viewing 15 posts - 61 through 75 (of 95 total)
  • Author
    Posts
  • in reply to: โœ…Taxonomy Advanced - Add New = True #44762
    CodogCodog
    Participant

    Hi Peter,
    yup that was it! Subscribers cannot "add new" tags. Be great if this was a feature available to this role in MB Frontend submissions in the future. Thanks for clarifying ๐Ÿ™‚

    in reply to: โœ…Taxonomy Advanced - Add New = True #44750
    CodogCodog
    Participant

    Hi Peter,
    thanks for getting back to me. I see no console errors?

    I have also just tried creating a very basic 'taxonomy' custom field with no advanced options and including 'add_new' => true I get nothing? No option to add a custom tag? I have also tested with all the different field_type (IE: select, select_advanced, select_tree, checkbox_list etc etc...) and the result is the same?

    Can you verify that this feature is working as expected at your end? Using MB V5.9.4 and AIO V1.24.2.

    If yes can you show me a demo/screenshot of what I should be seeing?

    Q) Can I also assume that tags can be added in both the wp-admin by an 'Administrator' and in a Frontend form by a 'User' with 'add_new' => true?

    Thanks ๐Ÿ™‚

    in reply to: โœ…File Upload - Binding Events - Multiple data-uploader's #44645
    CodogCodog
    Participant

    Thanks Peter,
    thats great!

    in reply to: โœ…Hide Field On Specific MB Frontend Page Template #44447
    CodogCodog
    Participant

    Hi Peter,
    understood. Thanks!

    in reply to: โœ…Hide Field On Specific MB Frontend Page Template #44425
    CodogCodog
    Participant

    Hi Peter,
    not sure what you mean by ..."create another select field with the ID page_template to use the conditional logic in the frontend"....

    Can you elaborate or show me an example of how to achieve my goal with your described method?

    Thanks in advance!

    in reply to: โœ…file_upload field - Return "large" image size #44405
    CodogCodog
    Participant

    Ok understood.

    Thanks Peter.

    CodogCodog
    Participant

    Hi Peter,
    no probs... hacky... but works. Yeah, be nice to see this added as a feature to the validation methods.

    Cheers ๐Ÿ™‚

    CodogCodog
    Participant

    Hi Peter,
    perfect!

    Thank you ๐Ÿ™‚

    CodogCodog
    Participant

    Hi Peter,
    so I did! But I didn't follow up on that implementation in the end. After looking at the links you provided it's still not 100% clear on how to use rwmb_the_value to show the output of the file_upload custom field as an admin column. It would be very helpful if you could you post a basic example?

    Many Thanks ๐Ÿ™‚

    CodogCodog
    Participant

    ..... sorry forgot to close the code block. For clarity....

    add_action( 'init', 'prefix_add_profile_columns', 20 );
    function prefix_add_profile_columns() {
        class Prefix_Custom_Profile_Columns extends \MBAC\Post {
            public function columns( $columns ) {
                $columns  = parent::columns( $columns );
                $position = 'before';
                $target   = 'username';
                $this->add( $columns, 'profile_picture', 'Profile Picture', $position, $target );
                // Add more if you want
                return $columns;
            }
            public function show( $column, $post_id ) {
                switch ( $column ) {
                    case 'profile_picture':
                          // My My image query to go here.
                        break;
                }
            }
        }
        
        new Prefix_Custom_Profile_Columns( 'user', array() );
    }
    CodogCodog
    Participant

    Hi Peter,
    thanks for clarifying. So I can see that when activating the text tab via the WYSIWYG options[] setting 'quicktags' => true that indeed the field is scrolled to when empty.

    The problem is that I DO NOT want my users to use the "text" tab as arbitrary HTML can be added here?

    A Hack (for anyone else using WYSIWYG Custom Field with NO TEXT TAB ONLY)
    ==========================================================================

    It is possible to trick scroll to validate field on the WYSIWYG.... it's a hack! But tested and works.

    In your SAAS add the following:

    .rwmb-input{
        .wp-editor-container{
          iframe{
            // Set to your preferred height
            min-height:200px;
          }
          textarea{
            &.rwmb-wysiwyg-required{
              display: block !important;
              height: 0px !important;
              padding:0;
              border:none;
          }
        }
      }

    What this does is force the <textarea> (the bit the validation needs to scroll up to) to be displayed but be visually hidden.

    CodogCodog
    Participant

    Hi peter,
    When you say....

    For the WYSIWYG field, the input field textarea will display if you switch to tab Text and you can see the browser scrolling to the field as well.

    Q) Are you suggesting I switch to using a 'textarea' or 'text' custom field type instead of the 'wysiwyg'? Because this allows for the scrolling to the field on error?

    Although I appreciate switching field type will fix the scrolling issue you are effectively asking me to reduce the functionality I wish to provide to my users? I need the WYSIWYG to allow my users to format their posts?

    Have I understood you correctly?

    CodogCodog
    Participant

    Ok, thanks for the info Peter ๐Ÿ™‚

    CodogCodog
    Participant

    Thanks Peter ๐Ÿ™‚

    CodogCodog
    Participant

    Hi Peter,
    thanks for your response.

    It would be really great to have the option to turn off the confirmation password - In UXD forcing users to confirm their password has been known to reduce registration conversion rates significantly!

    Could this be considered as a future improvement?

    Thanks ๐Ÿ™‚

Viewing 15 posts - 61 through 75 (of 95 total)