View Issue Details

IDProjectCategoryView StatusLast Update
0006244OXID eShop (all versions)3.1. Design, GUI, UXpublic2022-01-31 10:32
Reportera4p ASD Assigned To 
Status resolvedResolutionfixed 
Product Version4.9.5 / 5.2.5 
Summary0006244: extend persParam functionality (pull request)
Descriptioni created a pull request 'feature/PR_persparams_handling' for feature request 31940 from oxid-uservoice

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 Informationbetter 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.
TagsNo tags attached.
ThemeNot defined
BrowserNot defined
PHP VersionNot defined
Database VersionNot defined


a4p ASD

2015-10-12 11:26

reporter   ~0011259

also see mantis 0001798


2022-01-31 10:32

administrator   ~0013590

I would say the Requirement was already fulfilled. Unfortunately the UserVoice instance was meanwhile closed and the PR was lost.
Nonetheless 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.