When accessing a borrower detail page, the following lines appear in the logs: [Wed Feb 1 15:55:44 2012] moremember.pl: Use of uninitialized value in concatenation (.) or string at /home/asaurat/workspace/versions/community/C4/Members/Messaging.pm line 216. [Wed Feb 1 15:55:44 2012] moremember.pl: Use of uninitialized value in concatenation (.) or string at /home/asaurat/workspace/versions/community/C4/Members/Messaging.pm line 216. [Wed Feb 1 15:55:44 2012] moremember.pl: Use of uninitialized value in concatenation (.) or string at /home/asaurat/workspace/versions/community/C4/Members/Messaging.pm line 216.
Created attachment 7411 [details] [review] proposed patch
Comment on attachment 7411 [details] [review] proposed patch Proposed a very simple patch with minimal consequences. It will correct the bug and nothing more. But maybe we could go further, if the 'transport_X' is not mandatory it may be better to avoid sending anything when the 'message_transport_type' is not defined (NULL in DB).
Can you provide a test case where message_transport_type would be undefined? Under what circumstances is this allowed? It doesn't seem logical to me (at first blush) that this should come up under any normal usage scenario, so finding the root of the problem and fixing it there may be a better course of action, rather than chasing down manifestations like this.
I cannot reproduce this error. Could you explain the steps to reproduce?
Adrien, I have got the same problem on my install. I don't know why. Execute queries in installer/data/mysql/.../sample_notices_message_transports.sql to populate your message_transports table. It should fix these warnings.
(In reply to comment #5) > Adrien, > I have got the same problem on my install. I don't know why. Execute queries > in installer/data/mysql/.../sample_notices_message_transports.sql to > populate your message_transports table. > It should fix these warnings. Jonathan, Does that mean that this bug should be marked INVALID or WONTFIX?
With a message_transport table fully populated, the logs are indeed ok. Don't know yet why I didn't have all the lines, though. I close this bug.