msp / cmsimportexport
msp/cmsimportexport
CmsImportExport
MSP_CmsImportExport is a module for Magento 2 allowing users to import/export CMS pages or blocks.
MSP_CmsImportExport supports multistore and wysiwyg images.
Installation
composer require msp/cmsimportexport
How to export contents
Select one or more pages you wish to export from CMS > Pages in your Magento Admin and select Export from the mass action menù.
You will download a ZIP file containing pages or blocks information. If your pages or blocks contain one or more images,
they will be automatically added in the ZIP file.
How to import contents
A new option Import will appear in your Magento Admin Content bmenu. Click on it to import a previously exported ZIP file.
While importing you can change import modes:
CMS import mode
Overwrite existing: If a page/block with same id and store assignment is found, it will be overwritten by the ZIP file content.
Skip existing: If a page/block with same id and store assignment is found, it will NOT be overwritten by the ZIP file content.
Media import mode
Do not import: Do not import media files in the ZIP file.
Overwrite existing: If an image with same name exists it will be overwritten with version in the ZIP file.
Skip existing: If an image with same name exists it will NOT be overwritten with version in the ZIP file.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.1.2 | stable | Fail | Magento 2.4.7-2.4.8 Details | 2023-02-28 13:11:17 |
| 1.1.1 | stable | Not tested | Not yet tested Details | 2019-05-09 15:00:19 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2019-03-27 09:11:31 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2018-04-19 13:50:54 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2018-04-18 14:21:38 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2018-04-18 14:03:42 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2018-04-18 12:49:18 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2017-06-21 16:22:10 |
| 0.1.4 | stable | Not tested | Not yet tested Details | 2016-10-10 12:35:09 |
| 0.1.3 | stable | Not tested | Not yet tested Details | 2016-07-19 12:01:58 |
| 0.1.2 | stable | Not tested | Not yet tested Details | 2016-06-14 10:12:20 |
| 0.1.1 | stable | Not tested | Not yet tested Details | 2016-06-06 14:25:08 |
Requires 2
| Package | Constraint |
|---|---|
| magento/magento-composer-installer | * |
| msp/common | * |
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.
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.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 61 | 1 error, 60 warnings (ruleset: Magento2) — 2 auto-fixable with phpcbf |
| PHPMD | Warning | 12 | 12 rule violations (MissingImport:8, ExcessiveMethodLength:1, ExcessiveClassComplexity:1, CyclomaticComplexity:1, NPathComplexity:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 2 | valid; 2 advisory notes (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.
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
| 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
| 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.
More from msp
View vendorTurn 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.