Jahia from the Field: jContent 3.7.1 simplifies Content Editor

This edition of Jahia product news puts the spotlight on jContent 3.7.1. It's not an overnight revolution: this release strips away what slows you down day to day, sharpens what you can target, and opens more doors for your technical teams. Here's a tour of what's changed in this new version.

A reorganized Content Editor, clearer day to day

With jContent 3.7.1, you no longer need to hunt for the settings that matter: they're now right at hand. Visibility conditions and vanity URLs, previously buried inside Advanced Edit > Advanced Options, are now one click away, right on the main toolbar. Live roles, edit roles, workflows, and versions are also available on that same toolbar. The upshot: fewer clicks, less searching, and teams that keep their editing rhythm without interruption.

The old preview panel and the old advanced options window give way to a genuine side panel: always open, extensible, and organized into four tabs — Preview, Details, History, and Usages.

• The Preview tab, always shown first, displays content in context, exactly as it actually appears on its page, using the same rendering logic in both jContent and Content Editor.
• The Details tab brings together the content's technical information, with one-click copy on every value, handy for passing a path or a reference to a developer or IT.
• The History tab breaks down each change, specifies whether it happened at the content level or on a specific property, indicates the language involved, and can be filtered by event type.
• The Usages tab, for its part, shows at a glance whether a piece of content is reused elsewhere, and where. A single destination for everything that used to mean switching screens.

Rethought navigation and preview

Building a page becomes more intuitive with jContent 3.7.1: the buttons for adding a component, an area, or an element appear at exactly the right moment, right where you need them. When you drag an element, a scroll zone appears visibly at the top and bottom of the screen, and the insertion line is more visible, so you can be sure exactly where your content will land. The result: a more natural feel for the Page Builder, with less hesitation and fewer attempts needed to build a page.

Preview moves in the same direction: jContent and Content Editor now share the same rendering rules, and selected content displays in context, exactly as it will actually appear on its page, rather than as raw text or isolated on a separate page. That means validating a piece of content at a glance, with no need to picture the final result. Context menus, for their part, load faster, so they don't break your working rhythm.

On sites that manage multiple domains, the Live button offers a dropdown arrow to choose which domain to open, with the site's "server name" domain always offered as the default.

Sharper content targeting, and safer too

jContent 3.7.1 brings all visibility rules together on a single screen: by language, and by date and time (with three possible condition types: day of the week, start and end date, or time of day). You can combine several conditions, and each one shows live whether it currently resolves to visible or hidden.

This is where the interface really makes editorial work safer: a summary permanently displays the "currently in preview" and "currently in live" statuses side by side. If the two don't match, you see it immediately, before publishing anything. For teams already using these settings, the transition is effortless: roles that had access under the old permission automatically keep it, with no reconfiguration and no interruption of service.

Simpler translation and multilingual editing

Switching between writing and translating no longer breaks your workflow: from advanced mode, jContent 3.7.1 adds a dropdown menu to switch instantly between Edit mode and Translate mode, with the source and target languages displayed side by side, and every field editable in the same place.

This version also reduces day-to-day production errors: file upload and replacement are more reliable, and the Advanced Search help text has been clarified. The content sanitizer policy now allows links inside tooltips, which lets you link a tooltip to a help page or piece of documentation, for example, to support editors right from their working screen.

More open foundations for your development work

Your technical teams gain real room to maneuver with jContent 3.7.1. The new side panel can be customized with your own modules, you can add your own tabs alongside Preview, Details, History, and Usages. Your teams can also expose content history in their own interfaces or audit dashboards thanks to a new version of the GraphQL API, with no custom development on Jahia's core, and build use cases that used to be complicated to set up — such as generating forms based on a historical version of a piece of content without touching the live node — thanks to the new NodeTypeResolver interface.

For teams building their own Content Editor screens, saving development time becomes tangible: EditPanelContent, the date-formatting primitives, and a new ContentEditorFragment GraphQL fragment are exposed to UI extensions, and new tableConfig options for accordions make it possible to deliver a tailor-made interface without starting from scratch. Less time is wasted resolving visual conflicts too: jContent's styles in the Page Builder are now isolated from your own page styles.

Reliability, stability, and security

jContent 3.7 fixes around 50 bugs and security flaws. Your teams gain day-to-day continuity, with fewer blocking errors and fewer interruptions, while reducing exposure to known vulnerabilities.

Among the fixes: document search is now case-insensitive, several blocking errors (NPEs) have been prevented, language switching during editing is more reliable, and visibility purge jobs are handled better on restart.