Latest update throws NEW errors on previously-accepted configurations

  • Hello. Love this plugin .. used it successfully for many years.

    This latest update, however, is throwing errors on a few config entries that were otherwise previously working and without error. Fortunately for many of my websites, and despite the red, ominous errors, the configuration does properly save AND continues to work without issue.

    ISSUE# 1:

    Notwithstanding, I noted within this forum the “FROM” issue and have since adopted the suggested config to use: [your-name] <[email protected]> and set ADDITIONAL HEADERS as such: Reply-To: [your-email]

    However, I prefer to use the following as the TO config and this, too, is throwing an error now. While it seems to be working regardless, what is the issue with this advanced config?:
    [_raw_target-recipient] <[target-recipient]>

    To clarify, I am using _raw_ as defined on your Selectable Recipient advanced feature: https://contactform7.com/selectable-recipient-with-pipes/

    That feature auto-selects the first entry I configured. Hence, even if the patron does not change the selection, a proper value is still provided to your plugin upon submit.

    That being said, why is it throwing an error in design mode?

    ISSUE# 2:

    One other issue I noted was in regard to the “Sender’s message was sent successfully” config; I was using a <br /> and it was working properly. With this latest update, the break is throwing an error in config mode. Why was this ability removed? I understand about cleansing input fields .. but I was merely trying to format the plugin’s response that is shown after successful submission. Namely, I wanted to force a break in the message.

    I am certain these changes were made in everyone’s best interest. That said, perhaps a clear and visible warning on the update disclosure page was in order .. as this 2016-FEB update certainly has frustrated many admins.

    Per moderator request, this topic was moved from REVIEW to SUPPORT forum.

    https://www.ads-software.com/plugins/contact-form-7/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    What do you have in your Form tab?

    Thread Starter IRD-dev

    (@ird-dev)

    Hello. The issues still persist, on the latest version as of 29-MAR.

    In the Form tab, I have:

    <p>
    [text* your-name maxlength:40 placeholder default:user_display_name default:user_first_name "Your Name*"]
</p>

<p>
    [email* your-email maxlength:100 placeholder default:user_email "Email*"]
</p>

<p>
    [tel tel-828 maxlength:20 placeholder "Telephone +1 (xxx) xxx-xxxx"]
</p>

<p>Preferred Contact:<br />
    [radio radio-329 label_first use_label_element "Email:" "Telephone:"]
</p>

<p>
    [textarea* your-message x4 maxlength:250 placeholder "Message*"]
</p>

<p>How Did You Find Us:<br />
    [radio your-arrival label_first "Google/YouTube:" "LinkedIn:" "Facebook:" "Twitter:" "Other:"]
</p>

<p>Recipient:<br />
[select target-recipient "Sales/Marketing Team|[email protected]"
"Technical Support Team|[email protected]"
"Webmaster|[email protected]"
]</p>

<p>Please Verify:<br />
[recaptcha theme:light size:compact]
[submit "Send My Message"]
</p>
<p>[response]</p>
<p>Note: * entries are required.</p>

    In the Mail Tab, I have:

    TO: [_raw_target-recipient] <[target-recipient]>
    Error is shown in red: “This field has syntax errors.”

    FROM: [your-name] <[email protected]>
    Error is shown in red: “This email address does not belong to the same domain as the site.”

    I presume this is due to the fact that site is on a development URL whose domain name is not “MyDomain2.com” at this time. It will be, however, once live.

    As mentioned earlier, the form works perfectly, despite the errors.

    Thread Starter IRD-dev

    (@ird-dev)

    Hello Takayuki. Looking forward to your follow-up. I presume my settings are proper, unless you state otherwise.

    Plugin Author Takayuki Miyoshi

    (@takayukister)

    Make the “target-recipient” field required (select*).

    Thread Starter IRD-dev

    (@ird-dev)

    Hello. I can do that, albeit that is contradictory to design.

    That feature auto-selects the first entry, in the list of choices. Hence, even if the patron does not interact/change the selection, a proper value is still provided to your plugin upon submit.

    Perhaps it’s worth mentioning your suggestion in the FAQ, as that may help avoid confusion.

    Thread Starter IRD-dev

    (@ird-dev)

    OK, thank you – That change eliminated one of the two errors / warnings.

    Regarding the last remaining error/warning, as mentioned above:

    FROM: [your-name] <[email protected]>
    Error is shown in red: “This email address does not belong to the same domain as the site.”

    Please comnfirm this is a non-issue. I presume this is due to the fact that website is presently on a development URL whose domain name is not “MyDomain2.com” at this time. It will be, however, once live.

    Thread Starter IRD-dev

    (@ird-dev)

    Hello.
    I was hopeful that, after this website moved from development to live, the last remaining error/warning would be eliminated.

    However, despite that the site is now resolving at MyDomain2.com, the contact form is still throwing an error on FROM: [your-name] <[email protected]>

    Error is shown in red: “This email address does not belong to the same domain as the site.”

    Regardless, the form is functioning as expected.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Latest update throws NEW errors on previously-accepted configurations’ is closed to new replies.