Introduction
This package implements Cory LaViska’s ‘JQuery Alert Dialogs’ for Plone.
Basically, they are fancy, styleable replacements for the standard ‘alert’, ‘confirm’ and ‘prompt’ browser functions.
See http://abeautifulsite.net/blog/2008/12/jquery-alert-dialogs/ for more details.
Usage
When collective.alerts is installed and the jquery.alerts library registered in portal_javascripts (should be automatic), then the alerts can be called as follows:
jAlert( message, [title, callback] )
jConfirm( message, [title, callback] )
jPrompt( message, [value, title, callback] )
Dependencies:
On Plone 3.x, make sure that you have a newer version of JQuery than what is shipped with Plone. That would be JQuery > 1.3.5
The easiest way to do this is to install collective.js.jquery.
Plone 4.x users already have a new enough version of JQuery.
Changelog
1.2.3 (2011-02-08)
Removed the setup.py dependency on collective.js.jquery (not needed for Plone 4) [jcbrand]
Added GS-XML (metadata.xml) dependency on collective.js.jqueryui [jcbrand]
Added css for the popup [jcbrand]
1.2.2 (2010-04-12)
Add jquery dependencies to setup.py [jcbrand]
1.2.1 (2010-01-27)
Remove collective.js.alerts from css registry [toutpt]
1.2 - (2009-10-05)
Released
Release files for collective.alerts 1.2.3
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 |
|---|---|---|---|---|
| collective.alerts-1.2.3.tar.gz | 13.9 kB | Without provenance | Details for collective.alerts-1.2.3.tar.gz |
Release files / collective.alerts-1.2.3.tar.gz
| Download URL | collective.alerts-1.2.3.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
563742397113ec389f50593be70f16aa3f8a36cca8c88c6002f8fa547c33acb5
|
|
BLAKE2b-256 checksum How to use checksums |
7787226312edcbde89d554df652c26af0e14e7de4486a19061eafb2a9cb65a3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.alerts 1.2.3
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.
