Type
magento2-module
Swissup core module. It's purpose is to add menu and config placeholders
magento2-module
OSL-3.0
None
None
None
None
None
None
cd <magento_root>
composer config repositories.swissup composer https://docs.swissuplabs.com/packages/
composer require swissup/module-core --prefer-source
bin/magento module:enable Swissup_Core
bin/magento setup:upgrade
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?
Swissup\Core\Model\Module object.Swissup_ArgentoDefault module from composer.json
file.Swissup_ArgentoDefault module.getOperations and up command for each of the found upgrade class.getOperations and up command of Swissup_ArgentoDefault 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 allows to show regular Magento messages with additional information in popup window.

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
);