This module provides Livestream handler for video embed field module now with this module you can add embed videos from http://livestream.com to your website.
You can use livestream standard web page address for video url, for example
http://original.livestream.com/allthingsfun.

Requirements

Video Embed Field

Video Embed Dailymotion
Video Embed Metacafe
Video Embed Myspace
Video Embed Rutube
Video Embed Youku
Video Embed AOL
Video Embed Instagram
Video Embed Field Overlay

Project link

https://www.drupal.org/sandbox/varghese/2637426

Git instructions

git clone --branch 7.x-1.x https://git.drupal.org/sandbox/varghese/2637426.git

Pareview URL

https://pareview.sh/node/323

Comments

varghese created an issue. See original summary.

visabhishek’s picture

Status: Needs review » Needs work

Git clone command for the sandbox is missing in the issue summary, please add it.

varghese’s picture

Issue summary: View changes
Status: Needs work » Needs review
PA robot’s picture

Issue summary: View changes

Fixed the git clone URL in the issue summary for non-maintainer users.

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

manojapare’s picture

Status: Needs review » Reviewed & tested by the community

Automated Review

No issues found.

Manual Review

Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
Yes: Follows the guidelines for master branch.
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt
Yes: Follows the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements.
Coding style & Drupal API usage
List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:
  1. It is good to put drupal template file in template directory.

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

harika gujjula’s picture

Status: Reviewed & tested by the community » Needs work

Automated Review

[Best practice issues identified by pareview.sh / drupalcs / coder. Please don't copy/paste all of the results unless they are short. If there are a lot, then post a link to the automated review and mention that problems should be addressed.]

Note that perfect adherence to Drupal Coding Standard is NOT a reason to block an application, except for total disregard of them. However, modules should follow them as closely as possible.

Manual Review

Individual user account
[Yes: Follows] the guidelines for individual user accounts.
No duplication
[Yes: Does not cause] module duplication and/or fragmentation.
Master Branch
[Yes: Follows] the guidelines for master branch.
Licensing
[Yes: Follows] the licensing requirements.
3rd party assets/code
[Yes: Follows] the guidelines for 3rd party assets/code.
README.txt/README.md
[No: Does not follow] the guidelines for in-project documentation and/or the README Template. Please correct the links for configuration.
Code long/complex enough for review
[Yes: Follows] the guidelines for project length and complexity.
Secure code
[Yes: Meets the security requirements.]
Coding style & Drupal API usage
[List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:
  1. (*) Major finding, needs work
  2. (+) Release blocker
  3. Just a recommendation
  4. ...]

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

varghese’s picture

Hi harika gujjula

In this read me file may I know which link is not working. This module doesn't have configuration. It comes with video_embed_field.

varghese’s picture

Status: Needs work » Needs review
varghese’s picture

Issue summary: View changes
harika gujjula’s picture

Hey Hi @varghese,
The link i am referring to is "admin/config/media/vet_video_styles" in the README.txt file of video_embed_livestream module. I am able to configure video styles using "admin/config/media/vef/vef_video_styles" .

varghese’s picture

Hi @harika gujjula

That configuration comes with video_embed_field module. Anyway I added in my README.txt

ankush_03’s picture

HI varghese,

please Fix below minor change :

Add t() function on line 16 'title' => 'Live Stream Video',

warped’s picture

Status: Needs review » Postponed (maintainer needs more info)

Thank you for your contribution!

After 2017 March 7 everyone can promote a project to a full project.  A full project has a short project name and a drupal.org/project URL.  It can also have releases (like alpha1 or 1.0).  Edit your sandbox project, and then choose the 'Promote' tab.

https://www.drupal.org/docs/8/understanding-drupal-version-numbers/drupa...
https://www.drupal.org/docs/8/choosing-a-drupal-version/what-do-version-...
https://www.drupal.org/docs/8/understanding-drupal-version-numbers/what-...
https://www.drupal.org/docs/8/choosing-a-drupal-version/release-stable-v...

If you'd like to opt into security coverage, please ensure your module is ready for a full release, and then set this issue back to 'needs review'

Immense apologies for how long it took to get to this review completed.

avpaderno’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)
Issue tags: -New Project Review

I am closing due to lack of replies.

If you are still working on this application, and you need to be able to opt in the security coverage for the projects you maintain, please set the status to Needs review. (See also the project application workflow).