No longer simple and NAG ware

Try this in the MAIL tab:

FROM: [your-name] <[email protected]>
SUBJECT: Re: [your-subject]
ADDITIONAL HEADERS: Reply-To: [your-email]

How are they different from

[your-name]
[your-email]
[Telephone]
[EnquiryType]
[Enquirer]
[your-subject]
[your-message]

1. The issue is that the VALIDATOR is WRONG and badly written

2. It is nagging even when dismissed (protcol if to STOP PESTERING USERS when they click dismiss.

It is putting this nagware everywhere on every admin screen.

I am not going to do a workaround for BAD CODE

Just need to tell Author and they either fix it or lose customers

You can disable the configuration validator by adding:

define( 'WPCF7_VALIDATE_CONFIGURATION', false );

to your wp-config.php, or adding:

add_filter( 'wpcf7_validate_configuration', '__return_false' );

to your theme’s functions.php.

https://contactform7.com/configuration-validator-faq/

As I said “I am not going to do a workaround for BAD CODE

Just need to tell Author and they either fix it or lose customers “

If I was to hack the code as suggested I then need a change control document, this hack has to be documented, it has to be remembered for disaster recovery purposes.

No No No

The issue is that bad code has been produced.

A product that worked well for years has feature nobody needs or wants, there is no disable function and the product is acting like a troll in the back end.

Time to find alternative and to recommend alternative product

I can see you’re frustrated at the recent changes, but I’m not sure that you can fairly say the code is bad or that this is now nagware.

The code works exactly as planned, and therefore is good ?? What is bad for you is that you don’t like what the code does. That means you need to decide whether this plugin fulfills your personal needs and preferences, or as you say it’s time to move on to another plugin.

To be fair to the plugin author, all he has done with the validator is update the plugin so that users don’t fall foul of new ways in which mail is classified as spam, as sending a message which claim to be from a different domain to that which it is actually being sent from is a case where CF7 users can lose their mail to the spam folder. The issue is valid and well documented, and anecdotally I think we all have received spoofed mail (think of those message that claim to be from payapl.com, but are actually from a crook who is after your money). Mail providers are tightening their rules to address this phenomenon, and CF7 has merely taken steps to help the overwhelming majority of the users to easily ensure they comply with the current best practice.

The author has been fair in creating a filter to disable the validator for the minority who don’t choose to use the validator, and placing this in the functions.php file of your child theme with a clear label (/*this code does x y z*/) means that it will never be overwritten on theme update.

Finally, I don’t think it is correct to call the validator nagware, which typically means “a type of shareware that persistently reminds (nags) the user to register it by paying a fee, where the intent is generally that the user will register or buy the program to get rid of the trial version’s annoyance” 1. The author does not benefit in any way from this reminder in the admin section, and rather than ask for a donation/like/review/upgrade, the reminder is purely for the user to prevent their mails from falling into the spam folder.

I’m fine with the new feature (as you can tell), and feel that the filters plugin authors include are exactly for this use case where you prefer to tailor the plugin to your particular preferences. This helps us to avoid throwing the baby out with the bathwater, so to speak.

BW

EDITED

tI disagree

The code IS bad because it does not work as stated in my original post so it is not fit for purpose.

The code IS bad because it does not offer an option within the plugin to disable the feature and this requires a hack of code which is bad practice just to get a plugin to work because it has all kinds of issues with change control and disaster recovery.

It can and IS nagwaare, it nags the user for every screen that loads even after the user has clicked on the DISMISS. It is annoying to the extreme and reason in iteelf to DUMP CONTACT7.

Your assertion that nagware is shareware is nonsense, just because shareware can nag does not mean all nagging comes from shareware.

It is the action of nagging that defines it as nagware.

IOS updates are nagware, I have one on my iphone nagging me every day to update but I also have warnings online that the update will turn my iphone into a brick.

Still at least it is once a day not every time I do anything on my iphone which is what this stupid plugin is doing.

Yes I am Frustrated, because I liked this plugin and now they have done this bad development and are not even responding to the query themselves.

If they do not monitor these support threads then again a bad sign.

Takayuki Miyoshi, the plugin author answers plenty of questions every day in this forum and I’m sure is well aware of comments like yours – they’ve been made a number of times. Whether he agrees with your comment is an entirely different manner.