Support/Comments for eForm

• • 
  • 1,024 Posts
  Frank Reply #241, 19 years, 6 months ago

  Quote from: pixelchutes at Mar 08, 2007, 10:53 AM

  
  Quote from: Frank at Mar 08, 2007, 10:48 AM

  
  I get the same error Could not instantiate mail function I saw on page 6.
  I did not find a solution anywhere.
  
  Here some details:
  PHP Version 4.4.2
  Apache/2.0.46 (Red Hat)
  safe_mode_allowed_env_vars PHP_ PHP_
  safe_mode_protected_env_vars LD_LIBRARY_PATH LD_LIBRARY_PATH
  eForm vers 1.4.1
  Modx 0.9.5
  ...
  
  Any suggestions?
  

  
  Well, unless you are tied to eForm 1.4.1, I might first suggest upgrading to newest version of eForm (1.4.3+), and then going from there...
  

  
  I get the error back when I delete the lines concerning department choice. How can I get rid of the option of a department choice?
• • 
  • 254 Posts
  kudolink Reply #242, 19 years, 6 months ago

  Is eForm compatible with 0.9.2.2?
  kudo
  www.kudolink.com - webdesign (surprised?)
  
  [img]http://www.kudolink.com/kudolinkcom.png[/img] [sup]proudly uses[/sup] [img]http://www.kudolink.com/modx.png[/img]
• • MODX Staff
  • 12,272 Posts
  Ryan Thrash Reply #243, 19 years, 6 months ago

  Should be.
  Ryan Thrash, MODX Co-Founder
  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
• • 
  • 1,611 Posts
  ZAP Reply #244, 19 years, 6 months ago

  A minor tweak request: Could you please add a variable for the eform directory as well as $snipPath (or instead of it)? I like to keep old versions of snippets around at times, as this allows me to develop and test the new without messing up the old. The way it is now I need to change the "eform" directory in three or four places (which is no big deal, but it could be easier).
  
  I actually think this would be another nice standardization of MODx snippets: $snippetBaseDir or something like that.
  "Things are not what they appear to be; nor are they otherwise." - Buddha
  
  "Well, gee, Buddha - that wasn't very helpful..." - ZAP
  
  Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
• • MODX Staff
  • 12,272 Posts
  Ryan Thrash Reply #245, 19 years, 6 months ago

  That’s a great idea Zap.
  Ryan Thrash, MODX Co-Founder
  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
• • 
  • 1,010 Posts
  TobyL Reply #246, 19 years, 6 months ago

  Quote from: ZAP at Mar 20, 2007, 02:41 PM

  
  A minor tweak request: Could you please add a variable for the eform directory as well as $snipPath (or instead of it)? I like to keep old versions of snippets around at times, as this allows me to develop and test the new without messing up the old. The way it is now I need to change the "eform" directory in three or four places (which is no big deal, but it could be easier).
  
  I actually think this would be another nice standardization of MODx snippets: $snippetBaseDir or something like that.
  

  
  Duly noted.. It’s on the to do list from now.
  eForm | eForm support | eForm @ wiki
• • MODX Staff
  • 12,272 Posts
  Ryan Thrash Reply #247, 19 years, 6 months ago

  Hey TobyL ... since you’re back in action, any ideas on when the next release/beta might be available?
  Ryan Thrash, MODX Co-Founder
  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
• • 
  • 1,611 Posts
  ZAP Reply #248, 19 years, 6 months ago

  I have been experimenting a bit with the latest eForm (1.43), and really appreciating some of the new features. I need to write some validation functions for things like credit card numbers, birth dates, etc. Seems as if perhaps there ought to be a subforum or thread here for people to contribute these so that others can make use of them and perhaps you can bundle some of them in later releases.
  
  I was a little confused by the way that the &requiredClass and &invalidClass parameters functioned. I would’ve expected the required class to be added to all required fields (whether they’ve been submitted or not, including before any submission) and the invalid class to be added to all fields with invalid input (including missing required fields). It seems that in actuality both of these classes are triggered only on error - the required class when a required field is missing, and the invalid class when a field doesn’t validate.
  
  The way that it works is fine; It just wasn’t what I expected. For example, I would’ve expected a required email field to have the required class all the time and the invalid class in addition if after submission the field was empty or didn’t validate as an email address. Since some other folks may be as obtuse as I am, you might want to explain how these work more in the documentation (feel free to point out where you already did if I’m just missing it).
  "Things are not what they appear to be; nor are they otherwise." - Buddha
  
  "Well, gee, Buddha - that wasn't very helpful..." - ZAP
  
  Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
• • ☆ A M B ☆
  • 1,056 Posts
  pixelchutes Reply #249, 19 years, 6 months ago

  Quote from: rthrash at Mar 20, 2007, 09:50 PM

  
  Hey TobyL ... since you’re back in action, any ideas on when the next release/beta might be available?
  

  
  TobyL, if you do make am interim release, can you PLEASE include the update with new Snippet TPL support? (already coded)
  I would really like to rid myself of my hacked eForms all over the place.
  
  Also, when are we going to get 1.43 in the MODx distro/SVN? Still shipping w/ 1.42......
  Mike Reid - www.pixelchutes.com
  MODx Ambassador / Contributor
  [Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
  ________________________________
  Where every pixel matters.
• • 
  • 1,611 Posts
  ZAP Reply #250, 19 years, 6 months ago

  Oh - one more easy request:
  
  It seems to me that there ought to be a parameter for &autosendername as well as &autosender. I set &from and &fromname to the email and name fields submitted in the form (so that the email received by the admins appears to come from that person and it’s easier to find in a crowded inbox). However when I do this &fromname is still used for the automessage, which is the name of the person receiving the automessage (not the sender).
  
  I made this work for me by adding this code at line 52 of the snippet:
  

  autosendername => isset($autosendername)? $autosendername:$fromname,

  
  and changing line 495 of eform.inc.php to this:
  

  $mail->FromName	= $autosendername;
  "Things are not what they appear to be; nor are they otherwise." - Buddha
  
  "Well, gee, Buddha - that wasn't very helpful..." - ZAP
  
  Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options

This discussion is closed to further replies. Keep calm and carry on.