View Issue Details

IDProjectCategoryView StatusLast Update
0006880OXID eShop (all versions)1.01. Products (product, categories, manufacturer, promotions etc.)public2022-03-15 12:15
Reporterd3 Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version4.10.8 / 5.3.8 
Fixed in Version6.4.2 
Summary0006880: oxseo and oxseohistory entries will not deleted by deletetion of oxvendor and oxmanufacturer
DescriptionReproduction:
1. manufacturer
go to admin/manufacturer -> select "Cabrinha" f.e. -> copy seo url from seo tab "en/By-Manufacturer/Cabrinha/"
delete manufacturer "Cabrinha"
Enter shopurl with seo url: domain.de/en/By-Manufacturer/Cabrinha/
an empty page will be displayed -> have to be an 404 error

open database an execute query:
SELECT * FROM `oxseo` WHERE oxseourl = 'en/By-Manufacturer/Cabrinha/';
an existing entry will be displayed

if the manufacturer was renamed, the oxseohistory entries remains.

2. vendor
go to admin/vendor -> select "www-true-fashion-com" f.e. -> copy seo url from seo tab "en/By-distributor/www-true-fashion-com/"
delete vendor "www-true-fashion-com"
Enter shopurl with seo url: domain.de/en/By-distributor/www-true-fashion-com/
an exception occurs: "vendor/oxid-esales/oxideshop-ce/source/Application/Controller/VendorListController.php] [line 446] [message Call to a member function getId() on boolean]"
 -> have to be an 404 error

open database an execute query:
SELECT * FROM `oxseo` WHERE oxseourl = 'en/By-distributor/www-true-fashion-com/';
an existing entry will be displayed

if the vendor was renamed, the oxseohistory entries remains.


best regards
Kristian
TagsDatabase, Exception, Manufacturer, SEO, Vendor
ThemeNot defined
BrowserNot defined
PHP VersionNot defined
Database VersionNot defined

Relationships

related to 0006304 resolvedflorian.auer oxseohistory is left untouched when deleting entities like oxArticle, oxCategory, oxContent, oxManufacturer, oxVendor 

Activities

d3

2018-08-10 10:46

reporter   ~0012569

the behaviour is reproducable in 4.10.x/5.3.x as well in 6.1.0

Kristian

michael_keiluweit

2018-08-13 07:32

administrator   ~0012571

@dev: when closing or marking this one as resolved, please consider to elaborate 0006304 also.

anton.fedurtsya

2022-03-15 12:15

administrator   ~0013797

Now the problem is fixed in b-6.4.x and up.