An extension to the Aldryn Forms plugin that adds a Current User form field type. If there is a valid logged-in user session (request.user), that user’s information will be saved along with the form submission.
When you build your form, you can select to save the user’s:
User ID
Username
Email Address
Full Name
A “Current User Email Field” is also available that provides the same funcationality of the Aldryn Forms Email Field, allowing you to send the user who submitted the form an email confirmation.
Installation
Install via pip:
pip install djangocms-currentuser-field
Add to your INSTALLED_APPS (in settings.py):
INSTALLED_APPS = ( ... 'djangocms-currentuser-field', ... ) # Optional, if you'd like to use a subclass (1:1 relationship) attached # to user for the user id field, specify below CURRENTUSER_FIELD_USER_SUBCLASS = 'staff' # Optional, if you'd like to specify a custom fields off the user or # sub-user class, set a list of tuples: CURRENTUSER_FIELD_CUSTOM_VALUES = [ ('canvote', 'Voting Status') ]Run migrations:
python manage.py migrate djangocms-current-user
“Current User Field” should now be available as a plugin in the CMS when you build a form!
1 maintainer
Metadata
1 maintainer
Release files for djangocms-currentuser-field 0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| djangocms-currentuser-field-0.6.tar.gz | 10.2 kB | Without provenance | Details for djangocms-currentuser-field-0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| djangocms_currentuser_field-0.6-py3-none-any.whl | Python 3 | none | any | Details for djangocms_currentuser_field-0.6-py3-none-any.whl |
Total release size: 23.3 kB
Release files / djangocms-currentuser-field-0.6.tar.gz
| Download URL | djangocms-currentuser-field-0.6.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4396c06f03d4be9a88d7bb791884379a6c57c7dfe810aa4b2d2b97fe276fe99
|
|
BLAKE2b-256 checksum How to use checksums |
7e61facd13d7431a31650efebe8e0dfe5337522c79b3af0f78b65bc8b60ddb53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.55.0 CPython/3.8.5
|
Release files / djangocms_currentuser_field-0.6-py3-none-any.whl
| Download URL | djangocms_currentuser_field-0.6-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de41b522d50c2756ad7f8095aa5bd36e36bc9afd5db434b6d4a7de03fafd3b8e
|
|
BLAKE2b-256 checksum How to use checksums |
db205b96cf16ed9842f7b29108ba2152bbb107dd28fe6cb330fdb1046486dbdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.55.0 CPython/3.8.5
|
Security for djangocms-currentuser-field 0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
