Benjamin Pick

Constant __DIR__ is not defined in PHP 5.2 (thus, does not include admin css).

The newest version (v0.4) now allows to choose one form for this plugin.

You forgot the id:recipient part of the select box. I will make my extension throw a more visible error for this in the next version.

Thanks for including a concrete testcase.
However, it does work as intended in my test installation.
To make sure hyphen/slash is not the issue, would you test some name without them?

Thanks for your comment and your appreciation. Possibly I will implement it, whenever I come to it …
You mean, contact forms on different pages of your site?

Yes and no: it is fixed in the “nightly builds”-Version of it, so if you check this option it should be gone. But No, there has not been a bugfix release yet.
Alternatively, use my workaround above.

Oh, I see the issue is fixed there (#164 / rev1128). So the issue will disappear on the next release.

Oh, I’ve found a workaround: just put the following text into the “minimal word length”-option:

7, onerrorhandler: function() {}

Quite a hack, but it allows to add custom option (as the options are not validated/escaped). (Keeping the default of 6 does not work, though.)

The maintainer said at https://code.google.com/p/hyphenator/wiki/en_reportProblems:

> This sounds like a same-origin-policy issue. Do you have a link or test case where I can reproduce the problem?
> Some Error-logs could help, too…

For the wordpress extension, I’d suggest an option “surpress all error messages for non-logged-in users” (- happy to supply a patch if needed). In this way, at least the user doesn’t realize something went wrong.

(Just pass “onerrorhandler: function() {},” as an option to the Hyphenator object. Alternatively, allow “advanced options” to be set – see also patch at https://www.nomachetejuggling.com/2011/05/23/adding-dont-hyphenate-class-name-support-to-hyphenator/)

Strangely enough I can’t reproduce this issue. The pop-up correctly creates a link to “#Foretningsf%C3%B8rer” and the right recipient is selected.

Okay, after some debugging I realized that:
1) The reset event already is called
2) However, wpcf7 clears the form after resetting it, so that the changes made during the reset form are overwritten by clearForm
3) Thus, I’d suggest triggering the jQuery form handlers after clearing the form:

$(data.into).find('form').resetForm().clearForm().triggerHandler('reset');
(script.js:58)

(triggerHandler does not call the standard reset form event, but only those added via jquery’s bind. So standard functionality is not affected by this change, and the form isn’t reset twice.)

Would you please apply this patch? You could also trigger a custom event such as 'wpcf7_submit_success' or similar.

Did you enable it in the dashboard options at the top? For me it works fine in 3.3.1 .

[removed by author]

Wow, that was quick! ??
However, the preview of the “next scheduled GC” still shows the time given at “Clock” of the current day (even if it is already in the past) – independently of the interval chosen.

[removed by author]