CHANGELOG
0.4.1 (13-12-2017)
Fix on Instagram feed which was no longer available
0.4.0 (16-08-2017)
Dropped support for Wagtail 1.6, 1.7
Added support for Wagtail 1.9, 1.10 and 1.11
0.3.0 (28-10-2016)
Added dimensions when returning the attached Twitter Image
Fixes Facebook support: initially developed on 2.1 while the GraphAPI assumes 2.8.
Added Facebook field configuration
Added Twitter options via default config
0.2.0 (06-10-2016)
Added Facebook support
Added ability to mix all the feeds; just leave feedconfig empty in SocialFeedPage or SocialFeedBlock.
Made all returned data avaiable in FeedItem objects, even if it is not stored explicitly.
0.1.0 (27-09-2016)
Fixed PyPI long_description format error
Fixed value_for_form error in FeedChooserBlock
0.1.dev4 (27-09-2016)
Made looping over multiple result pages more DRY
Improved moderate page title
Fixed AttributeError in FeedChooserBlock.value_for_form
0.1.dev3 (11-09-2016)
Updated license model to BSD
0.1.dev2 (04-09-2016)
Added block type ‘SocialFeedBlock’
Added SocialFeedModerateMenu which live detects configuration changes
Added FeedItem to consolidate the item/post structure
Added search functionality to the Feed objects
Dropped Wagtail 1.5 support in favour of using the IntegerBlock
0.1.dev1 (01-09-2016)
First implementation
Metadata
Release files for wagtailsocialfeed 0.4.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 | Actions |
|---|---|---|---|---|
| wagtailsocialfeed-0.4.1.tar.gz | 18.4 kB | Without provenance | Details for wagtailsocialfeed-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wagtailsocialfeed-0.4.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for wagtailsocialfeed-0.4.1-py2.py3-none-any.whl |
Total release size: 44.8 kB
Security for wagtailsocialfeed 0.4.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.