Support/Comments for eForm

• • 
  • 29 Posts
  edmeehan Reply #211, 19 years, 7 months ago

  I updated the eForm to version .3 but I cant edit the snippet in the manager... it gives me an error.
  
  

  Not Acceptable
  An appropriate representation of the requested resource /manager/index.php could not be found on this server.
  
  Apache/1.3.36 Server at www.car256.com Port 80

  
  I am but a simple designer and this server stuff is killing me.... I just need something to work... any one know my problem or point me in the right direction.
  
  Ed
  -Ed
• • 
  • 1,010 Posts
  TobyL Reply #212, 19 years, 7 months ago

  Try the solution discussed here: http://modxcms.com/forums/index.php/topic,8957.msg62573.html#msg62573
  eForm | eForm support | eForm @ wiki
• • 
  • 29 Posts
  edmeehan Reply #213, 19 years, 7 months ago

  I fixed it.... since it won’t let me edit a snippet in the manager... I just had to login to mysql db and change it there. It works.. Thanks for the feedback
  
  Ed
  -Ed
• • ☆ A M B ☆
  • 24,524 Posts
  sottwell Reply #214, 19 years, 7 months ago

  Your server’s mod_security probably has hysterics over anything that looks like code to send email in the POST, and of course eForm is full of that (cc, bcc, etc), and the Manager is just a form that sends all its data via POST. So you won’t need to directly access the database for everything.
  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
• • 
  • 177 Posts
  seventhapex Reply #215, 19 years, 7 months ago

  is there a way to set the to address from within the form {{CHUNK}}? Something like a <select>?
• • 
  • 1,010 Posts
  TobyL Reply #216, 19 years, 7 months ago

  Yes, use the &mailselector parameter.
  
  From the eform documentation:
  
  

  &mailselector (Optional)
  Sets the name of the form field to use as a selector to select a single email from the comma (,) delimited emails assigned the &toparameter. This selector field will act like a numeric index to select an email. It will start at 1 for the first email and ends at N for the last email in the list.
  
  

  For example: &to =`[email protected],[email protected],[email protected]` &mailselector=`topic`
  eForm | eForm support | eForm @ wiki
• • 
  • 177 Posts
  seventhapex Reply #217, 19 years, 7 months ago

  thanks, I read through the documentation and wiki, I musta missed that.
• • 
  • 63 Posts
  padexx Reply #218, 19 years, 7 months ago

  Hi,
  
  I’ve updated to 1.4.3 and notized that &requiredClass and &invalidClass are not added to the captcha input box.
  
  Secondly:
  I am no css guru at all but individual styling of the required fields was not possible:
  
  ie:
  

  class="inputfield1 required" // snippet output
  
  .inputfield1 .required { ...} // css
  

  
  
  So I’ve changed in eform.inc.php:
  

  $fields[$n.'_class'] = $fields[$n.'_class']?$fields[$n.'_class'].' '. $class:$class;
  			$fields[$n.'_vClass'] = $fields[$n.'_vClass']?$fields[$n.'_vClass'].' '. $class:$class;

  
  to
  

  $fields[$n.'_class'] = $fields[$n.'_class']?$fields[$n.'_class'].'_'. $class:$class;
  			$fields[$n.'_vClass'] = $fields[$n.'_vClass']?$fields[$n.'_vClass'].'_'. $class:$class;

  
  
  Now the following works:
  

  class="inputfield1_required" //snippet output
  
  .inputfield1_required { ...} // css
  
• • 
  • 1,010 Posts
  TobyL Reply #219, 19 years, 7 months ago

  Hi,
  I’ve updated to 1.4.3 and notized that &requiredClass and &invalidClass are not added to the captcha input box.
  

  
  No, this is true. The vericode is not validated in the same way as other fields are. I’ve never considered it to be a problem but I’ll have a look at that for the future.
  
  

  
  Secondly:
  I am no css guru at all but individual styling of the required fields was not possible:
  

  Individual styling of required or invalid fields has not been the aim and it probably will not be in future versions either.
  
  The css
  .inputfield1 .required { ...} does not work because it is not valid css for <element class="inputfield1 required" />. It would be for <outerelement class="inputfield1"><element class="required" /></outerelement>
  
  You can change the code to suit your needs off course but the change you made here means that you are stuck with it. The existing method will no longer work (unless you have multiple copies of the snippet). That means creating individual classes for each and every field in all forms. I fail to see the sense in that for a generic solution as eForm is.
  eForm | eForm support | eForm @ wiki
• • 
  • 63 Posts
  padexx Reply #220, 19 years, 7 months ago

  I’ve never considered it to be a problem but I’ll have a look at that for the future.

  just wanted to mention it...
  
  

  I fail to see the sense in that for a generic solution as eForm is.

  I absolutely agree with that!
  
  The main reason for changing the code was that I wanted to (only!) give the inpuboxes a different background for the "required state"
  With just defining a .required {...} class the titles’ background would change, too.

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