Project task causes database failure citing unknown table 'project_task' in SuiteCRM 8.5.0
Closed this issue · 4 comments
After creating a Project Template with one or more Tasks, when one then creates a Project it spawns a "Database failure" message under "Project Tasks". This also occurs if a Project is created without specifying a Project Template, then attempting to create a task.
SuiteCRM log shows:
Sun Jan 21 12:41:39 2024 [46076][8e9600ea-8210-9588-678b-65a59de942a4][FATAL] Error retrieving Project list: Query Failed: (SELECT project_task.id , project_task.name , project_task.date_start , project_task.date_finish , project_task.assigned_user_id , 'projecttask' panel_name FROM project_task INNER JOIN project projecttask_rel ON project_task.project_id=projecttask_rel.id AND projecttask_rel.deleted=0
where ( project_task.project_id='89df78af-fb1d-f077-a94a-65ad46c309c8') AND project_task.deleted=0) ORDER BY project_task.project_task_id asc LIMIT 0,10: MySQL error 1109: Unknown table 'project_task' in order clause
Sun Jan 21 12:41:39 2024 [46076][8e9600ea-8210-9588-678b-65a59de942a4][FATAL] [ListView::processUnionBeans] . Database failure. Please refer to suitecrm.log for details.
What should happen is that a list of tasks is displayed; what happens is the Database failure message.
Repairing the database doesn't cure the problem. The project_task table is present in the database.
SuiteCRM 8.5.0
Firefox 121.0.1/Chromium Version 120.0.6099.224
mysql Ver 8.0.35-0ubuntu0.22.04.1 for Linux on x86_64 ((Ubuntu))
PHP 8.1.27
Ubuntu 22.04
Thanks.
Perhaps.
However, when following the suggestion given in #10321 (modify two lines in Project.php) we find the same "Database failure" message is generated and the project tasks are still not listed.
Please note also that #10321 refers to SuiteCRM Version 7.14.2 while the issue raised here (#10324) relates to SuiteCRM Version 8.5.0.
Thanks for the thought anyway, and any other thoughts/ideas/suggestions would be much appreciated!
All 8.x issues should be posted to SuiteCRM-Core/issues.
Sorry - now posted to SuiteCRM-Core/issues.