Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0011201 | Openbravo ERP | B. User interface | public | 2009-10-31 02:58 | 2011-11-09 15:29 |
|
| Reporter | elopio | |
| Assigned To | dbaz | |
| Priority | low | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | |
| Platform | | OS | 20 | OS Version | Ubuntu 9.04 |
| Product Version | main | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0011201: Table in grid view has "undefined_table" as id |
| Description | The identifier of data table on grid view is "undefined_table"
This is the HTML code according to Firebug:
<table id="undefined_table_header" class="DataGrid_Header_Table" style="width: 1837px;"> |
| Steps To Reproduce | Go to General Setup || Client || Client || Client
Switch to grid view |
| Proposed Solution | Use a better identifier.
See the related issue. The fix on 2.40 should work here too. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0005516 | | closed | iperdomo | Two tables with same Id |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-10-31 02:58 | elopio | New Issue | |
| 2009-10-31 02:58 | elopio | Assigned To | => rafaroda |
| 2009-10-31 03:01 | elopio | Relationship added | related to 0005516 |
| 2009-10-31 03:07 | elopio | Note Added: 0021495 | |
| 2009-11-03 09:00 | rafaroda | Assigned To | rafaroda => shuehner |
| 2009-11-03 09:00 | rafaroda | Priority | normal => low |
| 2009-11-03 09:00 | rafaroda | Status | new => scheduled |
| 2009-11-03 09:00 | rafaroda | Category | Z. Others => B. User interface |
| 2009-11-03 10:12 | shuehner | Note Added: 0021528 | |
| 2009-11-03 10:24 | shuehner | Note Added: 0021530 | |
| 2009-11-03 10:41 | shuehner | Note Added: 0021531 | |
| 2009-11-03 10:41 | shuehner | Assigned To | shuehner => dbaz |
| 2009-11-30 06:34 | elopio | Note Added: 0022244 | |
| 2009-11-30 11:18 | shuehner | Note Added: 0022253 | |
| 2011-10-28 13:51 | dmitry_mezentsev | Note Added: 0042253 | |
| 2011-11-09 15:29 | dbaz | Note Added: 0042701 | |
| 2011-11-09 15:29 | dbaz | Status | scheduled => closed |
| 2011-11-09 15:29 | dbaz | Resolution | open => no change required |
|
Notes |
|
|
(0021495)
|
|
elopio
|
|
2009-10-31 03:07
|
|
This applies also to selectors:
Log In
Go to Master Data Management || Product
click new
click Storage bin selector
The data table here has the same id. |
|
|
|
|
|
Note: defect as is is different from the 2.40 issue. There seem to be no duplicate id's in this case here. Just the chosen id strings with 'undefined_X' in it are no good name elements. |
|
|
|
|
|
Issue is not present in 2.40, in 2.50 the grid does not construct its internal html element id_s with the grid-id prefix (usually grid) but uses the string 'undefined' instead. |
|
|
|
|
Issue is that inside the dojo widget instance for the DataGrid the property this.widgetId seems to not contain the widgetId anymore in 2.50, i did in 2.40.
@dbaz: could you please check if this is a problem of the DataGrid.js conversion to the new dojo done from 2.40 -> 2.50 ? |
|
|
|
(0022244)
|
|
elopio
|
|
2009-11-30 06:34
|
|
We also need to access the table header, currently identified as "undefined_table_header".
Those are the only two elements of the table we are currently using. However it would be great to define a better name for the elements identified as undefined_container and undefined_viewPort. |
|
|
|
|
|
I think all of the undefined will be replaced by the real id for the grid as specified in the base html if the bug inside the datagrid code is fixed. |
|
|
|
|
David, Stefan,
Could you please confirm that it is not applicable to OB3?
Thanks. |
|
|
|
(0042701)
|
|
dbaz
|
|
2011-11-09 15:29
|
|
Openbravo provides community support only for the latest Openbravo version, which is Openbravo 3. This version has significantly improved financial flow, filtering, performance, etc and this issue is not present there. Upgrade path from Openbravo 2.50 to latest Openbravo version is available so we recommend to upgrade your instance to get this issue fixed.
Life cycle guarantee (backporting bug fixes to the previos to latest releases (Openbravo 2.40, 2.50)) is available for Professional Edition subscribers only. Please register your ticket through Openbravo Support Portal (http://support.openbravo.com/ [^]) if you have valid Professional subscription.
You can find more details about our Support policy in the following blog post
http://paolojuvara.blogspot.com/2009/12/maintenance-policy-for-openbravo-250.html [^] |
|