View Issue Details

IDProjectCategoryView StatusLast Update
0006935OXID eShop (all versions)2.4. Administer productspublic2019-03-27 08:03
Reporternexonic_de 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformWindowsOSChromeOS VersionVersion 71.0.357
Product Version4.10.8 / 5.3.8 
Target VersionFixed in Version 
Summary0006935: Saving new product doesn't work anymore
DescriptionSaving new product doesn't work anymore AFTER clicking "btn.new" - button for saving (#oLockButton) stays disabled.
Apparently only affecting chrome - tested in 71.0.357 - 64bit
Works in IE/Edge
Steps To Reproduce1) "Manage products" in admin
2) adding a product works on first "visit"
3) Click action link for adding a new product at frame bottom
4) now saving is not possible anymore - button for saving stays in "disabled" state
After a full page reload saving new product works again
Additional Informationno console errors in JS debugger
TagsNo tags attached.
ThemeNot defined
BrowserGoogle Chrome
PHP VersionNot defined
MySQL VersionNot defined

Relationships

has duplicate 0006936 closedbenjamin.joerger Save button is disabled after refresh only iframe 

Activities

QA

2019-01-03 07:54

administrator   ~0012748

Last edited: 2019-01-15 07:47

View 2 revisions

Reproduced on Ubuntu 18.04, Chrome 71.0.3578.98 (64 bit) and shop version EE 6.1.1

-MK

marco_steinhaeuser

2019-01-16 10:37

administrator   ~0012763

There's a solution for it as a module here:
https://forum.oxid-esales.com/t/bei-neuen-artikel-anlegen-unter-chrome-bleibt-das-feld-speichern-passiv/94673/13

leofonic

2019-01-16 11:04

reporter   ~0012764

This module is an option to get it working again, the problem itself has to be fixed by chrome. According to the note in the chrome bug this will be fixed in chrome version 73, which should be released in march.

QA

2019-01-16 11:42

administrator   ~0012765

@leofonic: Thank you for the further information. I will make a myself a reminder to check it again after the next release of a new Chrome version.

-MK

QA

2019-03-27 08:03

administrator   ~0012826

Works again with Chrome 73.
-MK