A recurring question among our customers when front-end issues arise, blocking customizations can help investigate the root causes of many problems. With that in mind, this topic aims to provide a simple tutorial on how to block these customizations in a straightforward way.
First, it’s worth pointing out that this tutorial is based on a tool called DevTools.
What is DevTools?
Chrome DevTools is a set of web developer tools built directly into the Google Chrome browser. These tools allow you to inspect the rendered HTML (DOM) and the network activity of your pages.
How do I block my store’s customizations using this tool?
1. To open DevTools, right-click on the page and select Inspect. Alternatively, you can press Command + Option + C (Mac) or Control + Shift + C (Windows, Linux, Chrome OS).
2. Click on the “Network” tab:
Note: if your DevTools is in a different language, look for the equivalent tab name in your language.
3. Then right-click on the central area of DevTools, and select “Block request URL”:
4. After doing that, at the bottom of DevTools click on the “Network request blocking” tab and then the 
:
5. Now you’ll need to add the following files to be blocked:
*gtm*
*/files/*.css
*/arquivos/*.css
*/files/*.js
*/arquivos/*.js
*custom*
checkout*-custom.*
checkout6-custom.js
6. Now just select all the files added in the step above and refresh the page. Your page will then be free of customizations and will look something like this:
If you’d like to do this via LID, we have documentation with a tutorial on how to do so:
If you have any further questions on the topic, feel free to ask here or open a new topic referencing this one! 