Magento – Magento 2 code validation Unescaped output detected warning

magento2validation

I've created a Magento2 Module, When I validate the PHP code, am getting the Unescaped output detected.

I got the following solutions from that blog /* @noEscape */ moreover, it's not fixing the problem.

I want to know how to fix this issue, and need some detailed technical explanation of the /* @noEscape */

Best Answer

You can solve using This

For HTML Attribute

<?= $block->escapeHtmlAttr($var) ?>

or

<?= $block->escapeHtmlAttr("Demo text") ?>

For URL

<?= $block->escapeUrl($block->getUrl('*/*/forgotpasswordpost')) ?>

For used insted of echo

<?= $block->escapeHtml('Name') ?>

<?= $block->escapeHtml($var) ?>

<?= /* @noEscape */ $var ?>

Note: Some time code is required then we not change in code so use this line

//@codingStandardsIgnoreStart

Your code 

//@codingStandardsIgnoreEnd

This is perform coding standard ignore this line

I Hope This Hepls You.

Related Solutions

Magento 2 – Error When Running bin/magento setup:upgrade After Creating Module

Simple, try the following commands. I have encountered this error, and I have overcome.

rm -rf var/di/* 
rm -rf pub/static/_cache/* 
rm -rf pub/static/frontend/*
rm -rf var/generation/* 
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf var/view_preprocessed/*

In magento 2

var/di has been replaced by generated/metadata

var/generation has been replaced by generated/code

I switched to Developer Mode, and deleted the below files.

rm -rf generated/metadata/* 
rm -rf pub/static/_cache/* 
rm -rf pub/static/frontend/*
rm -rf generated/code/* 
rm -rf var/cache/*
rm -rf var/page_cache/*
rm -rf var/view_preprocessed/*

never delete pub/static/.htaccess. putting star *at the end does not delete .htaccess file in the folder.

you may also need to run setup di compile to optimize and regenerate magento2 file system.

bin/magento setup:di:compile
bin/magento indexer:reindex

Magento – Magento 2: Zend_Http_Exception Invalid header line detected

We had the same problem which was caused by the litemage caching extension. Reinstalling with the latest version of litemage solved the problem you mentioned.

But there is another problem when we tried to integrate m2 with Linnworks and the same error occurred in exception log when we tried to activate the integration. Frustrated!

Best Answer

Related Solutions

Magento 2 – Error When Running bin/magento setup:upgrade After Creating Module

Magento – Magento 2: Zend_Http_Exception Invalid header line detected

Related Topic