When take the view of the product view in Magento, some product pages shows blank page but other product pages are working fine. This blog try to explore some solution for this

Solutions:

When one get issues like such as the blank page for some of the product view page, check the each of functions used in the product view page. When checking the function, there is a possibility that one can find the PHP functions of the mbstring extension like mb_detect_encoding().

Then check the PHP environment through the phpinfo(). From the displayed list of the PHP extension, probably one couldn’t see the mbstring PHP extension.

Good idea to check with server support team for installing and enabling the mbstring extension. After it is enabled, the product view page of all products should work fine.

Some of the Magento extensions used the mbstring php function. For eg: Technooze magento module has one feature like display Meta Description Tag on Product View Page. In this, one of the mbstring PHP function named mb_detect_encoding() is used.

Installation ofthe 3rdparty magemonkeymailchimp module in magento 1.7.0.2, results in an error message in backend tab “Newsletter->Mailchimp->Ecommerce 360 Orders ->Ecommerce360 API Orders”.

The error message can be;

Solution:

Receives a wrong output n magento when saving the date of birth as 01.01.1970 during the customer registration OR updating the customer information.

Solutions:


if(strtotime($date) == "0"){
$this->setTime($date);
}
Then the function will be:
public function setDate($date)
{
//01.01.1970 – DOB issue -start
if(strtotime($date) == "0"){
$this->setTime($date);
}
//01.01.1970 – DOB issue -end
else{
$this->setTime($date ? strtotime($date) : false);
}
$this->setData('date', $date);
return $this;
}


At first, we need to find where the export filters are located. Going through Magento core we can understand that export filters are stored in the form of array inside load () in:


…\app\code\core\Mage\Catalog\Model\Convert\Adapter.php

Look for $attrFilterArray in load(), in that we can see:

$attrFilterArray = array();
$attrFilterArray ['name'] = 'like';
$attrFilterArray ['sku'] = 'startsWith';
$attrFilterArray ['type'] = 'eq';
$attrFilterArray ['attribute_set'] = 'eq';
$attrFilterArray ['visibility'] = 'eq';
$attrFilterArray ['status'] = 'eq';
$attrFilterArray ['price'] = 'fromTo';
$attrFilterArray ['qty'] = 'fromTo';
$attrFilterArray ['store_id'] = 'eq';


Suppose that we need to add a new export filter, let it be country of manufacture, an attribute of product, what we need to do is simple add that attribute just as shown below.


$attrFilterArray = array();
$attrFilterArray ['name'] = 'like';
$attrFilterArray ['country_of_manufacture'] = 'like';
$attrFilterArray ['sku'] = 'startsWith';
$attrFilterArray ['type'] = 'eq';
$attrFilterArray ['attribute_set'] = 'eq';
$attrFilterArray ['visibility'] = 'eq';
$attrFilterArray ['status'] = 'eq';
$attrFilterArray ['price'] = 'fromTo';
$attrFilterArray ['qty'] = 'fromTo';
$attrFilterArray ['store_id'] = 'eq';


The syntax for adding is:


$attrFilterArray ['attributecode'].


Important: we should not edit any core files or templates; this example is demonstrated by editing the core files/templates. We need to override the admin module.

Now, half of the work is done. Next we need to edit the phtml file. For that go to:

..\app\design\adminhtml\default\default\template\system\convert\profile

And open wizard.phtml file. Add the following code inside


<div class="profile_entity_type_product">
<span class="field-row">
<label for="product_filter_country_of_manufacture"><?php echo $this->__("Country of manufacture:") ?></label>
<input id="product_filter_country_of_manufacture" name="gui_data[product][filter][country_of_manufacture]" value="<?php echo $this->getValue('gui_data/product/filter/country_of_manufacture') ?>"/>
</span>

Now check the output and it will work perfectly…

Foradding a category filter, the process is comparatively more complex. There will be a change in logic of load() in Adapter.php. For that, a admin module must be created and Adapter.php must be overrided in such a way that it incorporates or uses the category resource model :
Mage::getResourceModel('catalog/category_collection')Thank you for reading and please share your valuable comments…

Before going to optimize, please make sure that ‘Search Type’ is ‘Like’. It can be determined taking a look at:

System ->Configuration ->Catalog ->Search Type


Important: If we want to see any changes in frontend search results please make sure the search data is re-indexed.

Open the file:

..\core\Mage\CatalogSearch\Model\Resource\Fulltext.php

Inside the prepareResult( ), see the code from line 343. The logic which we are going to change is in that particular line. Take a look at that part:

$like[ ] = $helper->getCILike('s.data_index', $word, array('position' => 'any'));

Here we can notice the parameter array(‘position’=>’any’).This means that Magento default search will search the word in such a way that the particular position of word will be anywhere .In SQL terms, we can say it will be like: %searchterm%

We can change that to ‘start’ or ‘end’ as defined in the class:

switch ($options['position']) {
case 'any':
$value = '%' . $value . '%';
break;
case 'start':
$value = $value . '%';
break;
case 'end':
$value = '%' . $value;
break;
}


It is self explanatory and in SQL terms the ‘start’ and ‘end’ can be defined as searchterm% and %serachterm respectively.

In Fulltext.php, we can optimize the search further in such a way that AND logic can be used. See the code below:


if ($like) {
$likeCond = '(' . join(' OR ', $like) . ')';
}
It can be changed to:
if ($like) {
$likeCond = '(' . join(' AND ', $like) . ')';
}

So that the magento will search for items containing exactly all the terms.

Thank you for reading… Please share your valuable comments