You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/13 21:20:00 UTC
[jira] [Commented] (VCL-993) web code should handle user.IMtypeid
being NULL
[ https://issues.apache.org/jira/browse/VCL-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086428#comment-16086428 ]
ASF subversion and git services commented on VCL-993:
-----------------------------------------------------
Commit 1801892 from arkurth@apache.org in branch 'vcl/trunk'
[ https://svn.apache.org/r1801892 ]
VCL-993
Updated calls to $self->data->get_user_imtype_name() to set the return value to 'none' if it's set to NULL in the database to prevent vcld.log uninitialized concatenation warnings.
> web code should handle user.IMtypeid being NULL
> -----------------------------------------------
>
> Key: VCL-993
> URL: https://issues.apache.org/jira/browse/VCL-993
> Project: VCL
> Issue Type: Bug
> Components: web gui (frontend)
> Reporter: Josh Thompson
> Fix For: 2.5
>
>
> With the efforts to make fields in the database that relate to other tables to be NULL when no value from the other table should be set (rather than using 0), getUserInfo was broken when user.IMtypeid is NULL.
> As an aside, given that IM notification is not used any more, it may be a good idea to remove the field altogether.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)