Step 1: are you sure that it’s a bug?¶

Sometimes, it’s quite clear that the behaviour you experience is a bug. But it is not always the case. Some behaviours can occur because you missed something (for instance a permissions misconfiguration), and the PIM just works as designed.

If you have doubts, please have a look at the following resources. If not, go to the next step.

• The PIM knowledge base
• The PIM user guides

Step 2: is your computer ready to use the PIM?¶

There are some client side requirements to use the PIM. Please check that everything is OK by looking at Client side configuration and compatibilities.

Step 3: are the system requirements still OK?¶

Maybe something has been changed in your server. You can check that by running the following command:

cd /path/to/your/pim/
php bin/console pim:installer:check-requirements

In addition, check that:

• The Xdebug PHP extension is well deactivated.
• The PIM commands are well run in prod mode instead of dev mode (See: Symfony documentation: Selecting the Environment for Console Commands)
• Your crontab scheduled PIM commands are not launched too frequently

Step 4: what about your infrastructure?¶

Depending on your infrastructure, you may need to check some points:

• Make sure you are not experiencing latency issues on your local network.
• Make sure you don’t have an issue with one of your network equipments. For instance with a proxy server.

Step 5: is your PIM up-to-date?¶

Make sure that you applied the latest patches available for your PIM version. You can check your current PIM version at the bottom of the PIM login or dashboard pages.

Step 6: are your additional bundles up-to-date?¶

As for the PIM it’s important to check that the additional bundles you use (for instance: EnhancedConnectorBundle, CustomEntityBundle, InnerVariationBundle…) are up-to-date.

If you need assistance, please refer to each bundle’s documentation.

Step 7: are your assets properly deployed?¶

From a technical point of view, assets are all the javascript, css and media files used by the PIM itself, by its dependencies, and eventually by your custom developments.

To make sure everything is OK, you can run the following commands:

cd /path/to/your/pim/
rm -rf ./web/bundles/* ./web/css/* ./web/js/*
php bin/console pim:install:assets --env=prod
php bin/console assets:install --symlink web
yarn run webpack

One last thing, clear your browser’s cache:

• If you use Chrome, see: Chrome documentation: Clear cache and cookies.
• If you use Firefox, see: Firefox documentation: How to clear the Firefox cache.
• If you use another browser, be aware this one isn’t officially supported.

Step 8: did you clear the cache?¶

Clear the PIM cache (also known as “Symfony cache”) by running the following commands:

cd /path/to/your/pim/
php bin/console cache:clear --env=prod --no-warmup

Step 9: did you consider the volume of your catalog?¶

Each catalog is unique. How many channels, locales, attributes, families, categories, products and users do you have? These values may had increased drastically since you began using your PIM.

Most of this information can be found on the PIM system information screen (under System > System information).

Once the calculations made, please have a look at our Scalability Guide and Performances Guide.

Step 10: did you customize your PIM?¶

Disable all custom developments by commenting them in the “AppKernel.php” file /path/to/your/pim/app/AppKernel.php.

// your app bundles should be registered here
// new YourCompagny\Bundle\AppBundle\YourCompagnyCustomBundle(),

And then, re-apply Step 7: are your assets properly deployed? and Step 8: did you clear the cache?

Alternatively, you can check if the issue is reproducible on Demo website (only for the latest PIM version).

Does the bug persist?¶

Sorry to hear that. It seems it’s Bug qualification time.