[BUG]: Placeholder::update_() compiler error

RaZaMo commented

2026-02-19 21:23:19 +00:00

What Happened?

Adding a layout to a view got this error when compiling a joomal component

An error has occurred.

0 VDM\Joomla\Componentbuilder\Compiler\Placeholder::update_(): Argument #1 ($data) must be of type string, null given, called in /var/www/html/libraries/vendor_jcb/VDM.Joomla/src/Componentbuilder/Compiler/Helper/Interpretation.php on line 3705.

The issue is related with a typo while echoing layout inside a view.

Steps to reproduce the Bug

1- Insert a layout inside a view with a typo on name layout.

something like this
Layout code name: contributioneditmodal

echoing

<?php echo LayoutHelper::render('contribution.edit.modal', [?]); ?>

this misspelled layout code name breaks the compiling process.

Actually echoing any "layout code name" that does not exist breaks the process.

Which Joomla version are you compiling in?

6.0.3

Which PHP version are you compiling in?

PHP Version 8.3.29

Which Joomla versions are you targeting?

6

Which PHP version are you targeting?

PHP Version 8.3.29

Which Web server is JCB running on?

Apache 8.3

Which Relational Database is JCB running on?

MySql 8.0.44

Which OS is JCB running on?

RaspiOs

Which JCB version are you using?

v 6.1.4 stable

Where in JCB did this issue occur?

Compilation of a component

On which browsers did you encounter the issue?

Firefox

Additional Comments

No response

### What Happened? Adding a layout to a view got this error when compiling a joomal component An error has occurred. 0 VDM\Joomla\Componentbuilder\Compiler\Placeholder::update_(): Argument #1 ($data) must be of type string, null given, called in /var/www/html/libraries/vendor_jcb/VDM.Joomla/src/Componentbuilder/Compiler/Helper/Interpretation.php on line 3705. The issue is related with a typo while echoing layout inside a view. ### Steps to reproduce the Bug 1- Insert a layout inside a view with a typo on name layout. something like this Layout code name: contributioneditmodal echoing <?php echo LayoutHelper::render('contribution.edit.modal', [?]); ?> this misspelled layout code name breaks the compiling process. Actually echoing any "layout code name" that does not exist breaks the process. ### Which Joomla version are you compiling in? 6.0.3 ### Which PHP version are you compiling in? PHP Version 8.3.29 ### Which Joomla versions are you targeting? 6 ### Which PHP version are you targeting? PHP Version 8.3.29 ### Which Web server is JCB running on? Apache 8.3 ### Which Relational Database is JCB running on? MySql 8.0.44 ### Which OS is JCB running on? RaspiOs ### Which JCB version are you using? v 6.1.4 stable ### Where in JCB did this issue occur? Compilation of a component ### On which browsers did you encounter the issue? Firefox ### Additional Comments _No response_

RaZaMo added the Bug label 2026-02-19 21:23:19 +00:00

Lemuel added help wanted and removed Bug labels 2026-02-20 17:01:17 +00:00

Lemuel commented

2026-04-14 21:43:21 +00:00

Owner

Hi @razarate, Thank you for taking the time to report this and for outlining the steps so clearly.

What you're experiencing is not a fault in the compiler itself, but rather a consequence of how layouts are resolved during the JCB build process. Layout (and Template) references must be exact, as they are compiled and linked at build time. If a layout name is misspelled or does not exist, the compiler cannot resolve it, which will result in an error like the one you encountered.

To help prevent this, several safeguards and conveniences have already been built into JCB:

Layout code names are normalized and stored in a consistent format (e.g. mylayoutname), regardless of how they are originally entered (spaces, caps, dots, underscores, etc. are all handled).
The layouts and templates list views provide a one-click option to copy the exact <?php echo LayoutHelper::render('mylayoutname', [?]); ?> snippet, ensuring the correct reference is used.

Because of this, when manually adding or editing layout calls, it's important to do so with care and precision. The system assumes that layout references are intentional and correctly defined, as it cannot safely infer or correct unknown layout names during compilation.

In short, the tooling is designed to make correct usage straightforward, but it still relies on accurate references when linked to other areas in JCB. If the provided helpers are used, this kind of issue should be avoided.

We appreciate your feedback and understand how this can be confusing at first, but this behavior is expected within the current architecture.

Hi @razarate, Thank you for taking the time to report this and for outlining the steps so clearly. What you're experiencing is not a fault in the compiler itself, but rather a consequence of how layouts are resolved during the JCB build process. **Layout (and Template) references must be exact**, as they are compiled and linked at build time. If a layout name is misspelled or does not exist, the compiler cannot resolve it, which will result in an error like the one you encountered. To help prevent this, several safeguards and conveniences have already been built into JCB: * Layout _code names_ are normalized and stored in a consistent format (e.g. `mylayoutname`), regardless of how they are originally entered (spaces, caps, dots, underscores, etc. are all handled). * The layouts and templates list views provide a one-click option to copy the exact `<?php echo LayoutHelper::render('mylayoutname', [?]); ?>` snippet, ensuring the correct reference is used. Because of this, when manually adding or editing layout calls, it's important to do so with care and precision. The system assumes that layout references are intentional and correctly defined, as it cannot safely infer or correct unknown layout names during compilation. In short, the tooling is designed to make correct usage straightforward, but it still relies on accurate references when linked to other areas in JCB. If the provided helpers are used, this kind of issue should be avoided. We appreciate your feedback and understand how this can be confusing at first, but this behavior is expected within the current architecture.

Lemuel closed this issue

2026-04-15 14:58:23 +00:00

[BUG]: Placeholder::update_() compiler error #1286