Cant access product admin pages

So came in to work today from my "weekend" and I have a number of issues that were not present when I left two days ago. Main one I'm looking at right now is that I can't get into either of my sites product pages (admin side). I can navigate through Categories/Products all the way to the lowest subcategory with no issue, but as soon as I try to enter an actual product page, all I get is a blank screen. I've got error logging turned on, but nothing is actually getting flagged, and all of my products are live and go through as orders without issue. If I try to make a new product, I get the same blank screen.

As I said, I've got two sites, one on 1.5.5 and one on 1.5.4 (different servers, domains and databases, same web-host), and as far as I can tell, they both started acting up at the same time. The other issue I'm having is that all of our emails that use either domain have quit working, but I've already got our web-host looking into that. I'm ASSUMING that because of how they are both having the exact same issue, that it is also a server-side thing, but I don't know how I would go about explaining this issue to the web host, or what I can do to actually check the issue first.

I know it isn't something that one of my coworkers has messed with, as none of the others have access to the FTP client.

Sites are https://www.athensartandframe.com/ and https://www.framebiz.com/

With the software being older, are you able to tell what php version is being seen by the software? It may (both far fetched, but also likely) be that there has been an upgrade in php version beyond that supported by the software.


As far as "error logging" being turned on, not sure what is meant by that (cuz I can't say that it is freely able to be turned off per se in a stock install). So the question is are there myDebug-xxx type files being generated in the logs directory of your store and what do they indicate about the blank screen result? Also, what was being done two days ago that might have been changed but may have been a session related thing that didn't appear until the next login (today)?

Just checked this morning. Server is running php 7.3.6. and with 5.6 being the highest that 1.5.4 can run on, not only does that look to be the likely culprit, I'm surprised anything is even working at all.

When I took over site maintenance/online sales for us, I was told that we keep debug_error_logging.php commented out, unless something actually happens, to prevent it from just filling up the logs folder with unnecessary files. Which I can honestly understand as we have got several thousand logs all pointing at our WordPress blog alone but those are all from last year and earlier. *shrugs* Absolutely nothing regarding this actual issue though.

As for what could have changed, I have 2 main issues I've been trying to work on.

1. One of our products has a customer image/file upload attribute on it, and we have not been getting anything in our images > uploads folder from it. Works fine for our 1.5.5, so I had been cross-referencing the Configuration > Images in Admin, as well as the Images > config.php files for the two. I made some changes in admin to match the working site, but when that didn't fix anything I changed them back to the original settings. Config.php matched (aside from the different wording of the defines between different ZC versions) so I didn't change anything there.

2. We have some EZ-Page E-Brochures explaining our various products and services on our 1.5.5 site, that I wanted to put up on our 1.5.4, but the sideboxes aren't working. Again opened them up on both admin sites to do a cross comparison, but I can't see any differences there, so I didn't make any changes either. Did not even touch the php files in this case.

Since I didn't change anything there, I would think that doesnt have anything to do with it.

The only significant changes I've made was installing Customer Review Reminder, Product Sorter, and Admin Display Product/Catalog Thumbnails, all of which are working fine, and I installed almost 2 weeks ago, well before these issues popped up. (I made sure to use the older versions that were rated for 1.5.4 as well, instead of the most recent, unless they were backwards compatible.)

The fact that it's the same issue on both sites, and that they both cropped up at the same time, I am going to assume it's due to a server upgrade. But I would think that that's something they should have informed us about prior to doing.....

Quote:

---

Originally Posted by Lordzoabar

When I took over site maintenance/online sales for us, I was told that we keep debug_error_logging.php commented out, unless something actually happens, to prevent it from just filling up the logs folder with unnecessary files. Which I can honestly understand as we have got several thousand logs all pointing at our WordPress blog alone but those are all from last year and earlier. *shrugs* Absolutely nothing regarding this actual issue though.
....

---

really hard to debug problems without log files.... turning logging off is never a good idea. addressing why there are several thousand logs is a better idea, and will allow you to keep logging on.

if you have taken over, i would suggest turning the logging back on, and work on correcting problems that the logs tells you.

best/

I have them on now, and I have been slowly trying to work my way through them. All the ones on the 1.5.5 site are from October 2019 or older, and (so far) all point to WordPress. Which we haven't updated in over a year anyway. The ones for 1.5.4 are even older from January 2018 and earlier, so I ASSUME they were addressed, and just never cleaned up?

Quote:

---

Originally Posted by Lordzoabar

I have them on now, and I have been slowly trying to work my way through them. All the ones on the 1.5.5 site are from October 2019 or older, and (so far) all point to WordPress. Which we haven't updated in over a year anyway. The ones for 1.5.4 are even older from January 2018 and earlier, so I ASSUME they were addressed, and just never cleaned up?

---

i would delete all old log files, and start addressing new ones as they come up... but that's me...

The Log Manager (a drop-in plugin) might help to automatically weed-out those older logs, too.

Quote:

---

Originally Posted by carlwhat

i would delete all old log files, and start addressing new ones as they come up... but that's me...

---

I would love to, it's just SO SLOW.

Quote:

---

Originally Posted by lat9

The Log Manager (a drop-in plugin) might help to automatically weed-out those older logs, too.

---

This. This is among the most beautiful pieces of coding I have seen on here. This is brilliant.



In other news, I started uninstalling and restoring from backups the last modules I installed, and taking out the Admin Display Product/Catalog Thumbnails seemed to do the trick. I guess one line ended up getting written over that only slightly broke the product pages. Now if only the image/file uploading mystery can be solved that easily, I'd be set.

Quote:

---

Originally Posted by Lordzoabar

I would love to, it's just SO SLOW.



This. This is among the most beautiful pieces of coding I have seen on here. This is brilliant.



In other news, I started uninstalling and restoring from backups the last modules I installed, and taking out the Admin Display Product/Catalog Thumbnails seemed to do the trick. I guess one line ended up getting written over that only slightly broke the product pages. Now if only the image/file uploading mystery can be solved that easily, I'd be set.

---

Thanks for the compliment; I'm glad it's working for you!

Quote:

---

Originally Posted by Lordzoabar

we have got several thousand logs

---

I was estimating. The actual amount is 9998 error logs going back 8 months.

Which is apparently the maximum allowed, as both sites have the exact same amount.

:laugh::frusty:

Quote:

---

Originally Posted by lat9

Thanks for the compliment; I'm glad it's working for you!

---

Ok, seriously. You have NO idea how helpful that actually turned out to be (or you probably do, being far more versed in php and zencart than I am).

When I mentioned the 9998 log files in my folder, apparently that is just the limit that FileZilla can handle. I have taken the "days to keep" config and brought it down from 150 to just 7 days, and it ended up clearing close to 60,000 (yes, sixty THOUSAND) logs over my many time resets. I have finally cleared out enough, that the log folder has actually started loading more and more recent errors.

Which brings me full circle to my original issue. I can access my product pages now, but if I make any changes and go to preview, I get "This page isn't working".

Error Logs give:

[06-Feb-2020 08:35:02 America/Phoenix] PHP Notice: Undefined index: gID in /home/##########__/public_html/____/includes/init_includes/init_zen_lightbox.php on line 86
[06-Feb-2020 08:35:02 America/Phoenix] PHP Notice: Undefined variable: new_version_available in /home/##########__/public_html/includes/functions/plugin_support.php on line 52
[06-Feb-2020 08:35:02 America/Phoenix] PHP Notice: Undefined index: gID in /home/##########__/public_html/____/includes/init_includes/init_zx_product_sorter.php on line 86
[06-Feb-2020 08:35:02 America/Phoenix] PHP Notice: Undefined index: gID in /home/##########__/public_html/____/includes/init_includes/init_google_analytics_config.php on line 365
[06-Feb-2020 08:35:02 America/Phoenix] PHP Notice: Undefined index: gID in /home/##########__/public_html/____/includes/init_includes/init_shipping_boxes_manager.php on line 80
[06-Feb-2020 08:35:02 America/Phoenix] PHP Fatal error: Call to undefined function dirList() in /home/##########__/public_html/2018/product.php on line 90


[06-Feb-2020 08:35:02 America/Phoenix] Request URI: /____/product.php?cPath=25&product_type=1&pID=2450&action=new_product_preview&page=3&s earch=uni, IP address: ##########__
--> PHP Fatal error: Call to undefined function dirList() in /home/##########__/public_html/____/product.php on line 90.

plugins were not properly installed. the product admin page is calling a function

Code:

---

function dirList()

---

which is not getting loaded. that function is not part of ZC which means it is part of a modification that someone did on your site. i have no idea which plugin defines that function, despite doing a quick look for it.

these undefined index problems are "probably" due to outdated plugins that need to be updated. tough to tell....

removing log files should not be your goal. addressing the problems that are generating the log files is your goal. having 60,000 log files is a sign of a site not well maintained. i would maintain it better.

good luck.

The log files had to be removed, as the folder was so bloated, that our FTP client refused to load anymore in until it was cleared out.

There are a number of plugins that I know are either broken or outdated, (looking at you, Google Analytics) but the previous solution was apparently just to comment out or rename the files to be ignored, so I'm slowly going through and comparing with a fresh copy of the plugin to see what changes have been made. One thing gets fixed, and two more pop up.

The dirList function was part of numinix' software (Numinix Product Fields at least).


As to clearing the logs directory from a mass deletion perspective, the entire folder could be deleted and then restored from a vanilla version of the software. This way the appropriate .htaccess and other associated files are put in place.

In some ways it may be easier to rebuild the software of the site and then compare the two to see where the differences are and as necessary incorporate whatever changes are needed. The rebuilt site could be in a sub-directory or on a local machine, wherever but leaving what operation is available ongoing. The same thing too is if it is only the admin directory that is having issues is that a second admin directory could be loaded to do the above rebuild...

Quote:

---

Originally Posted by mc12345678

The dirList function was part of numinix' software (Numinix Product Fields at least).

---

That did it. There was one single NPF file that was lingering, as well as the bit of code that was added to product.php. Pulled up an older backup version of the file and used that to clean up the current.

The boss says it isn't in the budget to hire anyone to manage a full rebuild/upgrade any time soon, so we've got a virtual machine set up that we use to test out major changes, but that doesn't really help when we can't replicate a particular issue.

Quote:

---

Originally Posted by Lordzoabar

That did it. There was one single NPF file that was lingering, as well as the bit of code that was added to product.php. Pulled up an older backup version of the file and used that to clean up the current.

The boss says it isn't in the budget to hire anyone to manage a full rebuild/upgrade any time soon, so we've got a virtual machine set up that we use to test out major changes, but that doesn't really help when we can't replicate a particular issue.

---

Whether someone else is brought in or it is done in house, my discussion was centered around "big picture" ways to discover and/or correct the issue. Use of a file difference comparison program would make that easier rather than counting on myDebug files providing indication of those differences/repeatability.