error generated from missing LARGE_IMAGE_WIDTH constant

[earmsby]

One of my clients' estores is generating many error log files due to missing constant: LARGE_IMAGE_WIDTH

Here's an example of the error:

PHP Warning: Use of undefined constant LARGE_IMAGE_WIDTH - assumed 'LARGE_IMAGE_WIDTH' (this will throw an Error in a future version of PHP) in /path/to/store/includes/templates/MYTEMPLATE/templates/tpl_modules_main_product_image.php on line 24.

I did some digging in Developers Toolkit to see where this constant should be set and found some code in includes/classes/observers/FualSlimboxObserver.php which looks like it should be setting this constant:

/ The constants LARGE_IMAGE_WIDTH/HEIGHT are supplied by neither Zen Cart nor Image Handler -- they're a
// LightBox 'legacy', I believe.  In any case, need to deal with the condition where those constants
// haven't been defined previously, using the IH defaults as fall-back values.
//
if (!defined('LARGE_IMAGE_WIDTH')) {
    define('LARGE_IMAGE_WIDTH', (defined('LARGE_IMAGE_MAX_WIDTH')) ? LARGE_IMAGE_MAX_WIDTH : 750);
}
if (!defined('LARGE_IMAGE_HEIGHT')) {
    define('LARGE_IMAGE_HEIGHT', (defined('LARGE_IMAGE_MAX_HEIGHT')) ? LARGE_IMAGE_MAX_HEIGHT : 550);
} 

The client's shop does have Image Handler 5 installed. Wondering if I can set this constant somewhere else at least temporarily to stop the barrage of error log files. But also wonder why this doesn't seem to be firing

Any advice on how to track this error down and resolve it?

[DrByte]

I'd start with exploring: in what ways has that template's tpl_modules_main_product_image.php file been modified from the original template_default version
... and why.

[earmsby]

Thanks. I should also have mentioned that the template uses zen colorbox plugin. So this file in the custom template folder is modified with that.

[DrByte]

Thanks. I should also have mentioned that the template uses zen colorbox plugin. So this file in the custom template folder is modified with that.

If that plugin expects that constant to be defined (and probably via an admin config switch it adds during its installation) then perhaps there's something missing from installation steps performed?

[mc12345678]

Thanks. I should also have mentioned that the template uses zen colorbox plugin. So this file in the custom template folder is modified with that.

If that plugin expects that constant to be defined (and probably via an admin config switch it adds during its installation) then perhaps there's something missing from installation steps performed?

Check to be sure that the plugin is up-to-date as the current software (available from github at the moment) from what I can tell also prevents log generation using the same test for the constant being defined..

The use of that variable is/was a carry over (from what I've been able to tell) from image handler. At least with zen_colorbox when the code was pulled out more to try to co-exist with other programs it also remained present. There is a suggested SQL to create the constant, but properly handling/use of the variable will reduce the log generation.

Looks like I have a few plugins that need to get updated to the forum.