Empty plugin list in Manager after clean installation of Evolution CMS 3.5.x

[evolution-lover]

Description

After performing a fresh, clean installation of Evolution CMS 3.5.x, the Plugins section in the Manager is entirely empty. Standard core plugins that are typically included by default do not appear in the Elements tree or the database table.

Environment

• Evolution CMS Version: 3.5.x

Steps to Reproduce

1. Run a fresh installation of Evolution CMS 3.5.x.
2. Complete the setup and log in to the Manager.
3. Go to Elements > Plugins.
4. Observe the empty list.

Expected Behavior

The default set of plugins (such as DocLister, TinyMCE, etc.) should be automatically populated in the site_plugins table and visible in the Manager interface.

Actual Behavior

The plugin list is empty. While the files may exist in assets/plugins/, they are not registered in the system/database.

Possible Cause/Observations

• It seems the migration or the "install" artisan command fails to seed the plugin table during the final stages of installation.
• Check if php artisan evolution:install or php artisan migrate is failing to trigger the seeder for core elements.

Screenshot

[middleDuckAi]

MiddleDuck update:

Analysis

• I re-checked this against the current Evolution 3.5.x install surfaces.
• The supported web installer path still imports bundled install assets from install/assets/* and registers them during installation.
• The standalone installer now lives in evolution-cms/installer, and its current flow is different: it runs migrations, a fixed seeder list, and optional Extras installation, but it does not appear to import the bundled core install payload from install/assets/*.

Conclusion

This looks like an installer-boundary issue, not a safe core patch in evolution-cms/evolution.

The main gap is not "install every historical extra automatically". It is that the new installer should reproduce the bundled default component baseline that still ships with the core install payload.

Follow-up

I opened the installer-side issue here:

• Bundled install/assets components are not imported by the standalone installer installer#41

That issue includes:

• the current evidence for why this belongs in the standalone installer
• the distinction between bundled core components and optional Composer Extras
• solution options for importing bundled install/assets/* content during evo install

Notes

• The web installer path in the core repo still looks correct.
• Because of that, I am not opening a core PR for this report.
• The next fix should happen in evolution-cms/installer, then we can re-check the resulting install baseline here.