WP-Henne

Hello @forinn

Yes, everything is well done and you did all correctly.

If you look at source code of the page (Mac: Option+Command+U or PC: Ctrl + U) but may be you are on that way ??

Only the plugin author or you as the thread starter can set Resolved. You can do this when replying below the form.
I am only a “power user” of the plugin ??

Have nice day!

Hello @forinn

I looked at the theme because I suspected… that the input field for the phone number is “cleaned” there so that only phone numbers and + remain – because it is a phone number area.
So it is not possible to execute shortcodes there. Whether the theme developer will support something … or a hook… I don’t think so.

In a similar scenario, I have solved this with an additional plugin, which works like a “search and replace” and works virtually after all plugins before the actual output of the website (possibly in a cache).

Just tested, you can use it!

• Install https://www.ads-software.com/plugins/real-time-find-and-replace/ and activate this
• Enter e.g. 12345678 in the Tel field of the theme builder
• go to the settings of “Real-Time Find and Replace” use 12345678 as “Find:”
• go to https://www.pinnacledisplays.com/unicode-converter.htm of your phone number and copy everything from the output box.
• set this to “Replace with” in “Real-Time Find and Replace”
• Save and go to the page in the frontend. The phone should be displayed correctly and be clickable.
• Look in the source code and you will only see the Unicode sequence (search for <i class=”fas fa-phone )

Cheers!

Hello @forinn

Please check the source code of the page. You will see inside the <div class=”topbar”> … <div> correct emcoded email (search for *protected email*)
But you should change the tags while using phone number. You should use any other than the phone outside the Shortcode from Email-Encoder to display the phone-icon.

If all is correct, you will see the green lock twice and at source code no phone number.

Regards
wp-henne

Hello @nims

I have created several forums based on GeneratePress.
https://de.www.ads-software.com/themes/generatepress/
The free version is perfectly fine.
Some corrections that are not available in the free version I have solved with CSS.

You can also try: The Minimal
https://www.ads-software.com/themes/the-minimal/

Cheers!

Hello?@ironikus!

I confirm that with update 2.2.2 the issue mentioned here is resolved and everything works as expected!

Thank You!

Hello @gwin

Thank You so much!

Have a nice day

Hello @ironikus!
You are so great!

I am patient and happy.
Have a good time!

Hello @berjanschroer95

plz check with developer tools. There are a lot of ! and I assume that another plugin or the theme is causing a problem.

@threeatetwo

Nope! 2.4.6 works here perfectly!

I think there is only a temporal context, but also there it will cause another plugin

Cheers!

Hi @ferda2!

I have been using the plugin for a few years now and in that time I have written around 5,500 IP unique addresses to a central database via 65 websites. Each day 5-15 are added. I would therefore assume that scripts programmed in this way do not exist.
If you want to be sure, the PRO version of the plugin offers the option to customize the link… then it would be a unique link for you and nothing can be recognized/bypassed by script.

My pure PHP installations (Jeff offers here: https://perishablepress.com/blackhole-bad-bots/ have a different link trap, even that is sometimes very popular – For example, the identical bot from a different IP.).

Please give details about the log entries in BBQ – because these are definitely accesses to REST or login etc. because BB cannot intercept this. Because Blackhole for Bad Bots can’t intercept that. I am currently familiarizing myself with BBQ. But you’d better use a thread there: https://www.ads-software.com/support/plugin/block-bad-queries/

Cheers!

Hello @voidzero,

You can! Use this inside the []

do_shortcode="yes"

Look here for further info:
https://www.ads-software.com/support/topic/encoding-cf7-shortcode/

Cheers!

Hello @robins9845,

You can increase the basic security of your form(s) by putting them in an encoder.
I initiated this extension (execute shortcodes in the encoder https://www.ads-software.com/support/topic/encoding-cf7-shortcode/ ) at the time and have been using it on all websites ever since. For contact forms as well as for logins or even entire forums.
Feel free to try it out.

1) https://www.ads-software.com/plugins/email-encoder-bundle/

[eeb_protect_content protection_text="Please activate javascript to see the protected form." method="rot13" do_shortcode="yes"]
[your-CF7-shortcode]
[/eeb_protect_content]

Change [your-CF7-shortcode] to Yours!

It is not a fix for the named bug, but at least it is no longer possible for scripts to fire your form. It requires real browser access, which at least significantly reduces the number of possible attackers.
If you also use the bad bot plugin, for example, dubious bots will also be blocked…

2) https://www.ads-software.com/plugins/blackhole-bad-bots/

cheers!

This is what I was originally looking for. https://www.ads-software.com/support/topic/add-filter-to-ignore-certain-emails-2/

Well, then all things are in order ??

Here is my pragmatic solution in a snipet.

An SQL delete is triggered each time the user logs in to the backend (no user level is taken into account).
The easiest way to do this is via
https://www.ads-software.com/plugins/code-snippets/.

add_action( 'wp_login', 'remove_wpml_mails', 16 );

function remove_wpml_mails()
{
    global $wpdb;
    $prefix = $wpdb->base_prefix;	
    $table = $prefix . 'wpml_mails';
    # address to remove from logfile
    $mail = "[email protected]";
	
    try {
        $wpdb->delete( $table, array( 'receiver' => $mail ) );
        return true;
    } catch (Exception $e) {
        return 'Error! '. $wpdb->last_error;
    }
}

Hello @dpinson,

Many thanks for your efforts.
I agree that it is a little complex. I am therefore pleased to have made a suggestion for a future version.
For the moment, I am trying to remove the entries from the database using my own script. This can then be done via cron and is certainly a solution for now.
I could post this here if it would be ok. Just need a few days to test it.
Thanks again & regards!

Yes, this is the real hint!

While we only need to confirm … not to disable. If we are using other plugins…