GX-Bug #67444
Von Moritz Bunjes vor mehr als 3 Jahren aktualisiert
1. Install the Cookie Consent Module in the Module Center. Module. 2. Install the SingleSignOn Module in the Module Center. 3. Activate at least one SingleSignOn Service (no configuration needed) 4. Open the shop frontend 5. Go to the Cookie Consent Purposes Configuration 6. Module. Edit the purpose description of the SingleSignOn Cause in several times. Wait for a few minutes and reload the Cookie Consent Module configuration 7. Open page which displays the shop frontend again 8. Go to purpose description. SingleSignOn will be displayed twice - once with the Cookie Consent Purposes configuration again Expected result: The SingleSignOn edited purpose is shown description and once with the changed puprpose description Actual result: The SingleSignOn purpose is shown twice, the first one has the new description. Bug info: After saving changes of a SingleSignOn purpose, the shop frontend triggers the creation of a new purpose, because the alias in the database gets lost during the an update. "SingleSignOn".