=============
collective.slideshare does not add any new contenttypes. It adds new
views for your `Link` and `File` (currently archetypes only) contenttypes.
Configuration
-------------
You have to configure collective.slideshare first to be able to use it.
It requires an API KEY and a SHARED SECRET. Additionally you may provide
a username and password. If you do not provide usermane and password
you will be prompted for those every time you upload a file to slideshare.
You can obtain an API KEY at http://www.slideshare.net/developers/applyforapi
You can specify a policy for this behaviour:
* Always use the credentials provided, never prompt user for input
* Always ask user for his credentials
* Allow user to supply his credentials, if none are provided use the system credentials
Files can be automatically uploaded to SlideShare_ when you 'publish'
them. For this to work a workflow must be activated for Files and you
have to provide credentials and the policy must not require the user
to supply his own credentials.
Links
-----
When you add a link to a SlideShare_ presentation the product retrieves the
slideshare_id from SlideShare_ and embeds the presentation in your page.
Do NOT use the link given in the slideshare `<> Embed` option!
You can (de)activate the 'SlideShare View' at any time.
Files
-----
When you upload a Presentation you can change the view to 'SlideShare View'.
You will then be asked to provide your credentials to add this file to
SlideShare_ and the presentation will be embedded in the page. At
First you may see a 'This document has either been removed or made private by
its owner' message. This is to be expected as SlideShare_ needs a little
time to convert the presentation. Refresh the page after a little while.
Slideshow was removed from SlideShare_
---------------------------------------
When a presentation is removed from SlideShare_ you can simply change the
view back to the default view. However this does not remove the id from
the annotation. To remove the annotation you have to call
`Remove Slideshare Annotation` in the `Actions` menu
or manually append `@@slideshare_removeid.html` to your objects url.
This does *NOT* delete the presentation from SlideShare.
It is not recommended to remove the id if you do not delete the
presentation from SlideShare, because if you change the view back to
`SlideShare View` it will result in another upload of the presentation.
- Code repository: https://github.com/collective/collective.slideshare
- Questions and comments to product-developers@lists.plone.org
- Report bugs at https://github.com/collective/collective.slideshare/issues
.. _SlideShare: http://www.slideshare.net/
Change history
**************
Changelog
=========
0.3 (2013/12/11)
----------------
- add action `Remove Slideshare Annotation`
0.2 (2013/12/11)
----------------
- fix broken Manifest
0.1 (2013/12/04)
----------------
- initial release
- Created recipe with ZopeSkel
[Christian Ledermann]
Contributors
************
Christian Ledermann, Author
Download
********
Metadata
Release files for collective.slideshare 0.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.slideshare-0.3.tar.gz | 15.6 kB | Without provenance | Details for collective.slideshare-0.3.tar.gz |
Security for collective.slideshare 0.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.