I am getting the following error with the 1.8-7q after uploading all the new files and running the sql statements

Question

I am getting the following error with the 1.8-7q after uploading all the new files and running the sql statements

samoy2002 opened this issue 3 years ago · comments

samoy2002 commented 3 years ago

Unhandled Exception
Message:
Undefined index: temps_fait
Location:
/home/mbbizca/public_html/bugs/app/application/models/project/issue/comment.php on line 39
Stack Trace:
#0 /home/mbbizca/public_html/bugs/app/laravel/laravel.php(37): Laravel\Error::native(8, 'Undefined index...', '/home/mbbizca/p...', 39)
#1 /home/mbbizca/public_html/bugs/app/application/models/project/issue/comment.php(39): Laravel{closure}(8, 'Undefined index...', '/home/mbbizca/p...', 39, Array)
#2 /home/mbbizca/public_html/bugs/app/application/controllers/project/issue.php(83): Project\Issue\Comment::create_comment(Array, Object(Project), Object(Project\Issue))
#3 [internal function]: Project_Issue_Controller->post_index('6', '90')
#4 /home/mbbizca/public_html/bugs/app/laravel/routing/controller.php(325): call_user_func_array(Array, Array)
#5 /home/mbbizca/public_html/bugs/app/laravel/routing/controller.php(285): Laravel\Routing\Controller->response('index', Array)
#6 /home/mbbizca/public_html/bugs/app/laravel/routing/controller.php(165): Laravel\Routing\Controller->execute('index', Array)
#7 /home/mbbizca/public_html/bugs/app/laravel/routing/route.php(153): Laravel\Routing\Controller::call('project.issue@i...', Array)
#8 /home/mbbizca/public_html/bugs/app/laravel/routing/route.php(124): Laravel\Routing\Route->response()
#9 /home/mbbizca/public_html/bugs/app/laravel/laravel.php(158): Laravel\Routing\Route->call()
#10 /home/mbbizca/public_html/bugs/index.php(18): require('/home/mbbizca/p...')
#11 {main}

Patriboom · Answer 1 · Wed Nov 03 2021 05:42:19 GMT+0800 (China Standard Time)

Hello, please let me know how did you abtain such result ( the whole process like :

open new issue
comment it
comment it again, but this time with nothing in ...

)

I tried again, but could not reproduce the problem.

Thanks.

Patriboom · Answer 2 · Wed Nov 03 2021 08:42:11 GMT+0800 (China Standard Time)

You may need this command in PhpMySQL

ALTER TABLE projects_issues_comments ADD COLUMN temps_fait time DEFAULT NULL AFTER comment;

samoy2002 · Answer 3 · Wed Nov 03 2021 08:49:45 GMT+0800 (China Standard Time)

Thank you. I cannot test or give screenshots of where I am getting the errors till tomorrow morning. It was a strange error as I was getting it at times as I hit go for a new issue and always when trying to link an image in a new issue. On a side note, all the help you give and doing custom work, where do we donate to the project? Mark

…

Sent from my iPhone

On Nov 2, 2021, at 7:43 PM, Patriboom ***@***.***> wrote: You may need this command in PhpMySQL ALTER TABLE projects_issues_comments ADD COLUMN temps_fait time DEFAULT NULL AFTER comment; — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

Patriboom · Answer 4 · Wed Nov 03 2021 11:19:52 GMT+0800 (China Standard Time)

Thanks for explination. I could reproduce the issue creating an issue. I'll fix it.

The patch will be available within few minutes. Your clues helped.

I've never had offer for donation. I think you have my email address, you can use it for that. Thanks for offer.
The best reward will ever by to know that users are using it.

Patriboom · Answer 5 · Wed Nov 03 2021 11:21:31 GMT+0800 (China Standard Time)

release 7s is there with the patch for "temps_plan" issue on new ticket's creation.

samoy2002 · Answer 6 · Wed Nov 03 2021 23:10:04 GMT+0800 (China Standard Time)

Error
SQL query:

ALTER TABLE projects_issues_comments ADD COLUMN temps_fait time DEFAULT NULL AFTER comment
MySQL said: Documentation

#1060 - Duplicate column name 'temps_fait'

Patriboom · Answer 7 · Wed Nov 03 2021 23:21:53 GMT+0800 (China Standard Time)

Ok, good. It says that the columns has already been defined. That what I wanted to make sure of.
What were you doing when you received this notice ?

Was it installling the last update ?
Did you apply the command « ALTER TABLE projects_issues ... » directly in phpMyAdmin ?

samoy2002 · Answer 8 · Wed Nov 03 2021 23:34:18 GMT+0800 (China Standard Time)

I did it directly in phpmyadmin. For some reason I cannot upgrade software from within the administration tab. It cannot connect for some reason. Mark

…

Sent from my iPhone

On Nov 3, 2021, at 10:23 AM, Patriboom ***@***.***> wrote: Ok, good. It says that the columns has already been defined. That what I wanted to make sure of. What were you doing when you received this notice ? Was it installling the last update ? Did you apply the command « ALTER TABLE projects_issues ... » directly in phpMyAdmin ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

Patriboom · Answer 9 · Wed Nov 03 2021 23:43:29 GMT+0800 (China Standard Time)

Ok.
You may have message like « Your version is ahead of what the gitHub deposit offers » in Administration tab. That could explain you can not update database automatically. It will come back to normal soon, just after those little fixes we are doing now.

Those MySQL commands will be part of the coming update.
Just make sure all is set properly with that:

ALTER TABLE projects_issues_comments MODIFY COLUMN temps_fait_fin datetime DEFAULT NULL;
ALTER TABLE projects_issues_comments MODIFY COLUMN temps_fait_deb datetime DEFAULT NULL;
ALTER TABLE projects_issues_comments MODIFY COLUMN temps_fait smallint(4) DEFAULT 1;

Patriboom · Answer 10 · Thu Nov 04 2021 22:01:28 GMT+0800 (China Standard Time)

samoy2002 wrote:

On a side note, all the help you give and doing custom work, where do we donate to the project?

If you're scuba diver, you can help me on another project.