View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005071 | OXID eShop (all versions) | 2.4. Administer products | public | 2013-04-15 16:38 | 2013-05-06 08:19 |
| Reporter | finnegan | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.7.3 / 5.0.3 revision 54408 | ||||
| Target Version | 4.7.5 / 5.0.5 | Fixed in Version | 4.7.6 / 5.0.6 | ||
| Summary | 0005071: EE: save article in subshop is not possible if oxprice is excluded from aMultishopArticleFields | ||||
| Description | If in EE you have an article in the master shop and make certain fields editable in a subshop the "save" button is greyed out if oxprice is not included in the aMultishopArticleFields array in config.inc.php. In our case we do _not_ want to make oxprice editable in a subshop but we want to edit short and long desc. So I edited aMultishopArticleFields to include only those fields we want to have editable in a subshop. After that the save button in article_main is greyed out. The reason seems to be the test in the template article_main: [{if $readonly && (!$edit->canUpdateField('oxprice') || $edit->isParentNotBuyable())}][{$readonly}][{/if}] So if I exclude oxprice from aMultishopArticleFields canUpdateField returns false and the button is greyed out. | ||||
| Additional Information | Furthermore I have to check "Allow individual prices for derived articles" in the subshop config even if I do _not_ want individual prices in subshops. Otherwise function "public function canUpdateField( $sField )" will always return false which will set even those fields to readonly that I _do_ want to have editable in subshops (e.g. short desc). Maybe the checkbox description in shop config should be more clear about that. | ||||
| Tags | Products, Subshops | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
