We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

eForm not quite working with PHx ???? ... [+name+] not working ...

    • 31039
    • 49 Posts
    unclespencer Reply #1, 15 years ago
    This is a strange one and its taken me quite some time to workout what is happening. Bascially I installed PHx and some time later i spotted an issue with email forms that were submitted. It wasn’t until much latter that i put the two events together.

    The forms would fill in and submit but the SUBJECT and FROM fields in the email that was sent out would be empty?

    [!eForm? &formid=`contactFormHelpDesk` &to=`[email protected]` &from=`[+email+]` &fromname=`[+name+]` &subject=`helpdesk request - [+name+]` &vericode=`1` &ccsender=`1` &debug=`0` &tpl=`contactFormHelpDesk` &report=`contactFormHelpDeskResults`  &format=`    name:Name:string:1,    phone:phone:string:0,    email:Email:email:1,    comments:Comments:string:0`  !]


    Ultimatly i worked out if i un checked "OnParseDocument" for the PHx component then the [+name+] variable would be correctly written.

    One other note the eform component was in a CHUNK.

    Has any one else had this issue using [+name+] type variables in chunks huh huh

    Many thanks spen grin
      • 16278
      • 928 Posts
      kp52 Reply #2, 15 years ago
      I hit this issue before, and found a reference to it somewhere in the forums. There is a clash with PHx, which you resolve by putting ((double parantheses)) in your snippet call instead of [+ +]. Try this:
      [!eForm? &formid=`contactFormHelpDesk` &to=`[email protected]` &from=`((email))` &fromname=`((name))` &subject=`helpdesk request - ((name))` &vericode=`1` &ccsender=`1` &debug=`0` &tpl=`contactFormHelpDesk` &report=`contactFormHelpDeskResults`  &format=`    name:Name:string:1,    phone:phone:string:0,    email:Email:email:1,    comments:Comments:string:0`  !]
      Somewhere in the snippet definition, you’ll find:
      // pixelchutes PHx workaround
foreach( $params as $key=>$val ) $params[ $key ] = str_replace( array('((','))'), array('[+','+]'), $val );
      which clarfiies what’s going on here (maybe).
      laugh KP
        • 33337
        • 3,975 Posts
        Zaigham (aka zi) Reply #3, 15 years ago
        Which version of eForm and MODx you are using?

        I see very old &format in your eForm call. tongue
          Zaigham R - MODX Professional | Skype | Email | Twitter

          Digging the interwebs for #MODX gems and bringing it to you. modx.link
          • 27330
          • 884 Posts
          sinbad Reply #4, 14 years, 10 months ago
          I’m with the same issue. using eform 1.4.4.5 and if I use [+name+] it comes blank. if I try the double (( I get ((name)) as sender.
          anyone have an idea?
            • 20413
            • 2,877 Posts
            mrhaw Reply #5, 14 years, 10 months ago
            There is this http://modxcms.com/forums/index.php/topic,33316.msg202684.html#msg202684
            if you guys don’t solve the issue of course.
              @hawproductions | http://mrhaw.com/

              Infograph: MODX Advanced Install in 7 steps:
              http://forums.modx.com/thread/96954/infograph-modx-advanced-install-in-7-steps

              Recap: Portland, OR (PDX) MODX CMS Meetup, Oct 6, 2015. US Bancorp Tower
              http://mrhaw.com/modx_portland_oregon_pdx_modx_cms_meetup_oct_2015_us_bancorp_tower
              • 27330
              • 884 Posts
              sinbad Reply #6, 14 years, 10 months ago
              still doesn’t work for me.
              what’s odd is that the &replyto gets the correct email the user has input but the &from &fromname are not. I’m getting ’name’ for the fromname and from field as my shared host email. even with bunk’s fix it ain’t working here. also using 1.4.4.5 and Evo RC1.00
                • 20413
                • 2,877 Posts
                mrhaw Reply #7, 14 years, 10 months ago
                Is this NEW fix better ---> http://modxcms.com/forums/index.php/topic,14306.msg226207.html#msg226207

                EDIT
                ...It was the same as mentioned above. tongue
                The old one started with: if (
                  @hawproductions | http://mrhaw.com/

                  Infograph: MODX Advanced Install in 7 steps:
                  http://forums.modx.com/thread/96954/infograph-modx-advanced-install-in-7-steps

                  Recap: Portland, OR (PDX) MODX CMS Meetup, Oct 6, 2015. US Bancorp Tower
                  http://mrhaw.com/modx_portland_oregon_pdx_modx_cms_meetup_oct_2015_us_bancorp_tower
                  • 28625
                  • 24 Posts
                  Stoffer Reply #8, 14 years, 10 months ago
                  Quote from: sinbad at Jul 14, 2009, 04:37 AM

                  still doesn’t work for me.
                  what’s odd is that the &replyto gets the correct email the user has input but the &from &fromname are not. I’m getting ’name’ for the fromname and from field as my shared host email. even with bunk’s fix it ain’t working here.
                  I have the same problem and am using eForm 1.4.4.6. At the end of the day it’s not a major issue as in the name appears in the body of the email. It’s just a little frustrating.
                  • pixelchutes Reply #9, 14 years, 10 months ago
                    With eForm 1.4.4.6 you should be able to use ((+placholder+)) opposed to [+placeholder+] in the eForm snippet call... with older versions of eForm, it’s a simple one-line fix to the eForm snippet using eForm PHx workaround.
                      Mike Reid - www.pixelchutes.com
                      MODx Ambassador / Contributor
                      [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
                      ________________________________
                      Where every pixel matters.
                      • 27330
                      • 884 Posts
                      sinbad Reply #10, 14 years, 10 months ago
                      updating to 1.4.4.6 fixed it for me. I wasn’t able to use ((+placeholder+)) but the old [+placeholder+] works now on my install.