nimrod54

Hi Guido,
thank’s for the fast reply.
I tested it with one of my sites and it works. I will check this also with another site where I use a different theme.
best regards

Hi,
as I mentioned, I had this site up only for testing and planned to delete it after the final release of WP 5 anyway. I sent you the info about this issue just for you to check if you had to update your plugin.
As said, I have the plugin installed on 3 other sites without any issue.
Thanks again for the nice plugin.
best regards

Hi guys,
thank you.
As written earlier, disabeling ‘Stop user enumeration’ resolved the issue
best regards

Hi,
unfortunately I’m an unexperiended WP user without a broad knowledgebase.

Hi,
I believe I found what has caused the issue. I disabled ‘Stop user enumeration’ and the problem disappeared

you’re welcome

no, I don’t run any caching.
I think the issue could be caused by using the plugin “WordPress Beta Tester”. Everything worked fine with the different WP 5 beta versions until I updated to the released WP 5.

Hi there,
here is what I found in the php-errors.log after activating the Happyforms plugin,
hope this helps

[09-Dec-2018 10:28:54 UTC] PHP Fatal error: Uncaught Error: Call to undefined function register_block_type() in /path/member5/wp-content/plugins/happyforms/inc/classes/class-block.php:62
Stack trace:
#0 /path/member5/wp-includes/class-wp-hook.php(286): HappyForms_Block->register(”)
#1 /path/member5/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#2 /path/member5/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#3 /path/member5/wp-settings.php(463): do_action(‘init’)
#4 /path/member5/wp-config.php(84): require_once(‘/…’)
#5 /path/member5/wp-load.php(37): require_once(‘/…’)
#6 /path/member5/wp-admin/admin.php(34): require_once(‘/…’)
#7 /path2/htd in /path/member5/wp-content/plugins/happyforms/inc/classes/class-block.php on line 62

if you need more info, just let me know.
Otherwise I will delete the website, I had it up for test only.

BTW, I use Happyforms plugin without any issue on 3 websites. All 3 sites are updated to WP 5.

best regards

Hi,
it works, thank you for your fast support.
Is there a way to add an empty line between the alphabet and the first name/term?

best regards

Hi Jeroen,

I would like to replace some of the words if possible. Main issue is the phrase “There are currently %d names in this directory” at the top of the list. I want to use the plugin for a glossary of terms, not listing of names. So I need to replace the text. Or could I uncheck a box to hide that line of text?

best regards

Hi Guido,
I am not allowed to make collection of name mandatory by judgement of courts. You will not find it written in laws.

@john
in Germany courts judgement in general is, you are allowed only to collect the email address if you want to send an email. I know it sounds strange, but that’s how judges rule here. If you make collection of name mandatory, someone like one of your competitors could activate legal assistance for cost-incurring warning. Cost-incurring warnings became pretty expensive over the past few years.
I assume it will be similar in other EU countries

Hi Guido,

thanks for the update and your hard work. Unfortunately in Germany you can’t make the collection of name mandatory and ask for consent.

Hi Guido,

I certainly understand. I assume that your VSCF will not be usable for companies in the EU as it is, after May 25.

Guido,

I believe a good source is https://gdpr-info.eu/
I believe double-opt-in is not mentioned there or in any legislation, but it is mandatory in Germany because of judgements of German courts.

Hi Guido,

I’m pretty sure Double-opt-in is not just to confirm an email address, main reason for douple-opt-in is to have him or her confirm you are allowed to send emails.
Sending a message via contact form is pretty much the same as signing up for a newsletter.
Also, with the new rules and regulations it is highly recommended to add a check box (which needs to be empty by default) in the contact form, to have him or her to confirm having read the privacy statement