Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0009070
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformtrivialalways2009-05-18 12:382009-05-21 00:00
ReporternetworkbView Statuspublic 
Assigned Toalostale 
PriorityimmediateResolutionduplicateFixed in Version
StatusclosedFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.40MP3
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_11
OS VersionrPath LinuxDatabase version8.3.5Ant version1.7.1
Product Version2.40MP3SCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0009070: The messages in the application does not show linebreaks

DescriptionThis occurs in any message in the application, either warning, error .....
These messages usually appear on top of the windows do not show linebreaks
Steps To Reproduce1) Logged as System Administrator, go to Application Dictionary || Message and search for 'Process completed successfully' message.

2) Change it by:
Process completed


successfully

In database it is correctly stored as:
Process completed


successfully

select * from ad_message where msgtext like '%successfully%' order by updated desc

3) Run Synchronize Terminology process: Application Dictionary || Synchronize Terminology

When process ends message shown is: Process completed \nsuccessfully
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
duplicate of defect 0006379 closedgorka_gil Wrong message when system rebuild process is complete 
depends on backport 00090792.40MP3 closeddbaz The messages in the application does not show linebreaks 

-  Notes
(0016419)
rafaroda (viewer)
2009-05-18 12:45

Please specify Openbravo ERP version and detail the steps to reproduce the issue.

Thanks.
(0016431)
pnuding (viewer)
2009-05-18 16:41

corrected priority to immediate
(0016482)
alostale (viewer)
2009-05-20 08:36

In pi it is working, it was fixed by 0006379

- Issue History
Date Modified Username Field Change
2009-05-18 12:38 networkb New Issue
2009-05-18 12:38 networkb Assigned To => marvintm
2009-05-18 12:38 networkb OBNetwork customer => Yes
2009-05-18 12:38 networkb Regression testing => No
2009-05-18 12:45 rafaroda Note Added: 0016419
2009-05-18 12:45 rafaroda Status new => feedback
2009-05-18 16:41 pnuding Note Added: 0016431
2009-05-18 16:41 pnuding Priority low => immediate
2009-05-18 18:41 networkb version => 2.40MP3
2009-05-18 18:41 networkb Proposed Solution updated
2009-05-19 11:21 rafaroda Assigned To marvintm => alostale
2009-05-19 11:21 rafaroda Status feedback => new
2009-05-19 11:21 rafaroda Category Y. DBSourceManager => A. Platform
2009-05-19 11:21 rafaroda Proposed Solution updated
2009-05-19 11:21 rafaroda Status new => scheduled
2009-05-19 11:21 rafaroda fix_in_branch => pi
2009-05-20 08:36 alostale Relationship added duplicate of 0006379
2009-05-20 08:36 alostale Status scheduled => closed
2009-05-20 08:36 alostale Note Added: 0016482
2009-05-20 08:36 alostale Duplicate ID 0 => 6379
2009-05-20 08:36 alostale Resolution open => duplicate
2009-05-21 00:00 anonymous sf_bug_id 0 => 2794608


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker