View Issue Details

IDProjectCategoryView StatusLast Update
0006986OXID eShop (all versions)2.4. Administer productspublic2024-06-12 11:14
Reporterdait Assigned To 
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionno change required 
Product Version6.1.3 
Summary0006986: SEO-URL of Subshops not editable - OXID EE all Versions
DescriptionSEO-URLs are not editable within subshops when article is inherited by supershop.
Neither input for SEO-URL is possible in subshop (deactivated) nor a change of SEO-URL in supershop is passed to subshop.

By this it is not possible to have an URL different from the standard scheme for an article in a subshop.
Steps To ReproduceSet shop A as supershop and shop B as multishop with inheritance of articles of shop A to shop B.
Add new article in shop A.
Change SEO-URL of article in shop A.
Check SEO-URL of article in shop B.
Additional InformationThis should be considered as bug because there are good reasons for the possibility to change the SEO-URL for an article. It is possible in PE, CE and supershop. It also should be possible in a subshop eventually by making SEO-URL editable within the subshop. Right now input is deactivated.
TagsNo tags attached.
ThemeNot defined
BrowserNot defined
PHP VersionNot defined
Database VersionNot defined

Activities

simon.runer

2019-05-28 16:50

reporter   ~0012899

I would say, this is not a "kleinerer Fehler" but a huge problem in a multishop environment. We just discovered the same problem today.

SvenBrunk

2024-06-12 11:14

administrator   ~0017012

Sorry, but your report is invalid.
You are actually creating an invalid setup (which is basically an infinite loop):
You set shop A as Supershop (which will inherit all products from all shops) and make a subshop of it as shop B inheriting everything from Supershop A.
That is no valid scenario.
The only problem here that I can see, is that the shop framework lets you do such things.
Apart from that I am really amazed that the whole setup didn't just explode into your face.

If this happens in other setups as well, please re-open the ticket with more information.