Help with Log Errors: Unable to get proper side for link

💬 General Discussion
1

Seeing this error a lot. any ideas?

Mon Dec 19 18:15:55 2016 [15910][7098c295-4ea7-26fe-af1d-4dda14b75350][ERROR] Unable to get proper side for link assigned_user_link

2

Also getting similar error:
Fre 23 Dez 2016 12:11:07 CET [7574][7098c295-4ea7-26fe-af1d-4dda14b75350][ERROR] Unable to get proper side for link project_name_link

This one seems to show up whenever I open either a) a Project with linked project task shown in subpanel ProjectTasks, or b) a Project Task with linked Project (in field “Project”).

The only place this link seems to be described is in the file /modules/ProjectTask/vardefs.php in two instances:

‘project_name’=> array(
‘name’=>‘project_name’,
‘rname’=>‘name’,
‘id_name’=>‘project_id’,
‘vname’=>‘LBL_PARENT_NAME’,
‘type’=>‘relate’,
‘join_name’=>‘project’,
‘table’=>‘project’,
‘isnull’=>‘true’,
‘module’=>‘Project’,
‘link’=>‘project_name_link’,
‘massupdate’=>false,
‘source’=>‘non-db’),

and

‘project_name_link’ =>
array (
‘name’ => ‘project_name_link’,
‘type’ => ‘link’,
‘relationship’ => ‘projects_project_tasks’,
‘vname’ => ‘LBL_PROJECT_NAME’,
‘link_type’ => ‘one’,
‘module’=>‘Project’,
‘bean_name’=>‘Project’,
‘source’=>‘non-db’,
),

And this seems to be the standard setting, nothing customized/altered after installation.

Any ideas what’s wrong here? is this a bug?

3

we are seeing this error in the logs now after upgrading to 7.8:

[ERROR] Unable to get proper side for link project_name_link

Did you vere discover a solution.

We are running into problems with the project module now:

Project and Project Template functionality does not work after upgrade from 7.4.x to 7.8.2:

Can not create new project template
Can not create new Project tasks for new project or using project template
Can not edit existing Project Tasks in Project Template

Log file Errors
Mon Mar 13 18:01:53 2017 [21025][1][ERROR] Unable to get proper side for link project_name_link
Diagnostic file attached

Centos 6.5
Apache
MySql
Php 5.6.3

1 Like
4

I am getting a similar error - after upgrade from 7.10.6 to 7.12.8 - Looking to clean things up.