View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006244 | OXID eShop (all versions) | 3.1. Design, GUI, UX | public | 2015-10-12 11:23 | 2022-01-31 10:32 |
| Reporter | a4p ASD | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.9.5 / 5.2.5 | ||||
| Summary | 0006244: extend persParam functionality (pull request) | ||||
| Description | i created a pull request 'feature/PR_persparams_handling' for feature request 31940 from oxid-uservoice http://oxid.uservoice.com/forums/31940-feature-requests/suggestions/1013223-extend-persparam-functionality this pr is not finished and maybe not fully working - only my idea of how the persparams should be improved. i extended oxView and all templates in which persparams occur. i moved the output of persparams in two templates (persparams_input and persparams_output; azure and admin), then you have to change only 2-3 blocks instead of 9. Or you extend oxView and change the new persparam functions. | ||||
| Additional Information | better solution: the persparams should become an own model and table and an assignment-table persparam2object. And everything in the admin to create a persparam and assign them to an article and make them invisible or something. | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
also see mantis 0001798 |
|
|
I would say the Requirement was already fulfilled. Unfortunately the UserVoice instance was meanwhile closed and the PR was lost. Nonetheless https://github.com/OXID-eSales/oxideshop_ce/search?q=persparams tells me, that in the current shop version, there is only one include file that contains the persparams and there is no more need to adapt multiple files. |
