Nibbly 1.4.0: MPL-2.0, Better Contact Delivery, Shared News Routing

Nibbly 1.4.0 is a housekeeping release with a few practical improvements that matter for real deployments: clearer licensing, more flexible contact email delivery, and simpler news detail rendering across languages.

License Change Starting with 1.4.0

Starting with this release, Nibbly is licensed under the Mozilla Public License 2.0. Earlier releases up to and including 1.3.2 remain available under the MIT License.

MPL-2.0 keeps Nibbly usable for personal, agency, client, and commercial projects, while making the boundary around Core changes clearer: if someone distributes modified Nibbly Core files, those modified Core files must remain available under MPL-2.0. Site-specific templates, assets, content, and custom project code can still use their own terms.

Multiple Recipients and BCC for Contact Forms

Contact form delivery now accepts comma-separated primary recipients and optional BCC recipients. This is useful for teams that want messages to reach multiple inboxes, archive addresses, or CRM intake addresses without changing template code.

Nibbly validates and normalizes the lists before saving settings. SMTP delivery sends every primary and BCC address as an envelope recipient, while keeping BCC addresses out of visible headers. The PHP mail fallback sends BCC copies separately to avoid exposing blind-copy recipients.

Shared News Post Renderer

News detail pages now use one shared Core renderer instead of duplicating the same post-loading logic into every generated language wrapper. Apache and the PHP development router send news detail URLs through that renderer before language-local listing templates can intercept them.

For existing projects, old generated wrappers continue to work. New generated wrappers simply delegate to includes/news-post.php, which reduces duplicated update-sensitive code in site templates.