TL;DR: If a bundled nopStation plugin throws a missing dependency error for
NopStation.Core, the file is already on your server. The admin dashboard is simply hiding it because the backend system name doesn't match the frontend display name.
When installing a new plugin in nopCommerce, missing dependency alerts can sometimes pull you into an unexpected troubleshooting loop.
Recently, I was setting up the SSLCommerz payment plugin. The installation halted with a bright red warning banner:
Error Message:
The "SSLCommerz" plugin depends on the following plugins which must be installed beforehand: "NopStation.Core"
Naturally, I immediately went to the Local Plugins search bar and typed in the exact system name provided by the error message: NopStation.Core.
Zero results.
Investigating the Server Folders
Knowing that the main NopStation.Plugin.Payments.SSLCommerz-4.90.zip package comes bundled with both plugins inside, I didn't actually have to upload them separately.
To make sure nothing went wrong during the unpack process, I checked my server's remote Plugins directory. Sure enough, both folders were unpacked and sitting right next to each other on the filesystem.
If the files were successfully on the server, why wasn't the local plugin list showing it?
The Display Name Catch 🔍
The issue comes down to how nopCommerce filters its plugin list, combined with how nopStation structures their extensions. This brings us to the main architectural learning here: the mismatch between backend system names and frontend display names.
-
System Name: Used in folder paths, code references, and dependency error strings (
NopStation.Core). - Display Name: The friendly text rendered in the admin panel UI.
Instead of looking for the system name NopStation.Core which was given in the SSLCommerz's plugin dependency error message, I went back to the Local Plugins dashboard, cleared the query, and searched for a broader keyword: "Nop".
Boom. It appeared immediately under its actual UI naming convention:
- Display Name: Nop-Station Core
- Description: This plugin is used to manage Nop-Station plugins.
Because the dashboard search bar filters strictly by the friendly UI display name rather than the backend system string, searching for the exact error message text hid it from view.
🚀 Key Takeaways for Developers
If you find yourself stuck on a similar dependency block while using third-party extensions like those from nopStation, bypass the error string and try these steps:
-
Verify the Directory: Check your filesystem's
Pluginsfolder first to ensure the dependency directory actually extracted. - Search by Fragment: Do not paste the full system name from the error banner into the admin search bar. Search for a core fragment like "Nop" or "Core".
- Install the Core First: Once found, hit Install on the core management plugin, click Restart application to apply changes, and then proceed to install your primary payment plugin.
Keeping this display-versus-system name behavior in mind will save you plenty of time when working inside the nopCommerce ecosystem!
