Jump to content

More errors


matchattaxoutlet
 Share

Recommended Posts

Hi Guys,

 

Just been trawling through my php_errorlog and came across the following error (amongst many)

 

 

25-Sep-2013 10:30:04 Europe/London] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxx/public_html/admin/sources/products.index.inc.php on line 1106
[25-Sep-2013 10:30:06 Europe/London] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxx/public_html/classes/ajax.class.php on line 163
[25-Sep-2013 10:30:06 Europe/London] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxx/public_html/admin/sources/products.index.inc.php on line 1088
[25-Sep-2013 10:30:06 Europe/London] PHP Warning:  implode() [<a href='http://docs.php.net/manual/en/function.implode.php'>function.implode.php</a>]: Invalid arguments passed in /home/xxxx/public_html/admin/sources/products.index.inc.php on line 1102

 

 

Also get lots of these in my system error logs after installing loyalty points mod. Noodleman says they are nothing to fret about. Is this the case?

 

File: [controller.index.php] Line: [0] "DELETE FROM plugin_customer_rewards WHERE related_order_number IN (SELECT * FROM (SELECT cart_order_id FROM cc4_CubeCart_order_summary WHERE status IN (1,4,5,6) AND cart_order_id IN (SELECT distinct(cr.related_order_number) FROM plugin_customer_rewards cr)) as a) " - Deadlock found when trying to get lock; try restarting transaction

 

 

Thanks in advance

Link to comment
Share on other sites

As you may have surmised, these errors don't crash the store.

 

To fix lines 1088, 1102, and 1106, in the file /admin/sources/products.index.inc.php, find near line 1047:

        if($options) {
            // Work out unique groups
            $key_id = -1;

Twelve lines later, find:

                $unique_groups[$key_id][$data['value_id']] = $data['value_id'];
            }
      }

Comment out the last closing brace:

//    } // Fix for no options processing

About 50 lines further down, find:

        $GLOBALS['smarty']->assign('OPTIONS_MATRIX', $smarty_data['option_matrix']);

After that line, add this:

        } // Fix for no options processing

I've not seen that specific ajax error -- a similar error, yes.

 

Try in the file /classes/ajax.class.php, line 162, from:

if (($dirs = $filemanager->findDirectories()) !== false) {

to:

if (is_array($dirs = $filemanager->findDirectories())) {
Link to comment
Share on other sites

  • 3 weeks later...

I have a similar issue on a fresh installation of 5.2.2 with no mods but after just taking a backup before upgrading to 5.2.4 i opened the error log and have loads of errors such as:

[17-Sep-2013 10:10:38 UTC] PHP Warning:  htmlentities() [<a href='http://docs.php.net/manual/en/function.htmlentities.php'>function.htmlentities.php</a>]: Invalid multibyte sequence in argument in /home/xxxxxxxx/public_html/classes/debug.class.php on line 193
[18-Sep-2013 11:21:40 UTC] PHP Warning:  Invalid Security Token in /home/xxxxxxxx/public_html/classes/sanitize.class.php on line 123
[18-Sep-2013 11:21:53 UTC] PHP Warning:  htmlentities() [<a href='http://docs.php.net/manual/en/function.htmlentities.php'>function.htmlentities.php</a>]: Invalid multibyte sequence in argument in /home/xxxxxxxx/public_html/classes/debug.class.php on line 193
[19-Sep-2013 11:12:31 UTC] PHP Warning:  htmlentities() [<a href='http://docs.php.net/manual/en/function.htmlentities.php'>function.htmlentities.php</a>]: Invalid multibyte sequence in argument in /home/xxxxxxxx/public_html/classes/debug.class.php on line 193
[19-Sep-2013 12:44:21 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/categories.index.inc.php on line 19
[19-Sep-2013 12:45:24 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/categories.index.inc.php on line 19
[19-Sep-2013 12:45:53 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/categories.index.inc.php on line 19
[19-Sep-2013 12:46:07 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/categories.index.inc.php on line 19
[19-Sep-2013 12:46:23 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/categories.index.inc.php on line 19
[19-Sep-2013 12:47:08 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1076
[19-Sep-2013 12:47:08 UTC] PHP Warning:  implode() [<a href='http://docs.php.net/manual/en/function.implode.php'>function.implode.php</a>]: Invalid arguments passed in /home/xxxxxxxx/public_html	color:#000;
 on line 1090
[19-Sep-2013 12:47:08 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1094
[19-Sep-2013 12:47:11 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1076
[19-Sep-2013 12:47:11 UTC] PHP Warning:  implode() [<a href='http://docs.php.net/manual/en/function.implode.php'>function.implode.php</a>]: Invalid arguments passed in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1090
[19-Sep-2013 12:47:11 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1094
[19-Sep-2013 12:47:11 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1076
[19-Sep-2013 12:47:11 UTC] PHP Warning:  implode() [<a href='http://docs.php.net/manual/en/function.implode.php'>function.implode.php</a>]: Invalid arguments passed in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1090
[19-Sep-2013 12:47:11 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1094
[19-Sep-2013 12:51:42 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 348
[19-Sep-2013 12:56:52 UTC] PHP Warning:  Invalid argument supplied for foreach() in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1076
[19-Sep-2013 12:56:52 UTC] PHP Warning:  implode() [<a href='http://docs.php.net/manual/en/function.implode.php'>function.implode.php</a>]: Invalid arguments passed in /home/xxxxxxxx/public_html/admin/sources/products.index.inc.php on line 1090
[19-S

This is just a small selection of the errors and they don't appear to be affecting the function of the store in any way but it's obviously a concern when you find hundreds of error messages :on2long:

Link to comment
Share on other sites

We agree. However, from an off-hand comment made by Devellion in the bug tracker that essentially said, "If the bug doesn't affect the outcome (user experience and valid transactions), it's priority is very low."

So are they anything to worry about?

Link to comment
Share on other sites

We agree. However, from an off-hand comment made by Devellion in the bug tracker that essentially said, "If the bug doesn't affect the outcome (user experience and valid transactions), it's priority is very low."

 

The problem IMHO with low priority error messages is that they make it harder to wade through the error log and spot the messages that ARE important, particularly when you don't know enough to know which are low and which are high priority.

Link to comment
Share on other sites

These error messages are to used after the fact. That is, if you experience something odd about CubeCart, something that is obviously not right, then we can look at the logs (forensics).

 

But this assumes you know how a properly functioning CubeCart store should behave.

Link to comment
Share on other sites

 

We agree. However, from an off-hand comment made by Devellion in the bug tracker that essentially said, "If the bug doesn't affect the outcome (user experience and valid transactions), it's priority is very low."

 

The problem IMHO with low priority error messages is that they make it harder to wade through the error log and spot the messages that ARE important, particularly when you don't know enough to know which are low and which are high priority.

 

Indeed! The messages 'suggest' to me that there is a problem with the code of the relevant file at the specified line and if like me you have no idea what any of it means it's quite worrying.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...