No Code Attached Yet bug
avatar svenbluege
svenbluege
13 Jun 2026

What happened?

I can't execute the installation script for components or packages. This results in not executed install-steps, migrations and more.

pkg_foobar_5_8_0-a1_QUICKBUILD.zip

Version

6.1-dev (2026-06-13)

Expected result

The installation script is executed.

Actual result

The installation script is not executed. In my example, resulting in an error page.

System Information

I'm using the latest dev version of Joomla 6.1

Additional Comments

I suspect the latest change here: https://github.com/joomla/joomla-cms/blob/6.1-dev/libraries/src/Installer/InstallerAdapter.php#L950

After changing the path back to 'source', both the component and the package install scripts work.

For components/packages, the installation script is checked for existence but copied after this check. Looks like a chicken-egg issue here.

avatar svenbluege svenbluege - open - 13 Jun 2026
avatar joomla-cms-bot joomla-cms-bot - change - 13 Jun 2026
Labels Added: No Code Attached Yet bug
avatar joomla-cms-bot joomla-cms-bot - labeled - 13 Jun 2026
avatar svenbluege svenbluege - change - 13 Jun 2026
The description was changed
avatar svenbluege svenbluege - edited - 13 Jun 2026
avatar joomdonation
joomdonation - comment - 13 Jun 2026

Look like it causes by #47637 . @laoneo Could you please check?

avatar joomdonation joomdonation - change - 13 Jun 2026
Labels Added: Release Blocker
avatar joomdonation joomdonation - labeled - 13 Jun 2026
avatar jiteshkhatri11
jiteshkhatri11 - comment - 14 Jun 2026

I investigated this locally and the issue appears to be related to the changes introduced in #47637.

For components and packages, the installer script file is checked for existence before it has actually been copied to its final location. As a result, the install script (install, update, migrations, etc.) is never executed.

Changing the path back to 'source' in InstallerAdapter.php restores the previous behaviour and allows the installation scripts to run correctly.

This looks like a regression caused by the order of operations (script existence check happening before the copy step). It would be good to confirm whether the check should continue to use the original source path until the package files have been moved into place.

I'll try to prepare a reproducer and possible fix if needed.

avatar joomdonation
joomdonation - comment - 14 Jun 2026

Yes, change path back to 'source' is the right option. In short, just revert the PR #47637

avatar laoneo
laoneo - comment - 15 Jun 2026

Thanks @svenbluege , you saved us a lot of headache with the early test.

avatar richard67
richard67 - comment - 15 Jun 2026

Please test PR #47964 . Thanks in advance.

avatar richard67 richard67 - change - 19 Jun 2026
Status New Closed
Closed_Date 0000-00-00 00:00:00 2026-06-19 13:31:09
Closed_By richard67
avatar richard67 richard67 - close - 19 Jun 2026
avatar richard67 richard67 - change - 19 Jun 2026
Labels Removed: Release Blocker
avatar richard67 richard67 - unlabeled - 19 Jun 2026

Add a Comment

Login with GitHub to post a comment