[diegocanal]

Hi Ally,

As always, you go beyond your duty and limits to provide us with the best possible support.

Thank you!

Regards
Diego

[diegocanal]

@katw regarding:

(…)but wouldn’t a public GitHub vocabulary list become less than effective when SPAMMERs read the words we are blacklistin(…)

I have managed many sites for many years and this blacklist has proven to be pretty effective. Take into account that:

• It is regularly updated so spammers would have to keep an eye on it constantly
• It is not easy for a spammer to avoid the patterns as they cover a lot of ground
• You can combine it with your own set of keywords, phrases and patterns

It is true that heuristic filtering, (e.g. bayesian) it is the ideal solution in terms of effectiveness. I have tried some plugins that employ it but they come with drawbacks that have finally made me choose this simpler solution as, at least for the sites I’ve managed so far, it’s been more than enough.

[diegocanal]

@katw, regarding:

(…)“A useful word list” would be a great help for many of us.(…)

I suggest everybody to use the Comment Blacklist for WordPress at GitHub managed by Grant Hutchinson. Just pay attention in case you are in a rare niche that needs some of the keywords, phrases or patterns to be removed, otherwise this list is pretty universal.

Even there are some plugins in the WordPress repository that fetch the data from that list, e.g. Comment Blacklist Manager By Andrew Norcross that automatically feeds the Comment Blacklist that is used by the WordPress built-in feature.

Regards
Diego

[diegocanal]

Hi

Thanks Ally for adding the suggestion to your development list. In the meantime, would it be too much to ask you for the piece of custom code that would do the trick? 🙂

Regards
Diego

[diegocanal]

Hi Ally

Does Quform supports the WordPress built-in feature Comment Blacklist?

That would be great as I believe that in most cases users would be willing to use the same blacklist for both, the WP comments form and the other forms built with Quform.

Regards
Diego

• This reply was modified 7 years, 2 months ago by diegocanal.
• This reply was modified 7 years, 2 months ago by diegocanal.

[diegocanal]

Hi Ally

That’s great!

I’ve been playing with the demo and I must say that it looks fantastic!

I wish you the best with this new version. Long life to Quform!

Regards
Diego

[diegocanal]

Hi Ally

I’ve just seen you have recently released version 2. I am so happy that the plugin is moving on! I am looking forward to give it a try.

I was wondering if this new version offers the possibility to use the WordPress API (wp_mail) to send mail (instead of mail() or the SMTP option).

Thanks!

Regards
Diego

[diegocanal]

I got it, thanks Ally!

[diegocanal]

Hi Ally,

I sent you the purchase code 4 days ago but I have not received the download link yet.

Thanks!

Regards
Diego

[diegocanal]

Hi Ally

Thanks a lot for your help, you’re very kind.

Regards
Diego

[diegocanal]

Hi Ally,

Fair enough, thank you for your thorough explanation.

Regards
Diego

[diegocanal]

Hi Ally,

I have tried editing in the /includes/elements directory the files text.php, textarea.php and select.php, adding something like this: if ($this->getRequired())…but did not succeed. Would you be so kind as to point me in the right direction?

Thanks!

Regards
Diego

[diegocanal]

Thanks Ally!

Regards
Diego

[diegocanal]

Hi Ally,

Thank you for taking the trouble to help me on this. I do appreciate it.

As I was expecting, both, the plugin and the edit of form-builder.php worked perfectly.

Thank you!

Regards
Diego

[diegocanal]

Hi Ally,

Thanks for taking this into consideration.

I am not an expert on accesibility matters but I think one way to go for Date and Time would be to add new labels –with heir corresponding for attributes– one for each single menu (day, month, year, hour, minutes, am/pm) positioning them off-screen –as using display: none or/and visibility: hidden; would hide them from the screen readers too– that could be achieved styling them as follows:

.hidden_labels {
    position:absolute;
    left:-10000px;
    top:auto;
    width:1px;
    height:1px;
    overflow:hidden;
}

Of course there could be an option to turn the visibility of those labels on and off in case the user wants to show them, but perhaps that would be too much extra work as they would have to be acommodated between the current main labels (e.g. “Date of arrival” or “Start time”) and the single menus, for those labels (the main ones) we could add the aria-labelledby attribute in each single menu (input/select).

References:

• Creating Accessible Forms • Advanced Form Labeling
• Invisible Content Just for Screen Reader Users

Regarding the reCAPTCHA, you are right, sorry I had not realized when I posted that it does not have a visible input with id.

Regards,
Diego

• This reply was modified 8 years, 8 months ago by diegocanal.

[Author]

Posts