Debug file in /logs - PHP Warning: Creating default object from empty value

[RixStix]

Will that same code work for the same error generated on line 1041?

PHP Warning:  Creating default object from empty value in /home/XXXXXX/public_html/XXXXXX/categories.php on line 1041

According to DrByte:
www.zen-cart.com/showthread.php?214369-myDEBUG-after-update-to-php-5-4-31

It's harmless.
It's a PHP 5.4 issue, where the use of an object element (in this case $pInfo) is assumed to already exist, but in this specific case it doesn't yet. So, the message is telling you that it created the object on-the-fly for you.

[lat9]

Will that same code work for the same error generated on line 1041?

PHP Warning:  Creating default object from empty value in /home/XXXXXX/public_html/XXXXXX/categories.php on line 1041

According to DrByte:
www.zen-cart.com/showthread.php?214369-myDEBUG-after-update-to-php-5-4-31

The "stock" version of /YOUR_ADMIN/categories.php has only 1032 lines, so I can't answer the first question without seeing what's 'around' that line in your version.

While it's a harmless message, my concern is that these "harmless" reports will make people complacent about seeing debug-log files such that they ignore an "important" report.

[RixStix]

The "stock" version of /YOUR_ADMIN/categories.php has only 1032 lines, so I can't answer the first question without seeing what's 'around' that line in your version.

While it's a harmless message, my concern is that these "harmless" reports will make people complacent about seeing debug-log files such that they ignore an "important" report.

I think it is the same line of code. QuickQuantityUpdate referenced in the other thread adds a few lines toward the top which probably caused the lines to shift down that much.

/admin/categories.php

// Split Page LINE 1038
if ($products_query_numrows > 0) {
  if (empty($pInfo->products_id)) {
    $pInfo->products_id= $pID;
  }
?>
            <td class="smallText" align="center"><?php echo $products_split->display_count($products_query_numrows, MAX_DISPLAY_RESULTS_CATEGORIES, $_GET['page'], TEXT_DISPLAY_NUMBER_OF_PRODUCTS) . '<br>' . $products_split->display_links($products_query_numrows, MAX_DISPLAY_RESULTS_CATEGORIES, MAX_DISPLAY_PAGE_LINKS, $_GET['page'], zen_get_all_get_params(array('page', 'info', 'x', 'y', 'pID')) ); ?></td>

<?php
}
// Split Page LINE 1048

Yes, I agree since I have started ignoring/deleting the myDebug files since most have been "Ignore them". I thought that I was being helpful in reporting the logs but it doesn't appear helpful at all. PayPal and this one are most frequent. There's really no dedicated area in the forum for questions related to myDebug, the questions tend to get sprinkled around.

[lat9]

I think it is the same line of code. QuickQuantityUpdate referenced in the other thread adds a few lines toward the top which probably caused the lines to shift down that much.

/admin/categories.php

// Split Page LINE 1038
if ($products_query_numrows > 0) {
  if (empty($pInfo->products_id)) {
    $pInfo->products_id= $pID;
  }
?>
            <td class="smallText" align="center"><?php echo $products_split->display_count($products_query_numrows, MAX_DISPLAY_RESULTS_CATEGORIES, $_GET['page'], TEXT_DISPLAY_NUMBER_OF_PRODUCTS) . '<br>' . $products_split->display_links($products_query_numrows, MAX_DISPLAY_RESULTS_CATEGORIES, MAX_DISPLAY_PAGE_LINKS, $_GET['page'], zen_get_all_get_params(array('page', 'info', 'x', 'y', 'pID')) ); ?></td>

<?php
}
// Split Page LINE 1048

Yes, I agree since I have started ignoring/deleting the myDebug files since most have been "Ignore them". I thought that I was being helpful in reporting the logs but it doesn't appear helpful at all. PayPal and this one are most frequent. There's really no dedicated area in the forum for questions related to myDebug, the questions tend to get sprinkled around.

Yes, the change that I posted should replace the same fragment in your (larger) file!

I believe that your reporting of these warnings is quite helpful; many times a warning in one PHP version leads to an error in a later version. I also agree that having a dedicated "I got this debug-log, what does it mean?" forum would be helpful.