WARNING
This package is superseded by collective.js.fancybox which contains the same functionality but uses better namespace. Please use collective.js.fancybox for new sites. There is no migration step provided from collective.fancybox to collective.js.fancybox though.
Introduction
Simple package which makes fancybox available in portal_javascript. This package does not change nor define any view or templates. It basically does nothing from the user point of view. It is usable for template developers to avoid several fancybox libraries registered from different products.
Problems
Please note, Plone often generates image URLs without extension suffix, eg. http://host/portal/news/news-item/image_preview returns correct image to the browser with correct content type set, but Fancybox does not handle such URLs correctly. Fancybox competitor, Thickbox, works fine in this situation.
From FancyBox FAQ:
6. I`m using custom urls for images (for example,
index.php?action=dlattach;topic=3.0;attach=9;image) and FancyBox shows source
of image. Why?
FancyBox gueses content type from url but sometimes it can be wrong. The
solution is to force your type, like so - $(".selector").fancybox({'type' :
'image'});
Usage
Fancybox requires custom invocation of the library. You must write custom javascript which binds fancybox code to particular tag. Define your own JS file, register it (portal_javascripts, javascript_head_slot) and use jQuery syntax to bind fancybox to the tags:
jq(function() {
jq("a.fancybox").fancybox();
});
More detailed configuration may be passed as arguments of fancybox() function. Please read http://fancybox.net/howto chapter 4 - Fire plugin using jQuery selector and Available options.
Changelog
0.5.1 - 2011-10-08
Fixed relative URLs for IE in CSS file
0.5 - 2011-09-22
Updated to fancybox 1.3.4
0.4.1 - 2010-04-17
Fixed order in portal_javascripts
Fixed image names for IE
added z3c autoinclude plugin
0.4 - 2010-04-17
CSS file is DTML resource now
0.3 - 2010-04-14
fixed paths in CSS file
0.2 - 2010-03-15
Updated to fancybox 1.3.1
0.1 - 2009-08-26
Initial release
Metadata
Release files for collective.fancybox 0.5.1
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 | |
|---|---|---|---|---|
| collective.fancybox-0.5.1.zip | 73.4 kB | Without provenance | Details |
Release files / collective.fancybox-0.5.1.zip
| Download URL | collective.fancybox-0.5.1.zip |
|---|---|
| Size | 73.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9c407afae37bfc7e03b9271b9fd61a999015a10da2a5eb988f57529b4a874cd
|
|
BLAKE2b-256 checksum How to use checksums |
3a4dceb81d73db62b9a88514f69e8db3ead0b411d33f0174854173b0f7762b6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.fancybox 0.5.1
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.