How do I resolve this error/warning? page_parse_time.log failed to open stream

[xcergy]

> admin > config > logging > Store Page Parse Time > set to "false"

Where is that? I can't find it.

C:\xampp\htdocs\local_cart\admin_name\includes\classes\logger.php

    function timer_stop($display = 'false') {
      $this->timer_stop = microtime();

      $time_start = explode(' ', $this->timer_start);
      $time_end = explode(' ', $this->timer_stop);

      $this->timer_total = number_format(($time_end[1] + $time_end[0] - ($time_start[1] + $time_start[0])), 3);

      $this->write($_SERVER['REQUEST_URI'], $this->timer_total . 's');

      if ($display == 'true') {
        return $this->timer_display();
      }
    }

    function timer_display() {
      return '<span class="smallText">Parse Time: ' . $this->timer_total . 's</span>';
    }

    function write($message, $type) {
      error_log(strftime(STORE_PARSE_DATE_TIME_FORMAT) . ' [' . $type . '] ' . $message . "\n", 3, STORE_PAGE_PARSE_TIME_LOG);
    }
  }
?>

[lat9]

> admin > config > logging > Store Page Parse Time > set to "false"

Where is that? I can't find it.

Navigate to your admin's Configuration->Logging and then change the setting for Store Page Parse Time to false.

While you're there, also change the Log Destination to /home/users/web/b1441/acct_name/cache/page_parse_time.log

[xcergy]

Navigate to your admin's Configuration->Logging and then change the setting for Store Page Parse Time to false.

While you're there, also change the Log Destination to /home/users/web/b1441/acct_name/cache/page_parse_time.log

Found it. was able to change the path there. Thanks

[xcergy]

The cart still is a blank page, and there is no relater error log to point to the problem.

[lat9]

If you're really still using Zen Cart v1.3.8a, the "native" processing did not include the error log handling. You can install the myDebug Backtrace (https://www.zen-cart.com/downloads.php?do=file&id=1879) plugin to enable logging to your store's /cache folder ...

... and you should really, really consider starting to upgrade.

[xcergy]

... and you should really, really consider starting to upgrade.


I'll look into that plugin.

And yes, I will upgrade, and tried to explain my method of madness. 1.3.8 is no longer available/working on my host, and this is the only way I can save the database, removed outdated plugins befor installing 1.5.4.

[xcergy]

If you're really still using Zen Cart v1.3.8a, the "native" processing did not include the error log handling. You can install the myDebug Backtrace (https://www.zen-cart.com/downloads.php?do=file&id=1879) plugin to enable logging to your store's /cache folder ...

Is there a link for 1.3.8? The page you referenced is for 1.5.x

[lat9]

The plugin should still operate on 1.3.8a.

[xcergy]

Found this ..
https://www.zen-cart.com/downloads.php?do=file&id=606

Installed but shows nothing :-(

[mc12345678]

I really hate to say this to someone that is trying so hard to follow the recommended instructions for upgrading. In the perspective of upgrading the database to operate under the newer version of ZC, if the plugins that were installed before the upgrade have an upgrade path to the current ZC, then any database changes made in that upgrade path can be made in parallel with the ZC store upgrade. Any plugins that will be abandoned can have their applicable database modifications (removal) made after the upgrade.

I somewhat feel that the last week or so in attempt to get this store upgraded (functional to make money) more effort has been spent (time = money) than is really necessary to become operational again.

Ideally, and basically speaking, plugins that touch the database if supported on this site at any version do not disable the ability to upgrade. They may leave behind some inaccurate settings that require a little bit of modification (typically seen sites with early mods to allow multiple admins might require a little login massaging to get back on track, but never something unrecoverable). There's even a plugin now available that basically inspects the database and identifies changes to the system that might need to be addressed...

Further understand that if a plugin does have an upgrade path that in some cases removal of that plugin by deletion of database information would be a loss for that plugin as that data may have to be manually/painstakingly recreated. That of course is something applicable to the plugin(s), and could/should be addressed in the plugin's forum... Listing said plugins here (as suggested by the forum posting tips) would help others to help you identify if this effort is even worth all that is being done.

Lastly, stated that it is not possible to salvage the database without going through this process, but question is, have you tried the upgrade on a backup of the database and what were the results?