I just restored to a working date and still not working

spawnie69:

[18-Mar-2016 08:04:51 America/Denver] PHP Warning: require(includes/templates/template_default/templates/tpl_flexible_footer_menu.php): failed to open stream: No such file or directory in /home8/gelcand1/public_html/includes/templates/responsive_sheffield_blue/common/tpl_footer.php on line 58
[18-Mar-2016 08:04:51 America/Denver] PHP Fatal error: require(): Failed opening required 'includes/templates/template_default/templates/tpl_flexible_footer_menu.php' (include_path='.:/usr/php/56/usr/lib64:/usr/php/56/usr/share/pear') in /xxxxx/xxxxx/public_html/includes/templates/responsive_sheffield_blue/common/tpl_footer.php on line 58
Those are not admin-related. But they're telling you that your active template, responsive sheffield blue, is specifically looking for a file named tpl_flexible_footer_menu.php but it's not present. (Should normally be in the includes/templates/responsive_sheffield_blue/templates/ folder, but since it's not there, it's trying the template_default folder, and when not found there it's showing up in the logs as a failure.)
So, need to restore that tpl_flexible_footer_menu.php file.

mc12345678:

So, need to validate that emails are being sent from retail. Also would suggest reviewing the settings for email between the two sites. Arethey expected to be using the same email address(es). Do account generation/order emails come in? What recipient is not getting the email(s)?

got it, will do. Looks like alot of sheffield blue temp files missing. 'I will upload mine.

Very strange its like all the responsive blue -- template files are missing
only default files are there within /includes/templates/responsive_sheffield_blue/templates

Is this typical?

spawnie69:

Is this typical?Probably not. But that's a loaded question. It all depends on the backups you made.
It would be "typical" if those files weren't already on the server when you did the backup, which you've subsequently restored from.
But if the files were indeed present at the time of the backup, then if the backup worked correctly then those files should have been in the backup, and thus when restored those files should have been restored. But, as you can see, there are a lot of possible points at which those files might not have went where they were supposed to.

DrByte:

Probably not. But that's a loaded question. It all depends on the backups you made.
It would be "typical" if those files weren't already on the server when you did the backup, which you've subsequently restored from.
But if the files were indeed present at the time of the backup, then if the backup worked correctly then those files should have been in the backup, and thus when restored those files should have been restored. But, as you can see, there are a lot of possible points at which those files might not have went where they were supposed to.

I restored from the 5th and I had my blue sheffield installed properly in my files. In fact there happens to be a /responsive blue sheffield folder in my includes/template folder.

DrByte:

Those are not admin-related. But they're telling you that your active template, responsive sheffield blue, is specifically looking for a file named tpl_flexible_footer_menu.php but it's not present. (Should normally be in the includes/templates/responsive_sheffield_blue/templates/ folder, but since it's not there, it's trying the template_default folder, and when not found there it's showing up in the logs as a failure.)
So, need to restore that tpl_flexible_footer_menu.php file.

Then why can't I even see my admin page. Shows a 500 error ?
I already edit my file to SELF in case.

Just wholesale admin works.

spawnie69:

Then why can't I even see my admin page. Shows a 500 error ?
I already edit my file to SELF in case.
The self:: vs static:: thing is specific to v154 and older PHP.
So, if you've already applied that fix and it's still giving you trouble, the next thing to do is look at the debug logs for what the newest messages are. And with '500' errors sometimes they happen before ZC turns on the logging so the errors are in your server's Apache error-log or maybe the server's PHP error-log ... which you can often access via your hosting company's control panel.

DrByte:

Probably not. But that's a loaded question. It all depends on the backups you made.
It would be "typical" if those files weren't already on the server when you did the backup, which you've subsequently restored from.
But if the files were indeed present at the time of the backup, then if the backup worked correctly then those files should have been in the backup, and thus when restored those files should have been restored. But, as you can see, there are a lot of possible points at which those files might not have went where they were supposed to.

I think I get it now just upload the file to satisfy the call

DrByte:

The self:: vs static:: thing is specific to v154 and older PHP.
So, if you've already applied that fix and it's still giving you trouble, the next thing to do is look at the debug logs for what the newest messages are. And with '500' errors sometimes they happen before ZC turns on the logging so the errors are in your server's Apache error-log or maybe the server's PHP error-log ... which you can often access via your hosting company's control panel.

yes applied fix.

debug files show a bunch of missing flexible footer files and a few session files.

Here is what showed up php error logs

/xxxxxx/xxxxxx/public_html/error_log:
[16-Mar-2016 21:15:06] PHP Fatal error: require() [<a href='function.require'>function.require</a>]: Failed opening required 'includes/application_top.php' (include_path='.:/usr/lib64/php:/usr/share/pear') in /xxxxx/xxxxxx/public_html/index.php on line 26

spawnie69:

/xxxxxx/xxxxxx/public_html/error_log:
[16-Mar-2016 21:15:06] PHP Fatal error: require() [<a href='function.require'>function.require</a>]: Failed opening required 'includes/application_top.php' (include_path='.:/usr/lib64/php:/usr/share/pear') in /xxxxx/xxxxxx/public_html/index.php on line 26
That date is from a few days ago. :)

spawnie69:

I think I get it now just upload the file to satisfy the call

Yes, if the program structure can find the file, then that specific error message will not occur. As to the discussion of "template default files" being in your responsive blue folder, have to ask what you mean by them being the template default file(s)? My reasoning is that it implies one of two things, either the template override system is not understood, or the files present are unmodified from the original and that this has been confirmed by use of a comparison tool.

The other thing which DrByte was getting at is the reason for the file to be missing... Yes in all of this backup/restore something could have gone wrong, but...

mc12345678:

Yes, if the program structure can find the file, then that specific error message will not occur. As to the discussion of "template default files" being in your responsive blue folder, have to ask what you mean by them being the template default file(s)? My reasoning is that it implies one of two things, either the template override system is not understood, or the files present are unmodified from the original and that this has been confirmed by use of a comparison tool.

The other thing which DrByte was getting at is the reason for the file to be missing... Yes in all of this backup/restore something could have gone wrong, but...

All I was saying is that I was seeing the defaut template structurev of the classic template.

I don't think I understand over rides.
I just built my 1.54 cart then setup my blue sheffield cart and it was working fine. Did I place fies in wrong folder then?
All I have to then is place those files were they are looked at to cause no errors?

Main error log in cpanel had a bunch a crap, I guess normal.

My log files are empty. I find them in cache. Why is this?

spawnie69:

All I was saying is that I was seeing the defaut template structurev of the classic template.

I don't think I understand over rides.
I just built my 1.54 cart then setup my blue sheffield cart and it was working fine. Did I place fies in wrong folder then?
All I have to then is place those files were they are looked at to cause no errors?

At the moment, the only file that was identified as being a problem was the footer file. In a majority of cases, pay attention to the first thing logged in the file. There are a few log files that come across differently and the location to be touched is elsewhere, but in the most cases, the first error/warning is the one that started all of the remaining messages that get logged in the file. So... As DrByte described, the template system tries to find a template file in the template override directory first, when it can't find it there, it tries the template_default directory. This is why the classic folder should remain "empty" (There is usually one or two "blank" files there), but by switching to the classic template, basically the default files are used and therefore modifications made to the template files (YOUR_TEMPLATE) are "ignored" (they do not get loaded).

So, yes upload/reupload the first file that was attempted to be found in the template_default folder (file was added by the template and only to the template directory not to both the template directory and the template_default directory. )

spawnie69:

Main error log in cpanel had a bunch a crap, I guess normal.

My log files are empty. I find them in cache. Why is this?

Assuming that the files are truly up-to-date, then because of this logic:

if (!defined('DIR_FS_LOGS')) { 
   $val = realpath(dirname(DIR_FS_SQL_CACHE . '/') . '/logs'); 
   if (is_dir($val) && is_writable($val)) { 
     define('DIR_FS_LOGS', $val); 
   } 
   else { 
     define('DIR_FS_LOGS', DIR_FS_SQL_CACHE); 
   } 
 } 

Found in either/both: includes/extra_configures/enable_error_logging.php and admin/includes/extra_configures/enable_error_logging.php

Which suggests that either or both the logs directory doesn't exist (have stated that it does, so that's not the problem) or the logs directory is not writeable. Check the permissions of the logs folder to see if they are at least 755.

