Dnn.Platform icon indicating copy to clipboard operation
Dnn.Platform copied to clipboard

Account Login Module crashes on 'update profile' - CKEditor ref error

Open Navilois opened this issue 3 years ago • 4 comments

Description of bug

When a user, whose profile is missing a required field, tries to login using the Account Login Module, the "Please update your profile before continuing." crashes and is stuck loading. In my case, this affects users having an older profile, which don't have a custom required field filled out that has been added since as well as missing the preferred language selection.

Steps to reproduce

List the precise steps to reproduce the bug:

  1. Go to Persona Bar -> Manage -> Users -> Add user
  2. Add names, Email and password and save. You also need to have set up required fields not showing up here
  3. Go to a page using the Account Login Module (non modal)
  4. Login with the new accounts username and password
  5. See error

Current behavior

The 'Please update your profile before continuing.' part of the login loads, followed by loading.gif overlay. Loading never stops and the profile cannot be updated.

Expected behavior

Properly load the inputs and allow updating the profile.

Screenshots

UpdateProfile0

Error information

Console log: See console log and screenshot. console-export-2021-2-23_10-53-25.txt UpdateProfile1

Additional context

Possibly related to the recent CKEditor update. Please note, that it does work when using the native default way of loging in not using the module.

Affected version

  • [ ] 10.00.00 alpha build
  • [ ] 09.09.00 release candidate
  • [ X ] 09.08.01 latest supported release

Affected browser

  • [ X ] Chrome
  • [ X ] Firefox
  • [ ] Safari
  • [ ] Internet Explorer 11
  • [ ] Microsoft Edge (Classic)
  • [ ] Microsoft Edge Chromium

Navilois avatar Feb 23 '21 09:02 Navilois

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

stale[bot] avatar Jun 02 '21 16:06 stale[bot]

Still an issue

Navilois avatar Jun 04 '21 08:06 Navilois

We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically. If new comments are are posted and/or a solution (pull request) is submitted for review that references this issue, the issue will not be closed. Closed issues can be reopened at any time in the future. Please remember those participating in this open source project are volunteers trying to help others and creating a better DNN Platform for all. Thank you for your continued involvement and contributions!

stale[bot] avatar Sep 03 '21 01:09 stale[bot]

I had this on one upgrade from a really bad original site with all kinds of funky stuff. I worked around it by making the biography field not rich-text. Unstaled the issue in case anyone has some steps accurate steps to reproduce from a clean upgrade

valadas avatar Sep 06 '21 02:09 valadas