Skip to main content

Magento 2 issues with layouts

 Hi 

I came with new issue debugging if have xml tag not valid issue to find which file it is.

Some times we will get xml errors like 

1 exception(s): Exception #0 (Magento\Framework\Config\Dom\ValidationException):
Element 'referenceBlock', attribute 'remove': 'True' is not a valid value of the atomic
type 'xs:boolean'. Line: 1 Element 'referenceBlock', attribute 'remove': 'True' is not
a valid value of the atomic type 'xs:boolean'. Line: 2 Element 'referenceBlock', attribute
'remove': 'True' is not a valid value of the atomic type 'xs:boolean'. Line: 3


like this of errors we will get It's hard find which file it is if we did in any xml file we can easily locate if some done long days ago if got ticket to solve this is hard to find. Some will do in pages admin Layout Update XML section some one done core files based their flexible they will do but finding is hard so for this do below steps we will get error code based on that we can search ang solve it

more info that might help resolve this by identifying the file at fault.

Edit vendor/magento/framework/Config/Dom.php

Or it might be lib/internal/Magento/Framework/Config/Dom.php depending on your installation of Magento.


Find the public function _initDom($xml)

And add something like this before the normal validation check.

$verboseOutput = true;

if ($verboseOutput) {
if ($this->validationState->isValidationRequired() && $this->schema) {
$errors = $this->validateDomDocument($dom, $this->schema, $this->errorFormat);
if (count($errors)) {
var_dump($errors);
$matches = [];
preg_match("/Line: (\\d+)/", $errors[count($errors)-1], $matches);
$lineNumber = intval($matches[1]);
$lines = explode("\n", $xml);
echo "<h1>A validation error occured in an XML layout file</h1>";
$lineText = htmlentities($lines[$lineNumber-1]);
echo $lineText . "<br>";
echo "<pre>";
echo "grep -rnw ./app -e " . escapeshellarg(trim($lineText));
echo "</pre>";
die('Please grep or search files for the above and fix it as per Magento 2 validation.');
}
}
}

Before adding code :::

protected function _initDom($xml)
{
$dom = new \DOMDocument();
$useErrors = libxml_use_internal_errors(true);
$res = $dom->loadXML($xml);
if (!$res) {
$errors = self::getXmlErrors($this->errorFormat);
libxml_use_internal_errors($useErrors);
throw new \Magento\Framework\Config\Dom\ValidationException(implode("\n", $errors));
}
libxml_use_internal_errors($useErrors);
if ($this->validationState->isValidationRequired() && $this->schema) {
$errors = $this->validateDomDocument($dom, $this->schema, $this->errorFormat);
if (count($errors)) {
throw new \Magento\Framework\Config\Dom\ValidationException(implode("\n", $errors));
}
}
return $dom;
}


After Adding::

protected function _initDom($xml)
{
$dom = new \DOMDocument();
$useErrors = libxml_use_internal_errors(true);
$res = $dom->loadXML($xml);

$verboseOutput = true;
if ($verboseOutput) {
if ($this->validationState->isValidationRequired() && $this->schema) {
$errors = $this->validateDomDocument($dom, $this->schema, $this->errorFormat);
if (count($errors)) {
var_dump($errors);
$matches = [];
preg_match("/Line: (\\d+)/", $errors[count($errors)-1], $matches);
$lineNumber = intval($matches[1]);
$lines = explode("\n", $xml);
echo "<h1>A validation error occured in an XML layout file</h1>";
$lineText = htmlentities($lines[$lineNumber-1]);
echo $lineText . "<br>";
echo escapeshellarg(trim($lineText);
die('Please grep or search files for the above and fix it as per Magento 2 validation.');
}
}
}
if (!$res) {
$errors = self::getXmlErrors($this->errorFormat);
libxml_use_internal_errors($useErrors);
throw new \Magento\Framework\Config\Dom\ValidationException(implode("\n", $errors));
}
libxml_use_internal_errors($useErrors);
if ($this->validationState->isValidationRequired() && $this->schema) {
$errors = $this->validateDomDocument($dom, $this->schema, $this->errorFormat);
if (count($errors)) {
throw new \Magento\Framework\Config\Dom\ValidationException(implode("\n", $errors));
}
}
return $dom;
}

for me I got

<referenceBlock name="aheadworks.blog.recent.posts" remove="True" />

I removed remove true tag then it working it is added under cmspages 

After fixing please remove code and save 

And add something like this before the normal validation check.



Comments

Popular posts from this blog

Magento 2 product collection Filtering multi-select attribute values

  If you have multi-select attribute of product like below If you want filter value for this option Use below syntax to get product data: ->addAttributeToFilter('store_model', array('finset' => $params['store_model'])) finset key is used for multiselect attribute filter. $objectManager = \Magento\Framework\App\ObjectManager::getInstance(); $products = $objectManager->get('Magento\Catalog\Model\Product')         ->getCollection()         ->addAttributeToSelect('*')         ->addAttributeToSelect('store_brand')         ->addAttributeToSelect('store_model')         ->addAttributeToSelect('store_year')         ->addAttributeToFilter('store_brand', array('finset' => $params['store_brand']))         ->addAttributeToFilter('store_model', array('finset' => $params['store_model']))         ->ad...

Integrity constraint violation: 1052 Column 'created_at' in where clause is ambiguous

When trying to filter sales order grid with From and To dates it was redirecting to dashboard.after that again i tried to open sales order grind it is generating reports in reports file it showing. "Integrity constraint violation: 1052 Column 'created_at' in where clause is ambiguous" means it is finding a another created_at field. because when we adding or joining the other table then it has also a field named as created_at. So below is the  solution for this error. magento that created_at is of the main_table not of my custom table. Find the below code in the sales order grid.php file. $this->addColumn('created_at', array(            'header' => Mage::helper('sales')->__('Purchased On'),             'index' => 'created_at',             'type' => 'datetime',             'width' => '100px',         )); ...

What startSetup() and endSetup() methods actually does?

The startSetup() and endSetup() methods are used in setup scripts. They are often at the beginning and the end of an upgrade/install method, like in “upgrade()” method of Magento/Catalog/Setup/UpgradeData.php The question is “do you really need them?” Or does it just “look necessary”? This blog post explores what these functions do and then explains when you do and do not need to use these methods. Let’s see what these methods are doing. First, startSetup(): public function startSetup() {   $this->rawQuery("SET SQL_MODE=''");  $this->rawQuery("SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0");   $this->rawQuery("SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO'");   return $this;  } 1. Disable foreign keys check. It may be necessary in some rare cases (for example, in a case of cyclic references between tables), but it’s not needed in common situations. It even may lead to hiding real problems...