Cause Of Php Error

Hi

I am trying to find the cause of this PHP error, It is a multi store installation but none of the stores have product features setup.

[16-Oct-2018 07:38:26 Europe/London] PHP Notice: Undefined index: price in /home/mydomain/public_html/app/controllers/frontend/product_features.php on line 62

any guidlines,

I have updated to the latest release

Alan

Hi

I am trying to find the cause of this PHP error, It is a multi store installation but none of the stores have product features setup.

[16-Oct-2018 07:38:26 Europe/London] PHP Notice: Undefined index: price in /home/mydomain/public_html/app/controllers/frontend/product_features.php on line 62

any guidlines,

I have updated to the latest release

Alan

Hello!

It happens when customer adds product to comparison list. Do you have any modification related to product price?

I have the same error going on for years. It is somehow stuck in trying to add an item that has long since been disabled/deleted to the compare list. I've learned to ignore it and it's present on many of my customer sites too. I added some diagnostics to the controller to sew what product is was trying to get a price for and that product does not exist.

I have the same error going on for years. It is somehow stuck in trying to add an item that has long since been disabled/deleted to the compare list. I've learned to ignore it and it's present on many of my customer sites too. I added some diagnostics to the controller to sew what product is was trying to get a price for and that product does not exist.

Thanks for that, It has been, I take it I can ignor this one. But I do have anohter error which has started showing randomly every few hours since I updated to the lates version.

[17-Oct-2018 18:48:24 Europe/London] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 39661536 bytes) in /home/mydomain/public_html/app/Tygh/SmartyEngine/Filters.php on line 357

I am not a developer so really don't know where to start looking

Alan

Have your hosting increase your PHP 'memory_limit' to at least 64M. Looks like you currently have it set to 32M

Have your hosting increase your PHP 'memory_limit' to at least 64M. Looks like you currently have it set to 32M

Hi

Thanks for the message, That is not the issue, my memory limits are set as 128M, I have changed this to 256M to see if it will make a difference.

Alan

The error states that you had it at 256M so you should probably increase it to 512M.

The error states that you had it at 256M so you should probably increase it to 512M.

Thanks for the info, I have changed the setting to 512M, Will have to wait to see if this cures the issue.

Alan

Sorry, missread on my part (eyes fail me sometimes). Yes, you ate up 256M of memory.

Most commonly, this is a reasult of a either a large export or import. All that data is held in memory before/during processing or writing out to a CSV file.

Big Kick:

Latest version of CS Cart and this still happens. CS Cart is parsing more php errors. Biggest issue is that with a high number of visitors so many errors will be parsed that it will slow down.

Undefined index: price in /home/*******/domains/********/public_html/app/controllers/frontend/product_features.php on line 62'

I have the same issue, did you find what it causes it?

I am on 4.11.5 with php7.4

It is the only php error i get

I have the same issue, did you find what it causes it?

I am on 4.11.5 with php7.4

It is the only php error i get

***sorry for the second message i mean I have this error:

Undefined index: price in /home/mydomain/public_html/app/controllers/frontend/product_features.php on line 62

Big Kick:

Latest version of CS Cart and this still happens. CS Cart is parsing more php errors. Biggest issue is that with a high number of visitors so many errors will be parsed that it will slow down.

Undefined index: price in /home/*******/domains/********/public_html/app/controllers/frontend/product_features.php on line 62'

Normally not a performance issue since the error_log is cached and it's actually the PHP binary that is detecting the 'Notice' notification to the error_log. These issues have been reported for years. There is still an undefined index error that comes from the session handler periodically that I reported nearly 10 years ago.

Given it is doubtful they will every get addressed, you might turn off logging of the notices by using the error_reporting() function to not report E_NOTIFY. I.e.

error_reporting(E_ALL & ~E_NOTICE);