PHP warnings suddenly start appearing in the log folder

[delia]

Yesterday just as I uploaded one file, php warnings started appearing in the log folder. Not error messages, warnings. I've seen this happen in one other website and was never able to figure it out. In that case, I couldn't pinpoint when it started. I ended up simply writing a script to empty out those logs with a cron job to keep the number of files to a low amount.

In this case, I can pinpoint the minute this started and it happened at the same time that I uploaded some files. There is nothing in those files I uploaded that would start this as I have used them many times before.

php version is 5.3.29. Nothing looks out of the norm. There are two installations of zc that are connecting to one database and the warnings are showing in both log folders. I made no changes to one cart at all. The installation I uploaded the files to is a default set of 1.5.1 with some template changes - no core changes and the file I uploaded that has the same time stamp is just a template file. I tried removing it but it didn't stop this from happening.

I really have to figure this out this time - cart owner is not going to accept my stop gap measure of log file deletion.

[Design75]

Yesterday just as I uploaded one file, php warnings started appearing in the log folder. Not error messages, warnings. I've seen this happen in one other website and was never able to figure it out. In that case, I couldn't pinpoint when it started. I ended up simply writing a script to empty out those logs with a cron job to keep the number of files to a low amount.

In this case, I can pinpoint the minute this started and it happened at the same time that I uploaded some files. There is nothing in those files I uploaded that would start this as I have used them many times before.

php version is 5.3.29. Nothing looks out of the norm. There are two installations of zc that are connecting to one database and the warnings are showing in both log folders. I made no changes to one cart at all. The installation I uploaded the files to is a default set of 1.5.1 with some template changes - no core changes and the file I uploaded that has the same time stamp is just a template file. I tried removing it but it didn't stop this from happening.

I really have to figure this out this time - cart owner is not going to accept my stop gap measure of log file deletion.

What is the contents of the log file?

you can use this module myDEGUB Backtrace to obtain more information about erors

[frank18]

...In this case, I can pinpoint the minute this started and it happened at the same time that I uploaded some files. There is nothing in those files I uploaded that would start this as I have used them many times before.

Obvious questions:

What happens if you get these new files off the server?
Is it possible to do this without breaking cart functionality?
Are you still getting the same warnings after deletion of these new files?

[delia]

[11-Mar-2015 07:06:12 America/New_York] #1 substr() called at [/home/scrappin/public_html/includes/functions/functions_general.php:1039]
#2 zen_trunc_string() called at [/home/scrappin/public_html/includes/modules/scrappin_stuff/product_listing.php:178]
#3 include(/home/scrappin/public_html/includes/modules/scrappin_stuff/product_listing.php) called at [/home/scrappin/public_html/includes/templates/scrappin_stuff/templates/tpl_modules_product_listing.php:12]
#4 require(/home/scrappin/public_html/includes/templates/scrappin_stuff/templates/tpl_modules_product_listing.php) called at [/home/scrappin/public_html/includes/templates/scrappin_stuff/templates/tpl_index_product_list.php:93]
#5 require(/home/scrappin/public_html/includes/templates/scrappin_stuff/templates/tpl_index_product_list.php) called at [/home/scrappin/public_html/includes/modules/pages/index/main_template_vars.php:217]
#6 require(/home/scrappin/public_html/includes/modules/pages/index/main_template_vars.php) called at [/home/scrappin/public_html/includes/templates/scrappin_stuff/common/tpl_main_page.php:151]
#7 require(/home/scrappin/public_html/includes/templates/scrappin_stuff/common/tpl_main_page.php) called at [/home/scrappin/public_html/index.php:97]

I can delete the files but they aren't new. The files were there - I just uploaded changed files. Getting rid of them leaves me with this only:
[11-Mar-2015 07:46:47 America/New_York] PHP Warning: substr() expects parameter 3 to be long, string given in /home/scrappin/public_html/m/includes/functions/functions_general.php on line 1016

I uploaded a fresh version of functions_general.php straight out of the zip file but that didn't stop it.

It was 1.5.1 I had the problem with before as well. I will be upgrading the other cart shortly but I was not hired to do it for this one.

[Design75]

the function substr() expects the third parameter to be a of the type "long". You are sending type "string". Try to find out why tpl_index_product_list.php is sending the variable of the type string on line 93

[delia]

Since it's happening in both installations, I don't how it can be caused by specific files. That's the real mystery here, I believe.

How come you conclude the tpl_index_product_list.php is the culprit? Those files do look to be the same in both installations - the default files.

[Design75]

sorry, looked at the wrong line

it should be /home/scrappin/public_html/includes/modules/scrappin_stuff/product_listing.php line 178. This is where zen_trunc_string() is called

[delia]

okay, when I took the product listing out I was still left with this:

[11-Mar-2015 07:46:47 America/New_York] PHP Warning: substr() expects parameter 3 to be long, string given in /home/xxxxx/public_html/m/includes/functions/functions_general.php on line 1016

[delia]

But the weirdest part of this is how the warnings started showing in the installation where I had made no changes at all. It all started in both at the same time.

Now I'm wondering if having the two separate installations with the same database could have something to do with it. I've never seen it happen before though.

[swguy]

Can you get a traceback on this so we can see the calling line?