Modules¶
Newsletter → Configuration → Modules
Modules are parts of the plugin you can switch on. Leave out what you do not need — a module that is off hooks into nothing, creates nothing and collects nothing.
All modules sit side by side at the top. A green dot means: running. Clicking one opens its settings; at the very top it says Module activated: Yes / No.
The eleven modules¶
| Module | Package | What for |
|---|---|---|
| Sending log | both | Who received which newsletter |
| Spam protection | both | Fending off automated sign-ups, without a third-party service |
| Post notification | both | Turning a post into a newsletter |
| Placeholder rule | both | Placeholders whose value depends on a condition |
| Statistics | Pro | Opens and clicks |
| Bounce processing | Pro | Fetching undeliverable mail and matching it up |
| Subscriber fields | Pro | Custom fields in the subscription form |
| Attachments | Pro | Attaching files to a newsletter |
| Captcha | Pro | Google reCAPTCHA on the form |
| SOAP interface | Pro | Third-party systems, the classic way |
| REST interface | Pro | Third-party systems, over HTTP |
In the free package the Pro modules are not included — not switched off but simply absent. They therefore do not appear in the list either.
What we recommend¶
| Module | Recommendation |
|---|---|
| Spam protection | Switch it on. An open subscription form will be found. The module needs no third-party service and stores no IP address |
| Sending log | Switch it on. Without it you cannot say later who received a newsletter — and that is exactly the question that comes up when there is doubt |
| Statistics | As needed, and with an eye on data protection: it measures the behaviour of individual recipients |
| Bounce processing | As soon as your list grows. Dead addresses cost deliverability |
| Captcha | Rather not — the spam protection does the same without Google |
| Everything else | If you need it |
What happens when switching on and off¶
Switching on creates what the module needs: its tables, its defaults, its menu item. That is always additive — existing data is not touched.
Switching off deletes nothing. The module simply stops hooking in: its menu item disappears, its hooks no longer run, its tables stay. Switch it on again later and everything is back.
What a switched-off module does to running newsletters
It is missing. And the plugin tells you — when you open a newsletter that has not been sent:
- Placeholders nobody resolves. A
%uf_1%from the subscriber variables reaches the recipient's text exactly as it stands. - Files belonging to a module that is not running. The attachments are still there but no longer reach any mail.
Both messages disappear by themselves once the module is running again.
Newsletters already sent are unaffected: their HTML is frozen, and what was in it stays in it.
Your own modules¶
If you write a module of your own, put it under
wp-content/uploads/wpng/user_mods/. A file of the same name there
replaces the supplied module.
Two things such a module should do, or it will stand out elsewhere:
- Implement
abonnent_delete()if it stores anything about the subscriber. Otherwise the record is left behind when the subscriber is deleted. - Implement
datenschutz_auskunft(). Otherwise the module appears under Newsletter → Configuration → Data collected among those that said nothing — and saying nothing is not the same as collecting nothing. - Read input through
wpng_eingabe_*()or applywp_unslash()yourself. Values in$_REQUESTare slashed, as everywhere in WordPress; taking them unchecked stores a backslash in front of every apostrophe.
