We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 30223
    • 1,010 Posts
    Finally then,... here it is, eForm 1.4.4(beta) This is an imterim release with suggested changes and additions from the forums

    I’d like it to be tested before it goes into the repository so attached is a minimal zip file. No documentation update, just three core files.

    Installation instructions:
    1. Extract zipped files into assets/snippets/eform/ (replacing existing files, so backup if you need to)
    2. In the manager open the eForm snippet and replace content with eform.1.4.4.snippet.tpl
    3. Test, test, test
    4. Curse me, praise me or feed me back

    Changes in 1.4.4

    • Fixed various Select box inconsistencies
    • Adjusted email validation expression to allow + character.
    • Line breaks in ’Html’ fields will only be replaced in report template if &sendAsText false!
    • Line breaks in ’Html’ fields will be replaced in thankyou template when &sendAsText is true
    • removed double semicolon on line 201
    • Properly display session hash name in debug text for &protectsubmit code
    • properly escape regular expression in form parser
    • Fixed 0 (zero) values not being processed in form parser for validating selectboxes
    • Fixed ambiguous variable naming in validation code
    • Enhanced efLoadTemplate to also allow snippets as templates
    • &invalidClass now also works for vericode field
    • Added &autoSenderName parameter
    • Added &runSnippet parameter - expects a snippet name. Snippet will be run before any eForm handling. Any return value from the snippet is discarded. This can be used to insert functions as an alternative to declaring a separate snippet in the document. One parameter, the &formid will be passed to the snippet. Sadly eForm will silently ignore a snippet that does not exist due to the way $modx->runSnippet handles snippet return values.
    • Added $lang[’ef_mail_error’] to the language file and a slightly improved error reporting when sending mail fails (which just happened to me)

    Let me know if I’ve missed anything and enjoy breaking things smiley

    EDIT: Updated zip file to final version (complete with exception of language files - please grab it and post translations in this thread)

    Some additional changes:



    • Added &snipFolder parameter for those that want to keep different versions of eform in different folders.
    • Date formatting for report can now be set in language file: $_lang[’ef_date_format’]
    • Report output is now more locale aware as far as numbers are concerned. Added $_lang[’ef_thousands_separator’] to the language file. If set to an empty string (default) the character defined in the current (php) locale will be used (if any).

      • 25663 MODX Staff
      • 12,272 Posts
      Thanks Jelle. Looking forward to this going into 096 release. smiley
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 27376
        • 576 Posts
        Line 612 is missing ’$’ for the docText variable laugh
          • 30223
          • 1,010 Posts
          Finalized eForm 1.4.4. but before I put it in the repository I’d like the language files to be updated (or at least some). Grab the zip file from the first post and please post your translation here. (There’s only 1 - 3 lines to translate).


          There’s also a few extra changes in eForm, see the first post....
            • 33337
            • 3,975 Posts
            Great work Jelle!

            Keep up the great work! smiley
              Zaigham R - MODX Professional | Skype | Email | Twitter

              Digging the interwebs for #MODX gems and bringing it to you. modx.link
              • 23703
              • 180 Posts
              Well done Jelle!

              Here are the Swedish language files.
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                I’m getting two mailings when debug is on, one is as expected the other just has ’’ in the body.

                [!eForm? &formid=`ContactForm` &tpl=`ContactForm` &report=`ContactReport` &subject=`sottwell.com Contact` &thankyou=`ThankYou` &replyto=`email` &debug=`1`!]
                
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 23491 ☆ A M B ☆
                  • 1,056 Posts
                  Woo hoo! G R E A T news, Jelle! I am very excited to test it out!
                    Mike Reid - www.pixelchutes.com
                    MODx Ambassador / Contributor
                    [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
                    ________________________________
                    Where every pixel matters.
                    • 30223
                    • 1,010 Posts
                    Quote from: sottwell at Apr 07, 2007, 11:54 AM

                    I’m getting two mailings when debug is on, one is as expected the other just has ’’ in the body.

                    [!eForm? &formid=`ContactForm` &tpl=`ContactForm` &report=`ContactReport` &subject=`sottwell.com Contact` &thankyou=`ThankYou` &replyto=`email` &debug=`1`!]
                    


                    Susan, I don’t see any &to parameter. You shouldn’t get any mail at all smiley

                    Can you post the rest? I’d like to try to replicate this. With my test setup this doesn’t happen.
                      • 28042 ☆ A M B ☆
                      • 24,524 Posts
                      Thought it defaulted to [(emailsender)]?

                      You can take a look on my site; I’ve got debug turned on for demo purposes, and you can log in as the guest user and see everything.

                      Interesting... looking closely at the full headers, one is sent to the [(emailsender)] address, the empty one is sent to the user’s email address (I was using another of my addresses).

                      Even when I set the &to= parameter, it still sends the correct report to the &to address, and an empty report to the user’s email address.
                        Studying MODX in the desert - http://sottwell.com
                        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                        Join the Slack Community - http://modx.org