woof

Okay, now there is something in the docs, will try to use it this weekend. Thanks.

https://wpforms.com/developers/wpforms_emails_notifications_message/

Most urgent would be the know how of the newly added filter usage. Please update/add the documentation (or tell me in here first).

Just to explain my situation and my point of view: I’ve chosen WPForms because of some specific functionality I need (“double opt in”, also for legal reasons) I thought I can realize with what this plugin offers in available API documentation. I don’t think reverse engineering or hacking would be a good choice (I don’t see myself being able to do also), I wanted to rely on official documented functionality. Hoping this would not change without further notice. The typical way to replace some functionality would have been adding the new, documenting it, marking the old as deprecated, documenting it, leaving the old for a while and then remove it (and documenting that).

Now my fear is that the intention on your side is not to replace something with something else, better – but to remove it from documented API so it is no longer available for users? For “lite” users only?

Thank you for investigating.

Why why why? Without notice in change log (or what do I miss?) and without updated documentation (404)?

Yes, a filter with this name is called, but it seems not to be just a renaming but also has changed API. This is very very very annoying.

Could you please provide further information how this filter can be used?

• This reply was modified 1 year, 2 months ago by woof.

Looks like the CSS file that comes with this plugin uses very generic class names like “menu” with no additional restriction (like all “menu” elements within calendar code). Which I think is a warning sign of poor code quality.

Also you should not modify files within plugin or theme directories other than your own (like child themes). Every plugin/theme update will overwrite your changes with no warning, they will be lost.

If you nevertheless want to, you could edit every rule to make selector more specific, so for instance “#caldavroot .menu” instead of just “.menu”.

• This reply was modified 3 years ago by woof.

Okay, for my missing reputation my/your request was rejected – totally acceptable. But this lead to that they accepted the long suggested strings, so the German translation should become available. My goal reached. Nevertheless I’ll keep an eye on the translation and maybe will earn the reputation and try again to become translation editor again then ??

Thanks for your affords.

• This reply was modified 3 years, 10 months ago by woof.

Fixed again with 3.1.3

Thanks a lot.

Thanks a lot. I tried a lot of Calendar plugins and really like yours the most. Showing that it is in active development is just one more pro ??

The fix worked for me, but now I have the issue again with 2.1.1 update.