We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 23510
    • 168 Posts
    Hi,

    I'm trying to find the code that is output by the [[+comments]] and [[+comments_form]] placeholders. Can anyone direct me to it please?

    I need to change the comments form so that the logged in user's email address is readonly in the form.

    Thanks.
    John

    This question has been answered by donshakespeare. See the first response.

    • discuss.answer
      • 42562
      • 1,145 Posts
      Why do you want to show users their email but disable them from changing it on the fly? You might as well use if statements to remove the field completely for logged in users since readonly fields can easily be altered client-side.

      Anyway this is what you are looking for:

      Go to your Articles container page --> Advanced Settings --> scroll down to Comments-->Display Reply [Form Chunk:]
      The default is something like quipAddComment
      Just change that default to your own.
      See http://rtfm.modx.com/extras/revo/quip/quip.quipreply/quip.quipreply.tpladdcomment

      Create a new Chunk with a name say, myQuipAddComment
      [[+preview]]
      <span class="quip-success" id="quip-success-[[+idprefix]]">[[+successMsg]]</span>
       
      <form id="quip-add-comment-[[+idprefix]]" action="[[+url]]#quip-comment-preview-box-[[+idprefix]]" method="post">
      <div class="quip-comment quip-add-comment">
          <input type="hidden" name="nospam" value="" />
          <input type="hidden" name="thread" value="[[+thread]]" />
          <input type="hidden" name="parent" value="[[+parent]]" />
          <input type="hidden" name="auth_nonce" value="[[+auth_nonce]]" />
          <input type="hidden" name="preview_mode" value="[[+preview_mode]]" />
       
           <div class="quip-fld">
              <label for="quip-comment-name-[[+idprefix]]">[[%quip.name? &namespace=`quip` &topic=`default`]]:<span class="quip-error">[[+error.name]]</span></label>
              <input type="text" name="name" id="quip-comment-name-[[+idprefix]]" value="[[+name]]" />
              <br />
          </div>
           
          <div class="quip-fld">
              <label for="quip-comment-email-[[+idprefix]]">[[%quip.email]]:<span class="quip-error">[[+error.email]]</span></label>
              <input readonly type="text" name="email" id="quip-comment-email-[[+idprefix]]" value="[[+email]]" />
              <br />
          </div>
           
          <div class="quip-fld">
              <label for="quip-comment-website-[[+idprefix]]">[[%quip.website]]:<span class="quip-error">[[+error.website]]</span></label>
              <input type="text" name="website" id="quip-comment-website-[[+idprefix]]" value="[[+website]]" />
              <br />
          </div>
       
          <div class="quip-fld">
              <label for="quip-comment-notify-[[+idprefix]]">[[%quip.notify_me]]:<span class="quip-error">[[+error.notify]]</span></label>
              <input type="checkbox" value="1" name="notify" id="quip-comment-notify-[[+idprefix]]" [[+notify:if=`[[+notify]]`:eq=`1`:then=`checked="checked"`]] />
              <br />
          </div>
       
          <div class="quip-fld recaptcha">
          [[+quip.recaptcha_html]]
          <span class="quip-error">[[+error.recaptcha]]</span>
          </div>
           
           
          <p><span class="quip-allowed-tags">[[%quip.allowed_tags? &tags=`[[++quip.allowed_tags:htmlent]]`]]</span>[[%quip.comment_add_new]]<span class="quip-error">[[+error.comment]]</span></p>
          <textarea name="comment" id="quip-comment-box-[[+idprefix]]" rows="5">[[+comment]]</textarea>
           
          <button type="submit" name="[[+preview_action]]" value="1">[[%quip.preview]]</button>
          [[+can_post:is=`1`:then=`<button type="submit" name="[[+post_action]]" value="1">[[%quip.post]]</button>`]]
           
          <br class="clear" />
      </div>
      </form>
        TinymceWrapper: Complete back/frontend content solution.
        Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
        5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
        • 23510
        • 168 Posts
        Thanks donshakespeare
          • 42562
          • 1,145 Posts
          You are welcome.
            TinymceWrapper: Complete back/frontend content solution.
            Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
            5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.