============
Adds an 8 year old version of `jquery-cookie <https://github.com/carhartl/jquery-cookie>`_ to plone.
Usage
=====
Set the value of a cookie.
$.cookie('the_cookie', 'the_value');
Create a cookie with all available options.
$.cookie('the_cookie', 'the_value', { expires: 7, path: '/', domain: 'jquery.com', secure: true });
Create a session cookie.
$.cookie('the_cookie', 'the_value');
Delete a cookie by passing null as value. Keep in mind that you have to use the same path and domain used when the cookie was set.
$.cookie('the_cookie', null);
Links
=====
* Main github project repository: https://github.com/4teamwork/collective.jqcookie
* Issue tracker: https://github.com/4teamwork/collective.jqcookie/issues
Copyright
=========
This package is copyright by `4teamwork <http://www.4teamwork.ch/>`_.
``collective.jqcookie`` is licensed under GNU General Public License.
Changelog
=========
1.1.0 (2014-02-12)
------------------
* Moved package from svn to GitHub.
[lknoepfel]
1.0a4
-----
1.0a3
-----
1.0a2
-----
1.0
---
* Initial release
Release files for collective.jqcookie 1.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 | Actions |
|---|---|---|---|---|
| collective.jqcookie-1.1.0.zip | 15.1 kB | Without provenance | Details for collective.jqcookie-1.1.0.zip |
Security for collective.jqcookie 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
