The {source} tags remain visible or produce no output

Check that the system plugin is enabled

Go to System >> Manage >> Plugins, search for System - Regular Labs Sourcerer, and make sure it is enabled. The separate Sourcerer editor-button plugin is only needed for the editor button; the system plugin processes the tags on the site.

Check the tag syntax

The opening and closing Sourcerer tags must be plain text without editor markup inside them. For example, this will not be recognized:

<span>{</span>source}

Remove surrounding spans or other formatting from the tag itself. Also check the configured Sourcerer tag word and Tag Characters under Tag Syntax if your site does not use the default {source}...{/source} syntax.

Check where Sourcerer is enabled

Sourcerer has separate policies for Articles, Components, and Other Areas such as modules and final page output. Confirm that the area containing the tag is enabled and, for component output, that the active component is not excluded. See Configuration for the available controls.

Code disappears when the item is saved

If the code is already missing immediately after saving, the editor or Joomla text filtering removed it before Sourcerer could process it.

The safest way to insert code is the Sourcerer editor button. If you enter code manually, configure the active editor profile and Joomla Text Filters to retain the HTML, CSS, JavaScript, or PHP syntax that the intended users are allowed to save. Reopen the item in source or code view after saving to confirm that the complete Sourcerer block is still present.

Code is present in the editor but removed on the site

This normally means that a Sourcerer security or area policy rejected the block or one of its code types. When Place HTML comments is enabled, inspect the page source for a Sourcerer comment explaining why the code was removed.

Check the following:

  • The Articles, Components, or Other Areas policy for the location where the tag is rendered.
  • The global and area-specific Allow CSS tags, Allow JavaScript tags, and Allow PHP tags policies.
  • For article content, whether both the article creator and last modifier satisfy the configured security groups. If no separate modifier is stored, the creator is used for both checks.
  • The configured forbidden HTML tags and forbidden direct PHP function calls.
  • Whether the syntax came from unverified page output or direct visitor input. Sourcerer blocks request-supplied code from untrusted visitors even when an area otherwise permits unverified content. Free trusts only Super Users for this purpose. In Pro, only logged-in groups selected under Trusted Request User Groups can pass that request guard; the normal area and code-type policies still apply.

Verified content is stored content passed directly to Sourcerer with enough information to check who may edit it. Unverified content is rendered page output whose original source and editing permissions Sourcerer cannot confirm. The Only Verified policies are the safe default for code that should never run from arbitrary generated output.

See Security Control for the full edition and policy details.

Add provenance diagnostics

To investigate why unverified code was removed, add sourcerer_diagnostics=1 to the frontend URL, for example ?sourcerer_diagnostics=1. This only adds provenance and rendering-context details to Sourcerer's removal comments. It does not display the removed source code, content IDs, credentials, or submitted visitor values.

Diagnostics are visible only while Place HTML comments is enabled. Remove the URL parameter after troubleshooting.

JavaScript is not working

Place inline JavaScript inside normal script tags:

<script>
    // JavaScript code
</script>

Then check the effective Allow JavaScript tags policy for the content area. Sourcerer also treats inline event handlers, executable JavaScript URLs, srcdoc, and JavaScript file attributes as JavaScript, so those are removed when JavaScript is not allowed.

PHP is not working

Place PHP inside complete PHP tags:

<?php
    // PHP code
?>

Check the effective Allow PHP tags policy, the article creator and modifier security groups when applicable, the forbidden PHP function list, and the configured Include Path for PHP files.

PHP errors

When Handle PHP Errors is enabled, Sourcerer catches recoverable PHP execution errors and exceptions, discards partial output from the failed block, and prevents the error from breaking the complete page. If Place HTML comments is also enabled, the page source contains a Sourcerer comment with the error type, message, and useful file or block line information.

When Place HTML comments is disabled, the failed block still produces no partial output, but its explanatory comment is removed. When Handle PHP Errors is disabled, the original PHP error is allowed to propagate for development and debugging.

Hard process termination such as exit, memory exhaustion, or a killed request cannot be recovered, and error handling cannot undo changes completed before an error occurred.

What to do with <head> or <body> tags

Do not add document-level <html>, <head>, or <body> tags inside article or module content. Joomla already creates that document structure, and inserting another copy produces invalid HTML.

When copying a complete example, insert only the content that belongs inside its body. To load CSS or JavaScript in the document head, use the Pro editor button's placement options or one of the methods described under Loading CSS Styles and JavaScript.

Restricting who can use Sourcerer

Use Sourcerer's security settings to control who may run each code type and in which content areas. Changing the Sourcerer tag word only changes the syntax; it is not an access-control mechanism.

For article content, configure the creator and modifier security groups. For generated component, module, or other output, keep the relevant policy on Only Verified unless every possible source is trusted. Keep the request guard limited to logged-in groups that are allowed to submit every code type enabled for unverified content.