- NONE
AddStuff lets you insert arbitrary HTML (scripts, stylesheets, etc.) at four precise locations in every rendered page. It works as a render filter: no template change, no redeployment, no developer required.
A new Add Stuff panel is available under Administration → Sites → [site] → Add Stuff. It provides four syntax-highlighted code editors (one per injection point) and saves without any publication workflow.
Access is controlled by the new siteAdminAddStuff permission, included in the built-in Site Administrator role. A custom site role can be created to grant access without full Site Administrator rights.
When editing page properties, the four AddStuff fields now use a CodeMirror editor with HTML syntax highlighting, line numbers, bracket matching and code folding.
UI labels are now available in English, French, German, Italian, Portuguese and Spanish.
The minimum required Jahia version is raised from 8.0 to 8.2.
@Component / @Activate)siteSettings added as a module dependencyjmix:addStuff fieldset hidden when editing site node properties in Content Editor (use the dedicated panel instead)My injected code does not appear on the page.
AddStuff only injects code in preview and live modes. Switch out of edit mode and verify in preview first.
The Add Stuff panel is not visible in site administration.
You don't have the siteAdminAddStuff permission. Ask your server administrator to assign you the Site Administrator role or a custom role that includes this permission.
I saved site-wide code but the live site still shows the old version.
Site-level changes are auto-published — no workflow is needed. If the content still looks outdated, your CDN or reverse proxy may be serving a cached response. Purge the cache for the affected pages or wait for the TTL to expire.
I saved a page-level snippet but nothing changed in live.
Page-level changes go through the standard Jahia publication workflow. Make sure the page has been published after saving.
Can I use AddStuff on multiple sites independently?
Yes. Each site has its own independent AddStuff configuration. Settings on one site have no effect on any other.
Is the injected code validated or sanitized?
No. Code is injected exactly as entered. Grant the siteAdminAddStuff permission only to trusted users — a malicious or erroneous script entered at site level would affect every visitor of every page.
Requirements: Jahia 8.2 or higher.
Alternatively, follow the module installation tutorial on the Jahia Academy.
Once deployed, the module need to be per-site activation required.
AddStuff lets you inject custom HTML at four locations in every rendered page:
| Location | Injected |
|---|---|
Start of <head> |
Right after <head> |
End of <head> |
Right before </head> |
Start of <body> |
Right after <body> |
End of <body> |
Right before </body> |
Injected code is visible in preview and live modes only — nothing appears in edit mode.
When both site-level and page-level snippets are configured for the same location, site-level content is injected first, followed by page-level content.
Required permission: siteAdminAddStuff, included in the built-in Site Administrator role. To grant access without full Site Administrator rights, create a custom site role with the Site admin add stuff permission under Server Administration → Roles and Permissions.
See full documentation at https://github.com/jahia/addStuff
MIT License