Jose Mortellaro

Hi @vfsjason,

I will be happy to help you, however, we are not allowed to assist users in this forum when the issue is related to the PRO version.

I kindly ask you to open a support ticket at https://support.freesoul-deactivate-plugins.com/ or use the contact form at https://freesoul-deactivate-plugins.com/contact/, specifying the email associated with your PRO license.

Best regards

Jose

Hi James,

Unfortunately, FDP can’t replicate the function WC().

It looks like free-shipping-notification-woocommerce doesn’t check whether a function exists before using it.

If you have the PRO version of FDP, you can solve this using the Plugin Dependencies settings. You can read more details here:
https://freesoul-deactivate-plugins.com/how-deactivate-plugins-on-specific-pages/keeping-plugins-always-active-when-another-plugin-is-active/

If you only have the free version, I see three possible options:

1. Contact the authors of free-shipping-notification-woocommerce and report this issue. You could tell them that when using a function that isn’t defined in their code and isn’t a native PHP function, they should first check whether the function exists.
2. Carefully review your FDP settings. Try to identify where WooCommerce may be disabled while free-shipping-notification-woocommerce is still active. You mentioned that all plugins are enabled, but that might not actually be the case. To be sure, I suggest resetting the FDP settings.
   Be aware that you will lose all the FDP setttings.
   More details here:
   https://freesoul-deactivate-plugins.com/how-deactivate-plugins-on-specific-pages/reset-fdp-settings/
3. Wait until I test Relevanssi and Free Shipping Bar for WooCommerce in my testing installation. At the moment, I can’t say how long this will take.
   

Best regards

Jose

Hi James,

thank you for reporting this issue.

Relevanssi  doesn’t check if the function is_checkout exists before using it.
When a function is defined in another plugin you should always check if it exist before using that function. Unfortunately, some plugins don’t check it.

Probably, you deactivated WooCommerce somewhere, and those rules are applied also during the searching process. Maybe Relevanssi calls the homepage, or another URL where that plugin is disabled. I don’t know. I should investigate it deeper to find out the main cause of this issue.

Anyway, I suggest update Freesoul Deactivate Plugins to the latest version v. 2.6.2 and let me know if you still have the same issue.

Now FDP provides the function is_checkout when WooCommerce is disabled and you should not have any more the issue. But if you still ahve problems with version 2.6.2, don’t hesitate to reply.

Best regards

Jose

Hi @cutu234

thank you for sharing this very useful snippet.

Regarding the essential_form_settings filter, I would replace

return $translations[$lang] ?? $translations['de'];

with

$current_lang_settings = $translations[$lang] ?? $translations['de'];

 return array_merge($options, $current_lang_settings);

I would do that because if in a future version of the plugin the $options array has new keys, with array_merge you will not lose them. As you probably know array_merge preserves all the keys that aren’t in your custom code, while overriding only the specific ones you’ve provided.
With the current version of the plugin you don’t need array_merge, and probably you will never need it. This is just a caveat. But if the plugin’s core logic in the future introduces new keys to the $options array, your current code would overwrite everything and return an array with missing data.

Let’s say that using array_merge makes your code more future-proof.

I think the rest is perfect as it is. Thank you again for your snippet.

Have a great day!

Jose

Hi @loralora

You can check if the domain of the email exists with this custom code:

add_action( 'essential_form_before_sending', function( $name, $email, $message, $post_id ) {
    /*
    * Check if the email is valid and the domain exists
    */
    if ( ! is_email( $email ) ) {
        wp_die( 'Invalid email address.' );
    }

    $domain = substr( strrchr( $email, "@" ), 1 );

    if ( function_exists( 'checkdnsrr' ) ) {
        $valid = checkdnsrr( $domain, 'MX' );
    } elseif ( function_exists( 'dns_get_record' ) ) {
        $records = dns_get_record( $domain, DNS_MX );
        $valid = ! empty( $records );
    } else {
        $valid = true; // fallback: skip check
    }

    if ( ! $valid ) {
        wp_die( 'Email domain does not exist.' );
    }

}, 10, 4 );

If you add this code to the functions.php file of your child theme or to a functional plugin, it will run before the email is sent.

At least one of the functions checkdnsrr() or dns_get_record() must be available; otherwise, this code will not be able to check whether the email domain exists. On most servers, this should not be an issue, but if these functions are not available, you may need to enable DNS support in PHP on your server.

Please keep in mind that even if you check the existence of the domain:

• The email address itself might still not exist
• The inbox might not accept emails
• Only sending an email (or using a verification service) can truly confirm it

However, accepting only email addresses with a valid domain is already a good way to filter out many invalid emails.

This custom code is not implemented in the core of Essential Form because it slows down the sending process, as it requires a DNS lookup for each submitted email, which introduces an external network request and potential latency. However, if we receive more reports about the form sending a large number of spam emails, even if they are manually submitted, I will consider adding this check to the plugin core.

I hope it’s clear.

Have a great day!
Jose

You are welcome @codings !

Your settings will not be lost because there is nothing you need to configure. The plugin automatically adds the missing titles without you having to do anything.

There are no settings that will be lost because the settings don’t exist. It’s like worrying about losing your third arm. Sorry for the stupid example. It’s just to say that the sentence means that you can’t lose something that was never created in the first place.

When you deactivate the plugin, you don’t lose any work, because no permanent changes were ever made. You can’t lose something that doesn’t exist.

Of course, you lose the titles after deactivation. This is clear.

If you want the missing titles to appear again, simply reactivate the plugin.

In short:

• You activate the plugin → it automatically adds the missing titles to the content.
• You deactivate the plugin → it stops adding the missing titles, and everything returns to the way it was before activation.

In my opinion, after deactivating a plugin, you should have the same situation that was before activating that plugin. If you could still have the same functionality after plugin deactivation, it would be a nightmare when you decide to deactivate some plugins.

I hope it’s clearer now.

Best regards

Jose

Hi @carlodamo

add that line manually and that’s it.

The plugin is only for those users who have no FTP access for adding that line of code.

Best regards

Jose