============
Changelog
===========
0.7.0
-----
* Improved template engine detection, didn't work well for unsupported engines. Now admin properly displays when using Kajiki
* Admin.make_controller is now a public method so that users can leverage it to create new CRUD controllers with Admin lookandfeel
0.6.6
-----
* Fix for allow_only not accepting custom predicated
* Preliminary support for Sprox version with subdocuments editing
0.6.0
------
Support for Layouts in TGAdminConfig with Bootstrap3 Layout
0.3
----
Lookup now uses ProviderSelector, for better mongo support
0.2.6
-----
Bugfix release. Support for _method fields in TG2.1
0.2.5
------
* Addition of defaultCrudRestController to
CRCConfig allows one to customize the controller
that the admin uses.
* Fixes tgadminconfig to override the Password properly for Users
Release files for tgext.admin 0.7.4
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 | |
|---|---|---|---|---|
| tgext.admin-0.7.4.tar.gz | 14.9 kB | Without provenance | Details |
Release files / tgext.admin-0.7.4.tar.gz
| Download URL | tgext.admin-0.7.4.tar.gz |
|---|---|
| Size | 14.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
445364cc94facb1dce444073dcd9fa19ef17aee09f8a646311292e323b288719
|
|
BLAKE2b-256 checksum How to use checksums |
04765cb124e5942feec21acfb19a600b7fd22f4adc30466d589cc18699409fbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tgext.admin 0.7.4
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.
