View Issue Details

IDProjectCategoryView StatusLast Update
0002369OXID eShop (all versions)2. ----- eShop backend (admin) -----public2012-12-10 15:34
Reporterfinnegan Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status resolvedResolutionno change required 
Summary0002369: Configuring a subshop for _not_ allowing individual article prices renders short description of master shop instead of subshop
Description- 1 Mastershop, several subshops
- if you deselect "Allow individual price for inherited article" in the basic settings of a subshop you will not be able to edit the article short description of an article inherited from the master shop any more.
Steps To Reproduce- Login to Admin
- select subshop A
- in basic settings->mall deselect "Allow individual price for inherited article"
- select master shop
- Create an article in the master shop, make it visible in subshop A
- enter a short description in master shop
- change admin to subshob A, select same article
- change the short description to something else, save

Result: changes will not be saved, input field always shows short description of MASTERshop instead of subshop A

- after checking once again the checkbox "allow individual price" then the short description field of a mastershop article inherited in a subshop will work again as expected
TagsNo tags attached.
Theme
Browser
PHP Version
Database Version

Activities

dainius.bigelis

2011-01-14 16:12

reporter   ~0003974

Reminder sent to: finnegan

Hi,

Just to be sure: you were using Internet Explorer when working on this case in Admin?

Best regards,

dainius.bigelis

2011-01-14 16:34

reporter   ~0003976

Reminder sent to: finnegan

Also other question:
do you have set config option aMultishopArticleFields in config.inc.php (also created needed fields in table oxfield2shop) to be able to edit wanted fields (like description) in the subshop?
if No - by default you cannot edit article data in the subshop, if article is inherited from Master shop.

In this case you are confused by shop because there is a bug, that using IE in subshop the product data fields are displayed as editable, when it should be read-only.

Best regards,

finnegan

2011-01-14 17:30

reporter   ~0003980

Hi dainius,

1. I have tested this behaviour using Firefox 3.6

2. "do you have set config option aMultishopArticleFields in config.inc.php (also created needed fields in table oxfield2shop) to be able to edit wanted fields (like description) in the subshop?" - YES

$this->aMultishopArticleFields = array("OXPRICE", "OXPRICEA", "OXPRICEB", "OXPRICEC", "OXLONGDESC", "OXSHORTDESC");

regards

arvydas_vapsva

2011-02-11 15:14

reporter   ~0004108

Last edited: 2011-02-14 08:28

OXLONGDESC/OXSHORTDESC are multilanguage. Did you add OXLONGDESC_x/OXSHORTDESC_x? Does count of them matches count from oxarticles table?

arvydas_vapsva

2011-02-14 08:37

reporter   ~0004115

Reminder sent to: finnegan

please check comment..

finnegan

2011-02-18 20:38

reporter   ~0004140

"OXLONGDESC/OXSHORTDESC are multilanguage. Did you add OXLONGDESC_x/OXSHORTDESC_x?"

Yes (not by me, the shop was set up by Oxid staff)

"Does count of them matches count from oxarticles table?"

No.

In oxarticle I have oxshortdesc, oxshortdesc_1, oxshortdesc_2, oxshortdesc_3
In oxfield2shop there is only oxshortdesc, oxshortdesc_1
Same for oxlongdesc

BTW: oxlongdesc is in table oxartextends, not in oxarticle

BUT we are using only 1 language (DE) and the shop system is configured for only 2 languages (DE and EN). So 2 fields should be sufficient, right?

arvydas_vapsva

2011-03-07 09:34

reporter   ~0004184

"BUT we are using only 1 language (DE) and the shop system is configured for only 2 languages (DE and EN). So 2 fields should be sufficient, right? "

NO, not right, there MUST be ALL fields

dainius.bigelis

2011-03-31 07:51

reporter   ~0004271

Reminder sent to: finnegan

Hi,

We close this bug entry, as we cannot reproduce it, and it's probably occurred because incorrect setup of eShop for such requirements.
We will inform our support staff about how this case should be solved, to avoid such problems in the future.
To solve your problem - please ping our support once again, with request to fix this case and include the link to this issue.
Thank you for your report.

Best regards,