View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001721 | OXID eShop (all versions) | 4.07. Source code, Test | public | 2010-03-25 11:40 | 2013-08-30 15:25 |
| Reporter | alfonsas_cirtautas | Assigned To | |||
| Priority | urgent | Severity | block | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.2.0 revision 23610 | ||||
| Fixed in Version | 4.5.1 revision 38045 | ||||
| Summary | 0001721: Missing functionality for custom component handling | ||||
| Description | in oxubase we have array for custom components: Names of components (classes) that are initiated and executed before any other regular operation. User may modify this himself. protected $_aUserComponentNames = array(); The only way to set this array is to override it in view class. Creating global custom component will require to extent/modify all existing views. Better solution needed. | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| related to | 0002865 | resolved | arvydas_vapsva | noncachable user components are not inititialised in initNonCacheableComponents |
|
|
since this issue is open for over a year now: For a start please load aUserComponentNames from config.inc |
|
|
+1 for defining user-components in config.inc.php. This is easy to fix. Can someone increase the severity please, because this bug makes use of components for extensions useless. Most people extend viewconfig thousend of times but in many cases it would be cleaner to create a user component. |
