jekyll-twitter-plugin | Liquid tag plugin for the Jekyll blogging engine

by rob-murray Ruby Version: v2.1.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | jekyll-twitter-plugin Summary

jekyll-twitter-plugin is a Ruby library typically used in Jekyll applications. jekyll-twitter-plugin has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

jekyll-twitter-plugin is a Liquid tag plugin for Jekyll that enables Twitter content to be used in any pages generated by Jekyll. Content is fetched from the Twitter Publish platform. The Publish platform allows Twitter users to curate content for display outside of Twitter. You can display many different types of content with the familiar Twitter styling. We use this API and allow any customisation of the content that is accepted by the Twitter publish platform.

Support

Quality

Security

License

Reuse

Support

jekyll-twitter-plugin has a low active ecosystem.

It has 212 star(s) with 24 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

There are 7 open issues and 25 have been closed. On average issues are closed in 143 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jekyll-twitter-plugin is v2.1.0

Quality

jekyll-twitter-plugin has 0 bugs and 0 code smells.

Security

jekyll-twitter-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jekyll-twitter-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jekyll-twitter-plugin is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jekyll-twitter-plugin releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

jekyll-twitter-plugin saves you 310 person hours of effort in developing the same functionality from scratch.

It has 747 lines of code, 57 functions and 6 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed jekyll-twitter-plugin and discovered the below as its top functions. This is intended to give you an instant insight into jekyll-twitter-plugin implemented functionality, and help decide if they suit your requirements.

Perform API request
Parses the url
Renders HTML tag .
Converts arguments into a hash
Handle HTTP response
Write data to cache
Checks if the user is enabled .
Reads and returns the response .
Outputs the default content of the response .
Raise an invalid parameter

Get all kandi verified functions for this library.

jekyll-twitter-plugin Key Features

No Key Features are available at this moment for jekyll-twitter-plugin.

jekyll-twitter-plugin Examples and Code Snippets

No Code Snippets are available at this moment for jekyll-twitter-plugin.

Community Discussions

Trending Discussions on jekyll-twitter-plugin

Travis-CI: S3 deploy script is not adding new files

Liquid error when trying to embed twitter feed on GitHub Jekyll page using plugin

QUESTION

Travis-CI: S3 deploy script is not adding new files

Asked 2019-Feb-03 at 10:40

My ultimate goal is to be able to schedule posts on my Jekyll blog. I am using Travis-CI to deploy the contents of /_site/ to an S3 bucket whenever I commit to my master branch in Github.

The Travis-CI flow works as expected but for the fact that new pages that are not built and addd to the /_site/ directory unless I build my site locally and push the new /_site/ folder directly to master. The posts are present in /_posts/ but do not get build and added to /_site/ automatically as they should when the site is rebuilt daily.

My travis.yml file is below.

...

ANSWER

Answered 2017-Mar-23 at 18:10

I figured this out: the Travis-CI deploy gem doesn't include a build step. It just pushes the contents of the repo to S3. I updated my build script to push as part of the build and validation step.

Source https://stackoverflow.com/questions/42918026

QUESTION

Liquid error when trying to embed twitter feed on GitHub Jekyll page using plugin

Asked 2017-Mar-22 at 20:42

I am trying to embed my twitter timeline on my Jekyll Blog hosted on Github.

This is the plugin I am trying to install: https://github.com/rob-murray/jekyll-twitter-plugin

These are instructions I am using to install plugins in general: https://jekyllrb.com/docs/plugins/

The site above includes the warning:

Plugins on GitHub Pages GitHub Pages is powered by Jekyll. However, all Pages sites are generated using the --safe option to disable custom plugins for security reasons. Unfortunately, this means your plugins won’t work if you’re deploying to GitHub Pages.

You can still use GitHub Pages to publish your site, but you’ll need to convert the site locally and push the generated static files to your GitHub repository instead of the Jekyll source files."

Does this mean what I am trying to do is impossible, without building the site statically, since I am using Github pages? I am lead to believe not, because I encounter an error even when serving the site locally on my laptop.

However, I get the following error when I place the example {% twitter https://twitter.com/jekyllrb maxwidth=500 limit=5 %} into my index.md file. When I do jekyll serve --watch locally, it gives the error:

...

ANSWER

Answered 2017-Mar-22 at 20:42

That plugin is not supported by Github Pages, so it won't work there. The only possibility to use it is to build your site locally before pushing your site to Github Pages.

If you want to install it locally anyway, after adding the gem to Gemfile, Install the gems specified in that Gemfile:

Source https://stackoverflow.com/questions/42962107

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jekyll-twitter-plugin

As mentioned by Jekyll's documentation you have two options; manually import the source file, or require the plugin as a gem. Install the gem, add it to your Gemfile;. Add the jekyll-twitter-plugin to your site _config.yml file for Jekyll to import the plugin as a gem. Note: this is deprecated and support will be removed in a later version. Just download the source file into your _plugins directory, e.g. To use the plugin, in your source content use the tag twitter and then pass additional options to the plugin. These are passed to the API. In addition to passing the Twitter URL directly to the plugin, you can also use Front Matter to store URLs as page variables. This allows you to re-use view configuration or partials by keeping the Twitter URL(s) separate to page content.

Support

The Twitter URLs that are supported depend on Twitter. We pass the url and all parameters to the API - check Twitter Publish platform for availability. Here is documentation for some common types:.

Find more information at: