Skip to main content

FAQ

Support​

Tip

If you have not found the answer to your question:

Purchasing​

Refund policy​

Important

You can request a refund by following these steps:

  • Log in to your Marketplace account that purchased the module.
  • Go to My Profile Purchase History.
  • Select the correct order from your order history.
  • Request a Refund.
  • Fill out and send the refund order form.

Marketplace Support will request information once the refund request is generated.

Requesting a Refund from Marketplace purchase in Commerce Marketplace Help Center.
Customer Agreement of Marketplace in Magento Legacy Terms.

Purchase to different accounts​

Warning
  • The Adobe Commerce Marketplace team does not have the ability to transfer extension purchases to a different account.
  • It is required to purchase all extensions under the primary entitled account to avoid installation and/or deployment issues.
  • The only resolution available is to initiate a refund request from the Adobe Commerce Marketplace purchasing account if allowed by Magento Marketplace Customer Agreement.

Transferring purchases to different accounts in Commerce Marketplace Help Center.
Customer Agreement of Marketplace in Magento Legacy Terms.

Demo, trial version or test before purchase​

Currently, there is no demo site for the modules and there is no way to test the module before purchasing.
Please read the module documentation and the FAQ page before purchasing the module.

However:

Marketplace order invoice​

The invoice for the order can be downloaded from My Profile Purchase History in your Marketplace account.

Warning

The invoice does not supply the VAT or address of the seller as this is not required by the Marketplace at the current time.

Marketplace order invoice in Commerce Marketplace Help Center.

Compatibility​

System requirements​

Warning

Please ensure that your test environment meets the system requirements of your Magento Open Source or Adobe Commerce version.

Marketplace compatibility and maintenance policy​

Adobe Commerce Marketplace compatibility and maintenance policy in Commerce Marketplace Help Center.

Edition and version compatibility​

Information about a module compatibility with an edition or version of Magento Open Source or Adobe Commerce can be found on the module Marketplace page in Technical Specifications Adobe Commerce platform compatibility section.

Module compatibility with third-party themes​

The modules are compatible with themes based on default themes Blank or Luma.

Hyvä themes compatibility​

Modules are currently not compatible with Hyvä themes.
See Compatibility Module Tracker.

Breeze themes compatibility​

Modules are currently not compatible with Breeze themes.
See compatible modules.

(Un)install, update or (dis)enable a module​

Add or update Access Keys for Marketplace​

composer config --auth http-basic.repo.magento.com <Public Key> <Private Key> # Add or update Access Keys in auth.json
# e.g. composer config --auth http-basic.repo.magento.com 39b747b8ab1d624582bb3n1a09deb489 31b9fce4cb78f523fd34aa3abb90c89c

Get your authentication keys in the Adobe Commerce Documentation.

Get installed module version​

composer show vct/<package name> | grep versions
# e.g. composer show vct/productinfoswitcher | grep versions

Get available modules list​

Execute the following command to show all available for install VCT modules:

