==========================
This product add's new tab to the topic content type called `embed`, and
publish topic's items similar to **twitter** widget.
Embed
-----
This is practically a simple form that allows user to configure a web widget.
The code can be found in the `textarea` in the same view. An example code
looks like that:
```html
<script>
(function() {
var s = document.createElement('script');
s.src = 'http://nohost/plone/events/embed.js';
s.async = true;
window.topic_options = (window.topic_options || []).concat([ {
element_id: 'embeded_id',
elements_length: 5, //how many elements to show
embed_css: true, //embed rt.topicembed css styles
new_window: true //open links in new window
}]);
document.body.appendChild(s);
}());
</script>
```
This code can be later embeded on the external site, the same as **twitter** widget.
Output
------
The template for rendering the output is registered by this ZCML slug:
```xml
<browser:page
name="json"
for="Products.ATContentTypes.interfaces.topic.IATTopic"
layer="..interfaces.IBrowserLayer"
class=".embed.EmbedJSON"
permission="zope2.View"
/>
```
and it's called `items_macro.pt`. It generates an HTML output similar to:
```html
<div>
<p>
<a href="http://nohost/plone/events/event1">Event 1 title</a>
</p>
<div>Short event description</div>
<img src="http://nohost/plone/events/event1/image_mini" title="Event 1 image">
</div>
<div>
<p>
<a href="http://nohost/plone/events/event2">Event 2 title</a>
</p>
<div>Other event description</div>
<img src="http://nohost/plone/events/event2/image_mini" title="Event 2 image">
</div>
```
Changelog
=========
1.3 (2013-12-20)
----------------
- Add it translations [lucabel].
1.2 (2013-03-18)
----------------
- add image size selection [amleczko]
- add example CSS [massimo]
- add translations [amleczko]
1.1.1 (2013-03-05)
------------------
- Fix JSON [amleczko]
1.0 (2013-03-05)
----------------
- Initial release
Metadata
Release files for rt.topicembed 1.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 |
|---|---|---|---|---|
| rt.topicembed-1.3.zip | 17.6 kB | Without provenance | Details for rt.topicembed-1.3.zip |
Release files / rt.topicembed-1.3.zip
| Download URL | rt.topicembed-1.3.zip |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3200eb903059290866854c35b626e8d3bd9271bb04a0a0272c8d710b52a2d35d
|
|
BLAKE2b-256 checksum How to use checksums |
c2884fc8283a073504035d0f1543399288703b784dd708ae3d30b5baf3dca802
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rt.topicembed 1.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.