Support/Comments for eForm

☆ A M B ☆
1,056 Posts

pixelchutes Reply #41, 19 years, 11 months ago

Not sure why I am struggling so much with this...I have read the eForm docs, the 20+ page thread, as well as this thread...

As of writing this, I have the latest SVN build:
MODx version: 0.9.5 beta 5
Version codename rev 1714

Which lists eForm as v1.4 ...

I have 3 defined chunks, as defined on the examples page:
- eFeedBackForm
- eFeedbackReport
- eFeedBackThanks

This is the calling snipped code I am trying to test out:


[[eForm?
  &formid=`feedbackForm`
  &to=`[email protected]`
  &tpl=`eFeedBackForm`
  &report=`eFeedbackReport`
  &thankyou=`eFeedbackThanks`
  &mailselector=`department`
  &vericode=`1`
  &subject=`Web site feedback`
]]

What confuses me is why I do not see a form output?

If I output

{{eFeedBackForm}}

I see the form, but of course nothing happens.

How can I begin troubleshooting this? I need to first get a sample version of eForm working before I can make the call whether or not I can leverage it for my needs.

Am I missing something totally obvious that I could/should be considering? Where should I place the snippet code, where I want the form to show up I assume...

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.

MODX Staff
12,272 Posts

Ryan Thrash Reply #42, 19 years, 11 months ago

Put all the parameters on one line.

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

☆ A M B ☆
1,056 Posts

pixelchutes Reply #43, 19 years, 11 months ago

Quote from: rthrash at Oct 16, 2006, 05:18 PM

Put all the parameters on one line.

[[eForm? &formid=`feedbackForm` &to=`[email protected],[email protected],[email protected]` &tpl=`eFeedBackForm` &report=`eFeedbackReport` &thankyou=`eFeedbackThanks` &mailselector=`department` &vericode=`1` &subject=`Web site feedback` ]]

:( No luck.. This is so odd..I must be missing something. At first, I noticed FCK Editor was malforming my ampersands, but I turned off the RTE to confirm, so that’s not it either...hmmm...

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.

MODX Staff
12,272 Posts

Ryan Thrash Reply #44, 19 years, 11 months ago

And call uncached: [! !] vs. [[ ]]

Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

☆ A M B ☆
1,056 Posts

pixelchutes Reply #45, 19 years, 11 months ago

Quote from: rthrash at Oct 16, 2006, 05:26 PM

And call uncached: [! !] vs. [[ ]]

OK...calling uncached. I also ensured my CHUNK-names were case-sensitve-matched to the value in the snippet-call.

No luck. Btw, thank you so much RThrash for your willingness to assist. What else can we check? Everything else seems to be functioning just fine. This is a CLEAN install!

UPDATE(S):
- I have also tried updating eForm Back to v1.3 (including .php files, database defs, etc.) ! Still experiencing the same :/ ..odd thing is, I don’t even get an error?
- Toggling on/off the snippet-call I am able to see that at least One MySQL query is being ran, as the MySQL Requests total is reduced without the code present.

It’s most likely part of the MODx core to check for DB definitions, but could this be part of eForm, indicating it is at least trying to run?

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.

73 Posts

Cassiel Reply #46, 19 years, 11 months ago

Quote from: pixelchutes at Oct 16, 2006, 05:12 PM

I have 3 defined chunks, as defined on the examples page:
- eFeedBackForm
- eFeedbackReport
- eFeedBackThanks

This is the calling snipped code I am trying to test out:
[[eForm?
  &formid=`feedbackForm`
  &to=`[email protected]`
  &tpl=`eFeedBackForm`
  &report=`eFeedbackReport`
  &thankyou=`eFeedbackThanks`
  &mailselector=`department`
  &vericode=`1`
  &subject=`Web site feedback`
]]

dunno if this is relevant... you say that you have an ’eFeedBackThanks’ chunk, but you’re naming it ’eFeedbackThanks’ in the snippet call.

1,611 Posts

ZAP Reply #47, 19 years, 11 months ago

Quote from: Cassiel at Oct 16, 2006, 07:17 PM

dunno if this is relevant... you say that you have an ’eFeedBackThanks’ chunk, but you’re naming it ’eFeedbackThanks’ in the snippet call.

And a related and also possibly irrelevant question is whether your snippet is indeed called "eForm" (and not "eform" or "myEform" or whatever)...

"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

502 Posts

ajayre Reply #48, 19 years, 11 months ago

I’m running MODx rev 1732, with eForm 1.4 and I’m running into a problem. I have the chunks:

contactform
contactreport
contactthanks

Here is the contents of the contactform chunk:

<p><span style="color:#900;">[+validationmessage+]</span></p>
<form method="post" action="[~[*id*]~]">
  <input type="hidden" name="formid" value="contactusform" />
  <input type="text" name="email" eform="Email Address:email:1" />
  <input type="submit" name="submit" value="Send" />
</form>

Here is my snippet call:

[!eForm?&to=`[email protected]`&formid=`contactusform`&tpl=`contactform`&report=`contactreport`&thankyou=`contactthanks`&subject=`Web Contact Form`!]

and here is the output of the snippet:

Document or chunk not found for template id= ''

Any ideas?

Andy

☆ A M B ☆
1,056 Posts

pixelchutes Reply #49, 19 years, 11 months ago

Quote from: ZAP at Oct 16, 2006, 07:56 PM

Quote from: Cassiel at Oct 16, 2006, 07:17 PM

dunno if this is relevant... you say that you have an ’eFeedBackThanks’ chunk, but you’re naming it ’eFeedbackThanks’ in the snippet call.

And a related and also possibly irrelevant question is whether your snippet is indeed called "eForm" (and not "eform" or "myEform" or whatever)...

@Cassiel and @ZAP,

Quote from: pixelchutes

...I also ensured my CHUNK-names were case-sensitive-matched to the value in the snippet-call...

Yes, both are very good catches; however, I had already ran into similar issues and ensured that my snippet-name and chunk names were all properly referenced.

Isn’t this weird?

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.

☆ A M B ☆
1,056 Posts

pixelchutes Reply #50, 19 years, 11 months ago

Quote from: ajayre at Oct 17, 2006, 12:02 AM

I’m running MODx rev 1732, with eForm 1.4 and I’m running into a problem. I have the chunks:

contactform

contactreport

contactthanks

Here is the contents of the contactform chunk:
<p><span style="color:#900;">[+validationmessage+]</span></p>
<form method="post" action="[~[*id*]~]">
  <input type="hidden" name="formid" value="contactusform" />
  <input type="text" name="email" eform="Email Address:email:1" />
  <input type="submit" name="submit" value="Send" />
</form>

@ajayre--

One thing I read in the eForm 1.4 docs was this:

New: You can now use <form id="formName"...> to match your &formid=`formName` instead of <input type="hidden" name="formid" value="formName" />

Granted, this probably is not your issue, but at least could get you headed in the right direction? ...Spaces between params should not matter, should it?

Mike Reid - www.pixelchutes.com
MODx Ambassador / Contributor
[Module] MultiMedia Manager / [Module] SiteSearch / [Snippet] DocPassword / [Plugin] EditArea / We support FoxyCart
________________________________
Where every pixel matters.