As part of authn redesign, validation messages have been updated.
- created a new endpoint for validations
- updated username/email conflict message in registration api based on
authn check
VAN-288
This change embraces persistent min-version dependencies, which can
simply be ratcheted up over time, or safely removed in time because IDAs
rarely have a large dependency downgrade.
Some dependencies are already encoded with a min-version constraint, which
makes the previous instructions confusing. There was also a very minor
issue in which the temporary constraint line was adding a spurious
`-c constraints.txt` to the committed changes, even though the constraint
itself was not being committed.
This change inspired by discussion on PR #27506.
Currently, course staff can always view their courses
in the Legacy courseware experience.
With this change, course staff will *not* be able
to view their courses if the New (MFE) courseware
experience has been enabled for them.
This does not affect global staff, and it does not
affect courses that are still running in the Legacy
experience.
Adds a new parameter returned by the course metadata API
used by the courseware MFE to determine if the button to
show legacy experience should be displayed or not.
TNL-8203
Enterprise was still using email_marketing code. This will bump
enterprise to a version that does not any more. And also temporarily
put the email_marketing model back for blue/green deploy sanity.
* docs: ADR for exposing existing studio views through new JWT-enabled endpoints
To allow MFEs to drive existing studio functionality, we need to expose that
functionality via REST APIs that can be used by MFEs. This ADR describes an
approach to do that.
* Update cms/djangoapps/contentstore/docs/decisions/0002-restful-studio-apis-for-MFE.rst
Co-authored-by: Farhaan Bukhsh <farhaan@opencraft.com>
* Update cms/djangoapps/contentstore/docs/decisions/0002-restful-studio-apis-for-MFE.rst
Co-authored-by: Kyle McCormick <kdmc@pm.me>
Co-authored-by: Farhaan Bukhsh <farhaan@opencraft.com>
Co-authored-by: Kyle McCormick <kdmc@pm.me>
This follows on the commit that gutted the email_marketing djangoapp
by actually dropping the model from code and database.
The djangoapp could now be removed after Maple releases.
AA-607
[MICROBA-1178]
- remove modulestore usage in `generation_handler.py`
- add duplicate functions that utilize a CourseKey or CourseOverview to remove dependence on modulestore (this will be cleaned up (if possible) at a later part of this refactor)
- add python API function to `content`/`course_overview` app that will retrieve a single CourseOverview (rather than a serialized list of dicts of CourseOverview data)
Upgrade edx-django-utils to bring in the new
code_owner_squad custom attribute for
monitoring purposes. See the edx-django-utils
changelog for details.
ARCHBOM-1551
This djangoapp was designed for talking to sailthru, in a fairly
edx.org-specific way. Nowadays, edx.org doesn't need this code and
if other installations do, it's better off as a more distinct
plugin anyway, rather than direct support in the platform.
I've moved the one signal that was still useful (calling
segment.identify() whenever user fields change) into user_authn.
And I've left the EmailMarketingConfiguration model alone for now,
but will remove that shortly. Nothing uses it as of this commit.
AA-607
DEPR-139
The course name can contain apostrophes and other special characters. The email template right now escapes every words. This is not desired because it can render apostrophes like #39;. Update the email templates so only second half of the email template is escaped
If a certificate available date was set on a self paced course, it would
show text to the learner saying that the grades would be available in
the future when that was inaccurate.
* fix: pin python-slugify<5.0.0
transifex-client requires python-slugify<5.0.0 for Python 2.0 support which conflicts with the latest python-slugify version.
Modify the existing login api in a way that
it will allow the user to login via username as well.
currently it is only allowing email to log the user in.
VAN-445
* Commits:
docs: Remove completed TODO discussions item
feat: Add support to Discussions API for legacy cohort settings
refactor: Remove get_course_discussion_settings helper
refactor: Remove set_course_discussion_settings helper
refactor: Add better DRF support to legacy discussions settings
