Django WYMEditor
A Django application that contains a widget to render a form field with a WYMEditor interface.
Requirements
Currently integration with django-filebrowser or django-bfm is hard-coded in. This will be fixed in a future version. For now, make sure you have django- filebrowser installed and included in your INSTALLED_APPS, and that one of the following is in your URLconf:
# For django-filebrowser
urlpatterns += patterns('',
(r'^admin/filebrowser/', include('filebrowser.urls'))
)
# For django-bfm
# Hack for WYMEditor hardcoded link URL... :-(
from django.views.generic import RedirectView
urlpatterns += patterns('',
url(r'^admin/filebrowser/browse/', RedirectView.as_view(url="/admin/files/")),
url(r'^admin/files/', include('django_bfm.urls'))
)
With that, you should have full filebrowser integration w/ WYMEditor.
1 maintainer
Metadata
1 maintainer
Release files for django-wymeditor 1.0
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 | |
|---|---|---|---|---|
| django-wymeditor-1.0.tar.gz | 163.9 kB | Without provenance | Details |
Release files / django-wymeditor-1.0.tar.gz
| Download URL | django-wymeditor-1.0.tar.gz |
|---|---|
| Size | 163.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29f3c48d2e8343d4ea717463fca25947ec37cd8be1460953d696e069631ae73a
|
|
BLAKE2b-256 checksum How to use checksums |
17f8ef8ebefb4cae2b71a8fca54433da5029340e65255ca0ed81e5fe09453cd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-wymeditor 1.0
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.
