Roy Orbitson

This plugin does not change how email is delivered. It uses the same core function of WordPress that everything else does. If you didn’t receive any email, you had something configured incorrectly.

Don’t mark this as resolved if you have no intention of doing so. Users deserve to know what they’re getting. The code on SVN still uses raw $_POST everywhere, and sanitize_text_field() on fields that have nothing to do with HTML.

I applaud your prompt response, but it’s still using sanitize_text_field() in several places it shouldn’t be, and using $_POST, directly, which should not be done in WordPress without stripping slashes.

Hire someone. It’s explained in this blog post, the form could have a checkbox set like this:

[checkbox* interests use_label_element "a|Subject A" "b|Subject B" "c|Subject C"]

Then something like this as the body of your custom plugin:

add_action(
    'wpcf7_before_send_mail',
    function($contact_form, &$abort, $submission) {
        $interests = (array) $submission->get_posted_data('interests');
        if (in_array('a', $interests))
            $submission->add_extra_attachments('path/to/info-a.pdf');
        ...
    },
    10,
    3,
);

Hi,

This plugin only creates the additional form parts for extra emails by duplicating what the original plugin uses in email (2). Since that does not have such conditional sending, nor do the extra ones. It’s not something I plan on building into this.

However, there is a filter called wpcf7_additional_mail in submission.php that can be used to inspect the current form submission and conditionally remove messages from that array.

The problem you’re describing isn’t necessarily a multiple emails issue. Wouldn’t it make more sense to send one email, but change its content and the set of attached files? That is also possible by using the filter/action hooks in CF7 and using add_extra_attachments().

Regards.

Have a read of Google’s consent docs. You could achieve this client-side (in the browser) by entering something like the following in the Preliminary JavaScript setting of this plugin:

gtag('consent', 'default', {
  'ad_storage': 'denied',
  'analytics_storage': 'denied'
});

Then have your consent management code (pop-up, etc.) change that default if allowed with JS like this:

gtag('consent', 'update', {
  'analytics_storage': 'granted'
});

Alternatively, your own code (in plugins/themes) can use hook into this plugin’s tiny_gtag_js_analytics_output filter to modify the pre_extra value in options array. By default, this holds that same Preliminary JavaScript setting as above, which you could modify or replace based on the visitors’ consent responses.

It’s not feasible for me to have comprehensive privacy defaults for different jurisdictions around the world, or to integrate with the countless consent management tools available. I’ve made this plugin extensible so site owners can easily use the standard API that Google’s gtag.js provides.

Oh, sorry about that. I added admin_url('upload.php') for the form action in my patched version and it works again. I used printf with esc_attr__() and esc_html__(), as it’s not advisable to pass raw HTML for translation.

Thanks but you missed a bunch of the fixes in that patch: moving the permission check to after page check (permissions are irrelevant if you’re on the wrong page, and they’re slower to check); you lost the href="#" on the close/cancel buttons that avoid a full page reload; and you still have the @media CSS that’s no longer needed because the popup markup is now outside the footer.

Any reason you excluded the other improvements? Did you have problems with the patch as it was?

Looks like this forum breaks data: URIs, but you can just add the scheme back to that link’s href to fix it.

I was completely wrong about the cause. The runtime correctly detects public path, but then Elementor overrides the with its own config. The config property can be corrected by attaching to the elementor/frontend/assets_url filter in PHP, but it’s up to the site owner to add plugin code to do this, so the default behaviour of Elementor is still broken. It does not supply a similar filter for its post.featuredImage property, so one has to add a (temporary) filter to post_thumbnail_url.

Or @mikeschroder?

Not a bad idea, I have seen other plugins do this. However, this is trivial to do yourself: create a plugin with only the following code, or add it to your theme’s functions file.

add_filter('tiny_gtag_js_analytics_output', function($options) {
    if (is_user_logged_in()) {
        $options['enabled'] = false;
    }
    return $options;
});

Yes, I see. Too much processing of those fields occurs before the wpcf7_mail_components hook. The downside of using only wpcf7_before_send_mail is that it fires before most additional mails get attached. You could process mail and messages properties as you do now, but also attach to wpcf7_additional_mail then process all the message arrays present in that filtered array, including mail_2. That should preserve your processing of all the properties you do now and offer attachment processing to the additional messages.

Do you agree that it makes sense to extend your conditional tag processing to all messages?

I used 8 for the priorities in mine so that the additional messages would be available to any other code that attaches with the default priority (10), but also to allow modification/removal at priority 9. You could increase your chances of catching all messages if you use a very late priority, like (PHP_INT_MAX - (PHP_INT_MAX % 2)) / 2.

You may need to consider writing custom code, e.g. your own plugin, as whether to send mail isn’t controlled by just deleting the To: address of an email. You should be removing unnecessary messages completely by attaching to that wpcf7_additional_mail hook.

https://www.ads-software.com/support/topic/alternative-hook-wpcf7_mail_components/