spawnie69:

Main error log in cpanel had a bunch a crap, I guess normal.

Error logs... abnormal... Errors should not exist.

Logs of activity... Normal. Activity is generally good, implies site is active.

mc12345678:

Assuming that the files are truly up-to-date, then because of this logic:

if (!defined('DIR_FS_LOGS')) {
$val = realpath(dirname(DIR_FS_SQL_CACHE . '/') . '/logs');
if (is_dir($val) && is_writable($val)) {
define('DIR_FS_LOGS', $val);
}
else {
define('DIR_FS_LOGS', DIR_FS_SQL_CACHE);
}
}

> 
> Found in either/both: includes/extra_configures/enable_error_logging.php and admin/includes/extra_configures/enable_error_logging.php
> 
> Which suggests that either or both the logs directory doesn't exist (have stated that it does, so that's not the problem) or the logs directory is not writeable. Check the permissions of the logs folder to see if they are at least 755.

After restored I emptied the old log files in /logs folder.  Now they appear in /cache folder.   /logs folder is writeable permissions

mc12345678:

Error logs... abnormal... Errors should not exist.

Logs of activity... Normal. Activity is generally good, implies site is active.

I found this under main error log:

MAIN error_log:
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:58 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] [client 5.178.68.254] mod_rbl: 5.178.68.254 is listed in RBL., referer: http://bfreese.com/xmlrpc.php
[Fri Mar 18 13:53:59 2016] [notice] [client 112.196.22.41] mod_rbl: 112.196.22.41 is listed in RBL.
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:53:59 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
[Fri Mar 18 13:54:00 2016] [notice] [client 176.74.12.52] mod_rbl: 176.74.12.52 is listed in RBL.
[Fri Mar 18 13:54:01 2016] [error] [client 199.180.60.117] File does not exist: /usr/local/apache/htdocs/autodiscover
[Fri Mar 18 13:54:02 2016] [notice] [client 176.74.12.52] mod_rbl: 176.74.12.52 is listed in RBL.
[Fri Mar 18 13:54:03 2016] [error] [client 199.180.60.117] File does not exist: /usr/local/apache/htdocs/autodiscover
[Fri Mar 18 13:54:03 2016] [notice] [client 112.196.22.41] mod_rbl: 112.196.22.41 is listed in RBL.
[Fri Mar 18 13:54:04 2016] [notice] [client 176.74.12.52] mod_rbl: 176.74.12.52 is listed in RBL.
[Fri Mar 18 13:54:05 2016] [error] [client 31.13.99.96] File does not exist: /usr/local/apache/htdocs/pinosky
[Fri Mar 18 13:54:05 2016] [error] [client 180.76.15.140] Zend Guard Loader requires Zend Engine API version 220100525.
[Fri Mar 18 13:54:05 2016] [error] [client 180.76.15.140] The Zend Engine API version 220131226 which is installed, is newer.
[Fri Mar 18 13:54:05 2016] [error] [client 180.76.15.140] Contact Zend Technologies at http://www.zend.com/ for a later version of Zend Guard Loader.
[Fri Mar 18 13:54:05 2016] [error] [client 180.76.15.140] 
[Fri Mar 18 13:54:05 2016] [notice] [client 112.196.22.41] mod_rbl: 112.196.22.41 is listed in RBL.
[Fri Mar 18 13:54:05 2016] [notice] [client 176.74.12.52] mod_rbl: 176.74.12.52 is listed in RBL.
[Fri Mar 18 13:54:07 2016] [notice] [client 176.74.12.52] mod_rbl: 176.74.12.52 is listed in RBL.

No other error other than the flexible footer file. Which is really weird because I setup the template and all, I even download my files dated march 11th and did a search for the workd flexible and could not find it. I could resort to using the template file if ok.
But this struck me as odd.

I know I had this template installed, I unfortunately do no have a backup since my downloads break when too big.
Can this happen? Weird cause I can see /public_html/includes/templates/responsive_sheffield_blue but all I see are three folders
/templates
/sideboxes
/commmon

which should have my missing files