View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004181 | OXID eShop (all versions) | 4. ------ eShop Core ------- | public | 2012-06-19 17:23 | 2012-12-10 13:42 |
| Reporter | FibreFoX | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Summary | 0004181: Making legacy-methods available as modules | ||||
| Description | I was thinking about deprecated methods/code, while looking at the list (http://wiki.oxidforge.org/Removed_deprecated_source) and throught to myself "how could it be easy used with old existing code?" -> make small modules containing an extend/overloading of the core-objects, so it is a safe way using deprecated stuff AND having a clean core WITHOUT having legacy-update-code (like https://bugs.oxid-esales.com/view.php?id=4172). Example: oxVendor::getrootvendor() -> oxvendor::load( 'root' ) one module for every version-step ... i dont know if it is the right position here. | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
