This module is used to collect year part of date in any field. It provides a custom field type Year Only in the field UI.

With the help of this module one can add field where he/she wants to get year only instead of complete date.

Project Page: https://www.drupal.org/project/yearonly

git clone --branch 8.x-1.x https://git.drupal.org/project/yearonly.git
cd yearonly

Installation:

Installation of Year Only module is similar to other drupal modules. To install Year Only module please follow the below steps:

  1. Download the Year Only module and extract into the /modules directory.
  2. Enable the module.
  3. Go to manage fields in any entity and add new field of type Year Only.

Manual reviews of other projects

  1. https://www.drupal.org/node/2870685#comment-12072303
  2. https://www.drupal.org/node/2840555#comment-12072347
  3. https://www.drupal.org/node/2871158#comment-12072373
  4. https://www.drupal.org/node/2865054#comment-12072407

Comments

sharma.amitt16 created an issue. See original summary.

sharma.amitt16’s picture

sharma.amitt16 commented
Issue summary: View changes
sharma.amitt16’s picture

sharma.amitt16 commented
Issue summary: View changes
PA robot’s picture

PA robot commented
Multiple Applications
It appears that there have been multiple project applications opened under your username:

Project 1: https://www.drupal.org/node/2891185

Project 2: https://www.drupal.org/node/2874772

As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).

If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.

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

PA robot’s picture

PA robot commented
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.

sharma.amitt16’s picture

sharma.amitt16 commented
Status: Needs review » Closed (duplicate)
sharma.amitt16’s picture

sharma.amitt16 commented
Status: Closed (duplicate) » Needs review
munish.kumar’s picture

munish.kumar commented

Hi @sharma.amitt16,

I've reviewed your module and it worked well for me. great work! Pareview.sh doesn't report any errors. This module also useful for drupal community so +1 from me.

sharma.amitt16’s picture

sharma.amitt16 commented
Issue summary: View changes
Issue tags: +PAreview: review bonus
sharma.amitt16’s picture

sharma.amitt16 commented
dhayanandan_k’s picture

dhayanandan_k commented

Hi @sharma,

I have reviewed your module. It has no issues and the module is working.

Automated Review

No issues found by pareview.sh (https://pareview.sh/node/2574)

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
[Yes: Follows] the guidelines for in-project documentation and/or the README Template.
Need to add Requirements and Configuration section
Code long/complex enough for review
[Yes: Follows] the guidelines for project length and complexity.
Secure code
[Yes: Meets the security requirements.]

Thanks,

Dhaya

sharma.amitt16’s picture

sharma.amitt16 commented

Thanks @dhayanandan_k for review.

sharma.amitt16’s picture

sharma.amitt16 commented

Any Update for +RTBC ?

sharma.amitt16’s picture

sharma.amitt16 commented
Priority: Normal » Major
sharma.amitt16’s picture

sharma.amitt16 commented
Priority: Major » Critical

I's over two months and no issue found but still no update about RTBC (Security Certified). Would anyone please update if I am doing anything wrong.

pranavgupta’s picture

pranavgupta commented
Status: Needs review » Needs work

Hi @sharma.amitt16,

The module seems to work perfectly fine. Good work !! on the module.
but there seems to be some problem after using the module and then uninstalling the module from drush, Please check.

sharma.amitt16’s picture

sharma.amitt16 commented
Status: Needs work » Needs review

Thanks @pranavgupta for reviewing the module.

There is no error on install/uninstall of the module using drush.

I have tested the scenario you described. If have you have created a field using this module, then there is a dependency of field on the module. In this case you can't uninstall the module, not even from UI. In this case, you need to delete the field first and then try to uninstall the module. Hope you will get success.

Please find the output I got after uninstall command using drush

The following extensions will be uninstalled: yearonly
Do you really want to continue? (y/n): y
yearonly was successfully uninstalled. [ok]

Please check in your case.

Thanks

sharma.amitt16’s picture

sharma.amitt16 commented

Hi,

Anyone please update for RTBC?

pranavgupta’s picture

pranavgupta commented
Status: Needs review » Reviewed & tested by the community

Hi sharma.amitt16,
looks good to me hence moving it to "RTBC".

sharma.amitt16’s picture

sharma.amitt16 commented

Thanks Pranav.

Anonymous’s picture

Anonymous (not verified) commented

I need such a module but Years Only isn't safe. When will it be safe?

sharma.amitt16’s picture

sharma.amitt16 commented

Thanks @20drei. Would you please provide security issues.

Anonymous’s picture

Anonymous (not verified) commented

On the project's page, they say:

This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.

What does it mean? It sounds like the module isn't safe. On the other hand, they say:

Reviewed & tested by the community

This is confusing. Can I help in any way? Please see: Security advisory process and permissions policy

sharma.amitt16’s picture

sharma.amitt16 commented

@20drei, This module is not covered under security advisory that's why I created an application here for the same. On this thread community is reviewing the module. If they are satisfied with module, they convert the status to RTBC and after that any user with special role can give permission to module author to choose "Security opt in".

Please check security advisory policy for the same.

Anonymous’s picture

Anonymous (not verified) commented

I will review and test it as well but I am not a PHP programmer. Hope the module will be covered under security advisory soon.

Thanks @sharma.amitt16

ayalon’s picture

ayalon commented

Automated Review

https://pareview.sh/node/2574

No warnings found.

Manual Review

Year Only is a small plugin that is using an int field instead of the date field to save the year. It implements a
FieldType, FieldFormatter and a FieldWidget following the Drupal 8 best practices.

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
[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
[No: List of security issues identified.]

sharma.amitt16’s picture

sharma.amitt16 commented

Thanks ayalon for review.

In your review you have posted

Secure code
[No: List of security issues identified.]

Would you please provide security issues list.

sharma.amitt16’s picture

sharma.amitt16 commented

Any update on security opt-in for the module.

visabhishek’s picture

visabhishek commented
Status: Reviewed & tested by the community » Fixed

Thanks for your contribution, Amit Sharma !

I updated your account so you can opt into security advisory coverage now.

Here are some recommended readings to help with excellent maintainership:

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

Thanks to the dedicated reviewer(s) as well.

visabhishek’s picture

visabhishek commented

Assigning Credits.

sharma.amitt16’s picture

sharma.amitt16 commented

Thanks @visabhishek for updating the account.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.