magebit / vsbridge-static-content-procesor

magebit/vsbridge-static-content-procesor

Converts magento URL's to VSF during indexation

  • Kristofers Ozolins
magento2-component Compatibility: 2.4.7 Code Quality: Fail Tests: N/A Security: Pass GPL-3.0-only

static-content-processor vsbridge-static-content-procesor

Static Content Processor for VSBridge

Automatically converts Magento urls to VSF urls during indexation

Installation

  • Via composer
    Run composer require magebit/vsbridge-static-content-procesor in your root magento directory

  • Git clone

    • Create Magebit directory in app/code
      • cd app/code
      • mkdir Magebit
    • Clone this repo inside Magebit directory

Usage

Standalone

This module requires you to configure VSF and VSF media urls.
You can find these configuration fields in:
Store - Configuration - VueStorefront - Indexer - Static Content Processor

You can also specify which category and product attributes to run through the processor. As an example, you
could select product description attribute and all the links and images will be converted with VSF urls.

You can also enable Category Image attribute url processor. It will convert all category attributes as image to VSF urls.

As a dependency

You can also use this module as a dependency for your own module:


use Magebit\StaticContentProcessor\Helper\Resolver;

/**
 * @package MyPackage\MyModule
 */
class MyModule
{
    /**
     * @var \Magebit\StaticContentProcessor\Helper\Resolver
     */
    protected $resolver;

    /**
     * @param Resolver $resolver
     */
    public function __construct(Resolver $resolver)
    {
        $this->resolver = $resolver;
    }

    /**
     * Does some content processing
     * @return string
     */
    public function example()
    {
        // This will convert urls and media urls to vsf urls according to the configuration
        return $this->resolver->resolve($this->getSomeStaticContent());
    }
}


Contributing

Found a bug, have a feature suggestion or just want to help in general?
Contributions are very welcome! Check out the list of active issues or submit one yourself.

If you're making a bug report, please include as much details as you can and preferably steps to repreduce the issue.
When creating Pull Requests, don't for get to list your changes in the CHANGELOG and README files.


Magebit

Have questions or need help? Contact us at [email protected]

Changelog

The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.

[2.0.1] - 2021-03-08

Added
  • Add Category Media Url Support

[1.0.0] - 2020-03-03

Added
  • Initial release
Versions
Version Stability QA Status Compatibility Released
2.0.4 stable Fail Magento 2.4.7 Details 2025-11-19 13:45:06
2.0.3 stable Not tested Not yet tested Details 2022-06-03 07:27:37
2.0.1 stable Not tested Not yet tested Details 2021-03-08 09:32:55
2.0.0 stable Not tested Not yet tested Details 2021-03-04 16:03:17
1.0.0 stable Fail Magento 2.4.7 Details 2020-07-16 10:59:32

Requires 3

Package Constraint
divante/magento2-vsbridge-indexer >=2.0.0
php >=7.3.0
symfony/property-access ^3.4||^4.4||^5.0

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 Pass Pass
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 Warning 31 31 warnings (ruleset: Magento2) — 17 auto-fixable with phpcbf
PHPMD Warning 2 2 rule violations (UnusedFormalParameter:2)
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. 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 3 3
2.4.8 Error Error
2.4.9 Error Error

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 Pass 0
License
GPL-3.0-only
Authors
  • Kristofers Ozolins

More from magebit

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.