Developer
Supported
ProForm Drag and Drop Form Builder
Back to this add-on's main page
View Other Add-ons From Isaac Raway
[Resolved] problem after updating
Support (Resolved)
|
dvn
|
| Posted: 21 April 2012 11:07 AM |
|
|
|
|
downloaded ProForm earlier this week and installed, all was well except notification templates weren’t rendering. saw the support post here and downloaded 1.05. updated, and my notifications are now rendering but I get the following php error after submitting the form.
Message: Cannot modify header information - headers already sent by (output started at /Applications/MAMP/htdocs/voltavolare/admin/expressionengine/third_party/proform/libraries/proform_notifications.php:257)
Filename: libraries/Functions.php
Line Number: 393
|
|
|
|
|
airways
|
| Posted: 21 April 2012 11:53 AM |
# 1
|
|
|
Developer
|
You probably just need to remove the debug=“yes” parameter from your template tags. This causes additional debug output to be provided - which is printed on the line noted in the error message you provided.
Can you prove the template code you are using which causes this?
It will also be helpful to know what version of PHP and ExpressionEngine you are using.
|
|
|
|
|
airways
|
| Posted: 21 April 2012 12:43 PM |
# 2
|
|
|
Developer
|
Okay I believe I have determined what the issue was that caused this. My test environments seem to have fairly high output buffering which allowed the user of a header after output - ordinarily this would stop the output with a fairly unfriendly message, which you’ve encountered. Most other users seem to have similarly high buffering settings since I haven’t gotten a report of this yet.
Removing debug=“yes” should definitely solve this issue for you.
Since I don’t really like relying on this buffering behavior, I’ve also uploaded a new build, 1.07, which will explicitly exit after printing debug output and will print a more friendly message that indicates that you should turn off debug=“yes” if you wish to run the form normally.
|
|
|
|
|
dvn
|
| Posted: 21 April 2012 01:10 PM |
# 3
|
|
|
|
thanks, I’ll download 1.07 and give it a shot. fyi, I wasn’t getting any kind of debug message previously, even with debug on.
|
|
|
|
|
dvn
|
| Posted: 21 April 2012 01:32 PM |
# 4
|
|
|
|
and thanks for your quick reply on a saturday morning! we’ve just launched a new site for a small airplane manufacturer and they’re getting a high degree of interest. the main channel right now for that interest is through a couple web forms, so this is a vital function for them.
|
|
|
|
|
dvn
|
| Posted: 21 April 2012 01:57 PM |
# 5
|
|
|
|
yeah, something’s still up and I’m getting the debug notice below.
as I said, I wasn’t getting a debug notice at all in the previous version, even with debug on. I’ve turned debug off now, so my config looks like this.
$config[‘debug’] = “0”;
$config[‘template_debugging’] = ‘n’;
———
Debug Output
Notifications exist for contact
Final notification list Array ( [0] => daven@ricochetpartners.com )
Sending admin notifications - result so far yes
Notifications
Template group ID: 2
Template saved as file /Applications/MAMP/htdocs/voltavolare/templates/default_site/Notifications.group/Contact.html
Template: Someone submitted the {form_name} form: {fields} {field_label}: {field_value}<br> {/fields}
Someone submitted the {form_name} form: {fields} {field_label}: {field_value}<br> {/fields}
submitter_notification off
share_notification off
Final result yes
Processing stopped to review debug output - remove the debug=“yes” parameter from your tag if you do not wish to see this message any more.
——-
and here’s my stock notification template:
<p>Someone submitted the {form_name} form:</p> {fields} <b>{field_label}</b>: {field_value}<br/> {/fields}
|
|
|
|
|
airways
|
| Posted: 21 April 2012 02:04 PM |
# 6
|
|
|
Developer
|
Yes, the version that you were using previously did not correctly print the entirety of the debug output without some other switches set elsewhere in the code, but it did attempt to do so - which caused the output to be flushed and prevented the redirect header from being used.
The new version forces the output to be flushed, and exits, so that you can view it (if needed) and also so you know to remove the debug parameter.
I may have been a bit unclear, sorry about that, the debug parmeter is part of your form template (you do not need to change anything in config.php or in your notification template). The sample templates in previous versions incorrectly included this parameter:
{exp:proform:form form="something" ... debug="yes" ...} {/exp:proform:form}
You need to remove the debug=“yes” part from your form tag in order to stop the debug output from being printed.
|
|
|
|
|
airways
|
| Posted: 21 April 2012 04:57 PM |
# 7
|
|
|
Developer
|
Hi dvn,
Just checking - were you able to resolve your issue by removing the debug parameter?
|
|
|
|
|
dvn
|
| Posted: 23 April 2012 11:27 PM |
# 8
|
|
|
|
yes I was, thank you!
|
|
|
|
|
airways
|
| Posted: 24 April 2012 08:57 AM |
# 9
|
|
|
Developer
|
No problem, please post again if you have any questions!
|
|
|
|