Pierre_02

Hi Scott ?? !

Now that I found what was going wrong (my fault), I have no need to downgrade SS ?? !

Anyway, thanks for the quick support ?? !!

Amicably,

Pierre.

Hi Scott ?? !

Oups… Don’t lose your time with this one and forgive me :$… I’ had a look on my code and as I used an “old” child theme, I still call the spambot function in it, disturbing SS…

Resolved.

Thanks for your quick support Scott ?? !

Amicably,

Pierre.

Hi Scott,

same problem here. As I have problems with links containing email addresses, I wanted to switch back to 1.7.1 like thomasvaeth and get the same erro message ?? “An exception occurred: Column doesn’t exist for Simply_Static_Page.”
It seems that you’ve done some changes on the database structure, so any reversion is impossible :(…

TIA for help.

Amicably,

Pierre.

Hi Scott :).

No don’t change anything for the moment. I’ll investigate longer on that “problem” and let you know the issue in an longer using time ;).
Anyway, thanks for the ideas ;).

Amicably,

Pierre.

Hi Scott :).

1/ I didn’t set that by myself :). It’s an automated process executed during the adding of a domain in thecPanel. And as my host add automatically a special Let’s encrypt folder (for the certificate), I can’t “deploy” correct rights easily ;)…

2/ I didn’t know that. That’s a cool news ?? !

3/ Ah, ok. I, now, have understand :). I therefore continue to manually remove the emoji script and the wp-content/uploads folder ;).

Thanks Scott.

Amicably,

Pierre.

Hi Tauseef :).

I’ve just discovered that I’ve responses from you today, and I’ve answered to you ;).

Amicably,

Pierre.

Hi Tauseef :).

Ok, I understand better now. The email I use to ask for support or suggest features is pierre[at]tips02.fr

TIA.

Amicably,

Pierre.

Hi Alin ?? !

Happy to know that you’re aware of the problem, but sad to know that there’s no solution actually and that you’ll remove the geo chart while looking to find one.

Anyway, thanks for the quick response ;).

Amicably,

Pierre.

Hi Scott ?? !

You’re kidding ?? ! No need for apology here, I will be really happy when you have added this functionnality ?? !

TIA.

Amicably,

Pierre.

Hi Scott ?? !

The function I use to parse email addresses is in this thread :).
It search for email addresses in the content part (but I think you’ll have to adapt it to search everywhere) and call the native WP function antispambot for each address.

Happy to know that it will be implemented in a future release ?? !

Amicably,

Pierre.

Hi Steve :).

Ok thanks for the information and the quick support :)!

Amicably,

Pierre.

Hi Scott :).

Sorry I did not be clear enough… As I can’t use forms with static content, I use email addresses in my contact page as link like this: <a href="mailto:[email protected]">Contact me</a> but as I don’t want that spambots recovers easyly my emails addresses, I write a special function that parse the content and transform each email address it found by using the native WP function “antispambot”.
So, when SS parse my pages it see the email link that have been transformed by the native function of WP. An it is unable to realize that’s an email address, that the problem.
So I stop to use my function to protect links with “mailto” and everything is workin now.
What I ask to you is to do the job from the plugin. Exactly as I was doing it :).
So, as soon the plugin discover a link containing a “mailto” it call itself the native WP function “antispambot” and everybody will be happy, because emails addresses will be correctly protected :)!
As I said you in my last answer : Like, actually, we can’t use form (at least in an easy way), it will be a really cool feature to protect our email addresses ;).

I hope that this time I’ve been enough clear ;).

Amicably,

Pierre.

Hi Scott ?? !

Thanks here too for the quick answer ?? !! It’s seems that there’s a double problem, here :)…
SS mangle the HTML but my theme too (Divi) because they use a lot of shortcodes to “gnerate” the render of pages. So they have the same problem than SS when they parse that part of code.
I just write a ticket to their support to report the problem.

Anyway, a big thanks to resolve the problem from your part ?? !

Amicably,

Pierre.

Hi Scott,

thanks for the quick answer ?? ! I’ve found a quick and dirty trick to “protect” my file by setting its rights to 0444 :).
BTW, everything works fine :).

Amicably,

Pierre.

Hi Scott :).

Ok :(, I’ll tried to be patient :)…

Amicably,

Pierre.