Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Well this is magento core code so i do expect some wrong value getting into $key variable from outside of this code.</p> <p>You can try to log the $key variable and check if it is an array.</p> <p><strong>Something like:</strong></p> <p>Mage::log(print_r($key,true), null, 'mycustomerror.log', true);</p> <p>or</p> <p>Mage::log($key, null, 'mycustomerror.log', true);</p> <p>If you want a better answer you should tell us when this notice is generated and the modules you are using.</p> <h1>After extra info</h1> <p>Well it is a guess because the information you gave me is not much. But your logs shows the following:</p> <pre><code>2013-01-17T16:52:36+00:00 DEBUG (7): Array ( [0] =&gt; CATALOG_PRODUCT_HIGHLIGHT [1] =&gt; 1 [2] =&gt; default [3] =&gt; a058 [4] =&gt; 0 [5] =&gt; highlight/product/grid.phtml [6] =&gt; 8 [7] =&gt; 4 [8] =&gt; Array ( ) [9] =&gt; Array ( ) [10] =&gt; Array ( ) [11] =&gt; Aanbiedingen [12] =&gt; highlight-special [13] =&gt; special_from_date,special_to_date [14] =&gt; -special [15] =&gt; product_special ) </code></pre> <p>I think the problem is:</p> <pre><code>[8] =&gt; Array() [9] =&gt; Array() [10] =&gt; Array() </code></pre> <p>When they are imploded they will give the notice.</p> <p><strong>SEE:</strong> <a href="http://codepad.viper-7.com/qb5tIW" rel="nofollow">http://codepad.viper-7.com/qb5tIW</a></p> <p>I would check the CATALOG_PRODUCT_HIGHLIGHT (highlight/product/grid.phtml)</p> <p>You can navigate your site so that the highlight/product/grid.phtml is loaded and see if this call is indeed putting that notice in your log files.</p> <p>good luck !</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload