swissup / core

swissup/core

Swissup core module. It's purpose is to add menu and config placeholders

metapackage Compatibility: Not yet tested Code Quality: Fail Tests: N/A Security: Pass OSL-3.0

Core

Contents

  1. Installation
  2. Swissup Installer Usage
  3. Swissup Upgrade Class
  4. Popup Message Manager

Installation

cd <magento_root>
composer require swissup/core
bin/magento module:enable Swissup_Core
bin/magento setup:upgrade

Swissup Installer Usage

Swissup installer is a class that collects Swissup Upgrades
from all module dependencies and run them, if needed.

Lets see the example of how the Argento theme installer is working:

$module = $this->_objectManager->create('Swissup\Core\Model\Module');
$module->load('Swissup_ArgentoDefault')
    ->setNewStores([0])
    ->up();

What does this code do?

  1. Create Swissup\Core\Model\Module object.
  2. Load module info for Swissup_ArgentoDefault module from composer.json
    file.
  3. Set the store to use (All Stores).
  4. Run installer:
    1. Search for Swissup\Upgrade classes for all
      depends of Swissup_ArgentoDefault module.
    2. Run getOperations and up command for each of the found upgrade class.
    3. Run getOperations and up command of Swissup_ArgentoDefault upgrade class.

Swissup Upgrade Class

When module or theme needs to run some extra logic for specified store views,
it's very handy to use Swissup\Upgrade class, which allows to create and
automatically backup various content types and configuration.

Why not to use Magento DataUpgrade?

  • It does not allow to run upgrade multiple times (reinstall)
  • It does not have built-in methods to change store configuration
  • It does not support content backups

Swissup upgrades — are migrations, located at <module_dir>/Upgrades directory.
Upgrade class must implement Swissup\Core\Api\Data\ModuleUpgradeInterface.

Upgrade examples:

Swissup/ArgentoDefault/Upgrades/1.0.0_initial_installation.php
Swissup/ArgentoDefault/Upgrades/1.0.1_add_callout_blocks.php
Swissup/ArgentoDefault/Upgrades/1.1.0_create_featured_products.php

Upgrade naming conventions

1.0.0       _               initial_installation   .php
^ version   ^ Separator     ^ ClassName            ^ file extension

Class example:

<?php

namespace Swissup\ArgentoDefault\Upgrades;

class InitialInstallation extends \Swissup\Core\Model\Module\Upgrade
{
    public function up()
    {
        // This method is optional.
        // Additional logic may be placed here.
    }

    public function getCommands()
    {
        return [
            'Configuration' => [
                'prolabels/on_sale/product/active'  => 1,
                'prolabels/on_sale/category/active' => 1,
                'prolabels/is_new/product/active'   => 1,
                'prolabels/is_new/category/active'  => 1,
            ],

            'CmsBlock' => [
                'header_callout' => [
                    'title' => 'header_callout',
                    'identifier' => 'header_callout',
                    'is_active' => 1,
                    'content' => 'content'
                ]
            ]

            'ProductAttribute' => [
                [
                    'attribute_code' => 'featured',
                    'frontend_label' => array('Featured'),
                    'default_value'  => 0
                ]
            ],

            'Products' => [
                'featured'       => 6,
                'news_from_date' => 6
            ]
        ];
    }
}

Supported Commands

Key/ClassName Description
Configuration Update store configuration
CmsBlock Create/backup cms blocks
CmsPage Create/backup cms pages
Easyslide Create slider if it does not exists
ProductAttribute Create attribute if it does not exists
Easybanner Create placeholders and banners
Products Create featured, new, special, and any other products

Popup Message Manager

Popup message manager allows to show regular Magento messages with additional
information in popup window.

[image: Popup Message Example]

Usage example

Inject \Swissup\Helper\PopupMessageManager component into your controller
action and use it instead of built-in \Magento\Framework\Message\Manager:

