After the timer reaches 00:00:00 , he makes 00:00:0-1 , and then, instead of writing 23:59:59 , he writes 24:19:06 . From where it takes 19 minutes ... Here is this piece of code that is responsible for this: <span id=\"deptimer". $row['id'] ."\"></span> <span id=\"deptimer". $row['id'] ."\"></span>

PS: I did not write the script, but I was destined to deal with it.

2 answers 2

You gave an example of data output. It does not say anything. Give an example of the code that is responsible for the $row['id'] parameter.

PS On request Darth:

Look for a place where the plans table’s nextdate field is filled. This script only displays information on payments. Any query that updates the table - UPDATE plans . Look at what triggers are executed in the database, which are tied to the tables deposits , plans , users .

  • code dropped on file sharing, it is not big dropmefiles.com/arE7t - Andrey Andrey
  • I myself looked and did not understand where there are intersections with them, only for the query database - Andrei Andrei
  • Look for where the nextdate field in the plans table is filled. This script only displays information on payments. Any query that updates the UPDATE plans table. See what triggers are executed in the database, which are tied to the table deposits , plans , users - GlWhitefoot
  • @GlWhitefoot the "nextdate" field is only in the "deposits" table, there are no triggers, and data are dumped into deposits from another page - "deposit" here is the code dropmefiles.com/8Y32k - Andrey Andrei
  • What I see from the presented code: 1. formation of the date occurs in lines 35-68, 2. probably the date is incorrectly calculated in lines 57-68, 3. incorrectly it is calculated, because the cfgSET function returns the time corresponding to not 00:00:00 the current day, and 00:19:00. Therefore, analyze how it works and where it takes the data, and how it gets there. - GlWhitefoot

The problem was solved!

 $nextdate = $nextdate + $row['moroz'] * 3600;