composer show --available vct/* # Get available VCT modules list

Get available module versions​

Info

Information about a current module version can be found on the module Marketplace page in Technical Specifications Current Version section.

  • Log in to your Marketplace account that purchased the module.
  • Available module versions are listed in the selector on My Profile My Purchases page.

OR

Execute the following command:

composer show --available vct/<package name>
# e.g. composer show --available vct/simpleproducturl

Install a module​

Use Composer to install the module or get the code for review:

composer config --auth http-basic.repo.magento.com <Public Key> <Private Key> # Add or update Access Keys in auth.json
# e.g. composer config --auth http-basic.repo.magento.com 39b747b8ab1d624582bb3n1a09deb489 31b9fce4cb78f523fd34aa3abb90c89c
  • Execute the following commands:
composer require vct/<module_name> # Install the module using Composer
bin/magento setup:upgrade --safe-mode=1 # Update the database schema and data
bin/magento setup:static-content:deploy --force # Deploy static view files
  • The module was installed in vendor/vct directory.
Info

Optional execute in production mode:

bin/magento setup:di:compile # Recompile the code in production mode

Get your authentication keys and install an extension in the Adobe Commerce Documentation.

Install a specific module version​

Tip

Whenever possible, always use the latest version of the module!

Use Composer to install a specific module version or get the code for review:

  • Log in to your Marketplace account that purchased the module.
  • Available module versions are listed in the selector on My Profile My Purchases page.
  • Execute the following commands after specifying the <package name> and the <version> you need:
composer require vct/<package name>:<version> # Install the module using Composer
# e.g. composer require vct/simpleproducturl:2.0.1
bin/magento setup:upgrade --safe-mode=1 # Update the database schema and data
bin/magento setup:static-content:deploy --force # Deploy static view files
  • The module was installed in vendor/vct directory.
Info

Optional execute in production mode:

bin/magento setup:di:compile # Recompile the code in production mode

Install an extension in the Adobe Commerce Documentation.

Uninstall a module​

Execute the following commands to uninstall a module:

bin/magento module:uninstall Vct_<ModuleName> # Uninstall module
# e.g. bin/magento module:uninstall Vct_ChangeSkuDynamically
bin/magento setup:upgrade --safe-mode=1 # Update the database schema and data
bin/magento setup:static-content:deploy --force # Deploy static view files

Uninstall modules in the Adobe Commerce Documentation.

Update a module​

Use Composer to update the module or get the code for review:

composer require --update-with-dependencies vct/<package name> # Update the module using Composer
# e.g composer require --update-with-dependencies vct/simpleproducturl
bin/magento setup:upgrade --safe-mode=1 # Update the database schema and data
bin/magento setup:static-content:deploy --force # Deploy static view files

Execute only in production mode:

bin/magento setup:di:compile # Recompile the code in production mode

Upgrade an extension in the Adobe Commerce Documentation.

Enable a module​

Execute the following commands to disable a module:

bin/magento module:enable --clear-static-content --force Vct_<ModuleName> # Enable the module
# e.g. bin/magento module:enable --clear-static-content --force Vct_ProductInfoSwitcher
bin/magento setup:upgrade --safe-mode=1 # Update the database schema and data

Module enable, disable in the Adobe Commerce Documentation.

Disable a module​

Execute the following commands to disable a module:

bin/magento module:disable --clear-static-content --force Vct_<ModuleName> # Disable the module
# e.g. bin/magento module:disable --clear-static-content --force Vct_ProductInfoSwitcher

Module enable, disable in the Adobe Commerce Documentation.

Getting a module as ZIP archive​

Warning

The only recommended way to install or update module is using Composer.

If you require the source code in ZIP archive for any reason, please contact me by email vct.vendor@gmail.com.

Issues​

Could not find a matching version of package​

Issue
Could not find a matching version of package <vct/package name>. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).
Possible fix 1
  • Log in to your Marketplace account that purchased the module.
  • Ensure that you have used the correct Access Keys for authentication (in auth.json) from the account where you purchased the module.
  • Ensure that Access Keys are enabled.

Manage your authentication keys in the Adobe Commerce Documentation.

Possible fix 2
  • Get a Composer version using command:
composer --version
composer self-update --2
Possible fix 3

Clear cache of Composer using command:

composer clear-cache
Possible fix 4
composer.json
...
    "repositories": [
        {
            "type": "composer",
            "url": "https://repo.magento.com/"
        }
    ],
...
  • Add repo.magento.com repository if it is missing.

Support for Composer 1 is deprecated​

Issue
Warning from https://repo.packagist.org: Support for Composer 1 is deprecated and some packages will not be available. You should upgrade to Composer 2.

Deprecating Packagist.org support for Composer 1.x in Packagist.org blog.

Possible fix 1

Migrate Composer version 1 to version 2 using command:

composer self-update --2
Possible fix 2

Clear cache of Composer using command:

composer clear-cache

Magento configuration​

Flush Magento Cache​

Important

Flush Magento Cache in System Cache Management after configuration change!

Clean and flush cache types in the Adobe Commerce Documentation.

Restore default settings​

Tip

Use Use System Value / Use Default / Use Website checkbox to the right of the setting to set the default value.

Use system value in the Adobe Commerce Documentation.

Module localization and translation​

Almost every text string in VCT modules can be translated into any language:

  • Copy the module's default translation dictionary for the US locale vendor/vct/<package name>/i18n/en_US.csv.
  • Rename the default translation dictionary to the required locale e.g. de_DE.csv.
  • The translation dictionary has the following structure:
"Source string","Translated string"
  • To do the translation, leave the Source string entry unmodified, and translate the Translated string e.g.:
"Add to Cart","Zum Warenkorb hinzufügen"
"Address","Adresse"
"Address %1 of %2","Adresse %1 von %2"
  • Flush Magento Cache in System Cache Management afterwards.

Translations in the Adobe Commerce Documentation.

Configurable products configuration​

  • A configurable product allows the customer to choose options from Dropdown, Multiple Select, Visual Swatch and Text Swatch input types.
  • Configurable child products can be Simple or Virtual products without custom options.
  • The thumbnail image in the shopping cart can be set to display the image from the configurable product record or from the product variant.
  • Swatch attributes can be configured to not display corresponding simple product images when the swatch is selected by setting the Update Product Preview Image option value to No in Stores ATTRIBUTES Product <Attribute> Attribute Properties.
  • By default, the theme controls how the Image Gallery behaves when a customer switches between product variants:
    • Blank theme replaces the main product image with the image of the selected variant.
    • Luma theme prepend the selected variant images to the configurable product images.

Things to remember about configurable products in the Adobe Commerce Documentation.