Since the 4.0 milestone, we’ve been busy expanding where you can publish, deepening analytics, and giving teams finer control over who can use which social profiles.
Nelio Content 4.1 ties all of that together and adds a developer-focused cleanup of hooks and function prefixes so your customizations stay future-proof. Here’s what’s new since 4.0 and how it all comes together in day-to-day use, followed by the full changelog at the end.
Publish to more places: Medium publications, Blogger, and Plurk
Your social lineup just grew again. If Medium is part of your strategy, you can now publish to Medium publication profiles, not just personal accounts, which means your best stories reach the audience that follows your publication directly.
Alongside Medium, Blogger joins the roster, giving you another owned channel to syndicate long-form content without leaving your editorial calendar. And for teams active in Asia and beyond, Plurk support lets you schedule posts with the right qualifier set at creation time so tone and context are spot-on.
All three integrate with the calendar you already use—drag, drop, and schedule across networks in one flow—while message previews continue to improve so you can trust what will go live.
Analytics that answer more questions, faster
Measuring resonance across networks is easier now that we’ve extended engagement tracking to more social platforms and tightened our Google Analytics 4 integration. You’ll see pageviews attributed from more networks and richer engagement signals in the same place you plan.
When it’s time to report, your Top Posts can be exported to CSV right from analytics, so you can hand off a spreadsheet to stakeholders, blend it into a Data Studio dashboard, or crunch it in your BI tool—no copy-paste marathons required.
Nelio Content
I’m so happy about Nelio Content that I will sound like a payed advocate… but here’s why you’ll love it: it works as promised, its auto-scheduling feature is top-notch, Nelio’s value for money is unmatched, and the support team feels like your own.
Panozk
Governance and control for social profiles
As teams grow, not everyone should hit “publish” everywhere. You can now control usage permissions per social profile, clarifying who can schedule or send where. It’s a small change with a big impact: fewer accidental posts to the wrong channel, clearer handoffs between roles, and review flows that match your internal policies.
Planning and publishing feel smoother
The calendar and content board continue to pick up small touches that add up. Status columns with multiple items now sort more predictably in the board, and your board date preferences persist across reloads so the view stays just the way you left it.
We’ve added a sticky post control right inside the calendar’s post editor and surface stickiness in the calendar, streamlining editorial decisions without bouncing into WordPress settings.
Around the social experience, walkthroughs of the message editor are clearer, connection dialogs are centered correctly, and VK profiles/communities switched to OAuth with improved previews, while Medium previews also look better.
Behind the scenes, we’ve reduced duplicate store registrations, fixed edge cases like saving posts without series via quick edit, and prevented duplicate email notifications on editorial comments or tasks.
Security, compatibility, and reliability
Reliability matters when you’re shipping daily. We tightened capability checks so users without proper permissions can’t view posts or create calendar items with different authors.
We also improved compatibility with caching and optimization tools—like fixing external featured-image edge cases and ensuring Speed Optimizer plays nicely when sharing to Medium and Blogger.
Scheduled posts use standard WordPress nonce generation/validation for missed schedules, and we cleaned up the management of rewrite copies through quick edit and the handling of non-active network profiles. The result is a calmer, more predictable workflow.
For developers: clearer hooks, safer extensions
If you extend Nelio Content, this release brings important housekeeping. We changed the filter the_nelio_content to nelio_content_the_content and renamed the actions before_the_nelio_content / after_the_nelio_content to nelio_content_before_the_content / nelio_content_after_the_content.
We also changed the global function prefix, aligning everything under a consistent, namespaced convention that avoids collisions. If you rely on these hooks or functions, update your code accordingly; the payoff is a cleaner integration surface going forward.
How this release helps your team
From planning to proof to publish, 4.1 widens your reach with Medium publications, Blogger, and Plurk, while analytics tell a fuller story across more networks and GA4. Your reports are simpler to share thanks to CSV exports of top performers, and your process is safer because profile-level permissions match who’s allowed to post where.
Day to day, the calendar and board feel more cooperative—sorted columns behave, preferences stick, sticky posts are obvious—and previews and connections on key networks are more faithful. Underneath, permissions, nonces, and compatibility tweaks make the whole system sturdier, so teams can move fast without surprises.
Getting started
Update to Nelio Content 4.1, then connect any new Medium publication, Blogger, or Plurk profiles you plan to use. Review profile usage permissions so the right people can publish to the right places. In analytics, try exporting Top Posts to CSV for your next report, and glance at your board and calendar—sorting and saved preferences should make the view feel familiar each time you return. If you maintain custom code, scan for the renamed hooks and prefix changes and update extensions to keep everything in sync.
Full changelog (since 4.0)
Added
- Support for Medium publication profiles.
- Blogger publishing.
- Plurk publishing, including a qualifier field in the message editor.
- CSV export for Top Posts in analytics.
- Usage permissions setting to control who can use each social profile.
- Sorting action for status columns with multiple items in the Content Board.
- Persisted date preferences in the Content Board between reloads.
- Sticky control in the calendar’s post editor and sticky indicator in the calendar.
- VK support for profiles and communities via OAuth.
- Link button option in Telegram profiles for URL shares.
- Plugin version number in the Dashboard widget.
Fixed
- Count of available profiles.
- Walkthrough of the social message editor.
- Duplicated registration of
'nelio-content/post-quick-editor'store. - Saving posts without series via WordPress quick edit.
- Capability check of internal events.
- Duplicate email notifications for a single editorial comment or task.
- Custom status selector behavior in the block editor.
- Center position of the social profile connection dialog.
- Compatibility with Speed Optimizer (sg-cachepress) when sharing to Medium and Blogger.
- Management of rewrite copies via WordPress quick edit.
- Handling of social profiles for non-active networks.
- Unauthorized creation of posts with a different author from the calendar.
- Unauthorized users viewing posts.
- PHP fatal error caused by external featured images.
- Post status icons in the “Nelio Content Overview” Dashboard widget.
- Sticky option compatibility on posts.
- Management of custom statuses.
- Drag & drop of custom statuses.
Other
- Better Google Analytics 4 integration.
- Engagement extended to more social networks; pageviews attributed from more sources.
- Improved Medium message preview.
- Improved VK message preview.
- Global function prefix updated for consistency.
- Filter renamed:
the_nelio_content→nelio_content_the_content. - Actions renamed:
before_the_nelio_content/after_the_nelio_content→nelio_content_before_the_content/nelio_content_after_the_content. - Use standard WordPress functions to generate/validate missed scheduled post nonce.
- Removed custom style in
RadioControlcomponent.
Featured image by Mathew Schwartz on Unsplash.
Leave a Reply