$this->popupMessageManager->addError(
    __('Decoding failed: Syntax error'),
    $popupText,
    $popupTitle
);

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.12.27 stable Fail Not yet tested Details 2026-05-15 11:02:12
1.12.26 stable Not tested Not yet tested Details 2025-12-17 08:27:01
1.12.25 stable Not tested Not yet tested Details 2025-11-17 12:09:02
1.12.24 stable Not tested Not yet tested Details 2025-07-21 12:04:57
1.12.23 stable Not tested Not yet tested Details 2025-07-21 08:02:35
1.12.22 stable Not tested Not yet tested Details 2025-04-09 14:16:36
1.12.21 stable Not tested Not yet tested Details 2024-12-12 09:05:58
1.12.20 stable Not tested Not yet tested Details 2024-07-11 13:18:35
1.12.19 stable Not tested Not yet tested Details 2024-03-28 10:10:19
1.12.18 stable Not tested Not yet tested Details 2023-07-27 11:55:04
1.12.17 stable Not tested Not yet tested Details 2023-07-13 12:57:48
1.12.16 stable Not tested Not yet tested Details 2023-05-23 11:25:26
1.12.15 stable Not tested Not yet tested Details 2023-05-02 12:53:38
1.12.14 stable Not tested Not yet tested Details 2023-03-06 11:40:16
1.12.13 stable Not tested Not yet tested Details 2023-01-13 12:07:27
1.12.12 stable Not tested Not yet tested Details 2022-10-24 09:34:07
1.12.11 stable Not tested Not yet tested Details 2022-08-05 11:18:40
1.12.10 stable Not tested Not yet tested Details 2022-07-18 08:25:16
1.12.8 stable Not tested Not yet tested Details 2022-04-15 13:46:12
1.12.9 stable Not tested Not yet tested Details 2022-04-15 13:43:09
1.12.7 stable Not tested Not yet tested Details 2021-10-27 08:40:57
1.12.6 stable Not tested Not yet tested Details 2021-09-27 13:12:02
1.12.5 stable Not tested Not yet tested Details 2021-08-30 08:12:18
1.12.4 stable Not tested Not yet tested Details 2021-04-06 08:02:14
1.12.3 stable Not tested Not yet tested Details 2021-03-24 09:21:28
1.12.2 stable Not tested Not yet tested Details 2021-03-17 09:06:06
1.12.1 stable Not tested Not yet tested Details 2021-01-25 14:41:37
1.12.0 stable Not tested Not yet tested Details 2021-01-13 09:08:09
1.11.1 stable Not tested Not yet tested Details 2020-11-19 15:53:02
1.11.0 stable Not tested Not yet tested Details 2020-11-18 10:01:28
1.10.5 stable Not tested Not yet tested Details 2020-08-06 11:54:28
1.10.4 stable Not tested Not yet tested Details 2020-08-04 14:14:39
1.10.3 stable Not tested Not yet tested Details 2020-07-22 08:29:29
1.10.2 stable Not tested Not yet tested Details 2020-02-17 09:24:39
1.10.1 stable Not tested Not yet tested Details 2020-01-31 14:31:28
1.10.0 stable Not tested Not yet tested Details 2020-01-08 15:25:43
1.9.0 stable Not tested Not yet tested Details 2019-10-16 07:26:01
1.8.7 stable Not tested Not yet tested Details 2019-09-27 14:27:20
1.8.6 stable Not tested Not yet tested Details 2019-08-12 07:16:10
1.8.5 stable Not tested Not yet tested Details 2019-05-31 13:42:47
1.8.4 stable Not tested Not yet tested Details 2019-03-29 08:29:08
1.8.1 stable Not tested Not yet tested Details 2019-01-02 09:22:19
1.7.3 stable Not tested Not yet tested Details 2018-11-14 10:22:51
1.7.2 stable Not tested Not yet tested Details 2018-11-09 09:36:35
1.7.1 stable Not tested Not yet tested Details 2018-10-22 07:49:40
1.7.0 stable Not tested Not yet tested Details 2018-09-25 13:40:42

Requires 1

Package Constraint
swissup/module-core ^1.12.27

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 not tested not tested
2.4.8 not tested not tested
2.4.9 not tested not tested

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS N/A 0 metapackage ships no source of its own — phpcs skipped (#122)
PHPMD N/A 0 metapackage ships no source of its own — phpmd skipped (#122)
Cpd N/A 0 metapackage ships no source of its own — cpd skipped (#122)
PHP Compatibility N/A 0 metapackage ships no source of its own — php-compatibility skipped (#122)
Composer validate Info 1 valid; 1 advisory note (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 42 42
2.4.8 42 42
2.4.9 42 42

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan N/A 0 metapackage ships no source of its own — malware scan skipped (#122)
License
OSL-3.0

More from swissup

View vendor
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.