View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001211 | OXID eShop (all versions) | 1. ----- eShop frontend ----- | public | 2009-08-17 16:03 | 2012-12-10 14:16 |
| Reporter | andreas_ziethen | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Product Version | 4.1.4 revision 21266 | ||||
| Summary | 0001211: parameter shp overwrites domain dependent shop id | ||||
| Description | If you have shop-urls with for example "/shp=2" then the logic in oxconfig::getShopId() takes this one as actual shop-id instead of the domain-dependent shop-id. I think this should be changed, cause e. g. it leads to big problems if shop-structure and shop-ids have changed but google still keeps some links with the old shp-parameter. If there are explicit domains for subshops then I think the domain should ALWAYS overrule any other shop-id parameter (appart from admin access). | ||||
| Tags | Subshops | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.2.6 | ||||
| Database Version | 5.0.33 | ||||
|
|
Reminder sent to: andreas_ziethen Hi, Basically this parameter "shp" should not be used in the url. Do you get this in default shop version (if yes - please tell where, in what case), or is it appended by some module, which is installed in the shop? Best regards, |
|
|
Reminder sent to: andreas_ziethen Hi, The basic idea is clear: you want that domain would have higher priority than ShopId. But the problem is - that if you want to know the domain of the shop - you need to have it's ShopID. And in this case - when you are working in some shop X with it's own domain, but overriding some other shops ID using "shp" in the url (what basically - shouldn't be there) - it get's confused. Question - is this "shp" parameter in url is really needed or not, because in this case it's probably implemented in some modules. To have requested behavior - it would need changes in some base functionality, and is more like a feature request. So for now the entry here is closed and the request is moved to customers whishlit for deeper consideration. Best regards, |
|
|
Hi, sorry, I did not see your questions immediately. This appears when there's a migration from EE 2.7 to EE 4. Because then very often you do have URLs with "shp=..." in the Google index. Best regards, Andreas |
|
|
Thank you for an answer. Now it's clear about this parameter. But it's still hard to find solution for this case, especially when this is affected by data stored outside. We'll consider how this can be solved. For now it still remains in customers whishlist. |
