{"section":"faq","requestedLocale":"en","requestedSlug":"blocking-customizations-to-troubleshoot-front-end-issues","locale":"en","slug":"blocking-customizations-to-troubleshoot-front-end-issues","path":"docs/en/faq/shopping/blocking-customizations-to-troubleshoot-front-end-issues.md","branch":"main","content":"> ⚠️ Tutorial valid only for Legacy CMS Stores.\n\nIn this article, you will learn how to find the origin of the problem. The first step is to block front-end customizations. Depending on the website’s response, you will be able to identify whether the problem is in the information that VTEX delivers natively or in your page customization.\n\nTo do that, we will show you how to remove the customizations using a Chrome native tool: **DevTools**. You can also use Chrome’s apps and extensions for removing them. However, the native solution tends to be more secure and efficient.\n\n## How to configure DevTools\n\n1. To open DevTools, open Chrome and click **F12** or **right-click** anywhere on the page and select **Inspect**.\n\n![Customizations1](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/en/faq/shopping/blocking-customizations-to-troubleshoot-front-end-issues_1.png)\n\n2. Search for the **Request Blocking** function to block all customizations made via CSS, JavaScript, and Google Tag Manager. Click on the three vertical dots on the top right of the page, as indicated in the image below. Select **More Tools** and then **Request Blocking**.\n\n![Customizations2](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/en/faq/shopping/blocking-customizations-to-troubleshoot-front-end-issues_2.png)\n\n3. A box will be displayed, as in the image below:\n\n![Customizations3](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/en/faq/shopping/blocking-customizations-to-troubleshoot-front-end-issues_3.png)\n\n4. Click on the **Request Blocking** tab.\n\nNow you will determine the features you want to block. This configuration must be done only once.\n\n5. Click on the “+” signal and include the following items one by one:\n- `*/arquivos/*.js`\n- `*/files/*js`\n- `*/arquivos/*.css`\n- `*/files/*.css`\n- `*gtm.js*`\n\nThe box will finally be displayed as in the image below:\n\n![Customizations4](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/en/faq/shopping/blocking-customizations-to-troubleshoot-front-end-issues_4.png)\n\nPlease remember that this configuration must be done only __once__.\n\n## How to block customizations using DevTools\n\n1. Select the checkbox **Enable request blocking** and enable all checkboxes.\n\n2. This configuration will be set by default, with all options for blocking enabled.\n\n![Customizations5](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/en/faq/shopping/blocking-customizations-to-troubleshoot-front-end-issues_5.png)\n\n3. Now refresh the page by clicking on **F5**. The page will be displayed without custom components.\n\n![Customizations6](https://cdn.statically.io/gh/vtexdocs/help-center-content/refs/heads/main/docs/en/faq/shopping/blocking-customizations-to-troubleshoot-front-end-issues_6.png)\n\n4. To view customizations again, deselect the checkbox **Enable request blocking** and refresh the page.\n\nCheck if the unexpected behavior you initially observed only happens when customization is enabled. If that is the case, contact the team responsible for your front-end to investigate the problem.\n\nIf the unexpected behavior persists even after blocking customizations, open a ticket to the VTEX support explaining the problems you are experiencing."}