Problem/Motivation

You're required to modify the package name as you've specified 'Package: Custom'. If this module doesn't fall into any specific category, you can designate it as 'Package: Other'

CommentFileSizeAuthor
#2 spp.patch415 bytesdiksha@lnwebworks
spp.patch415 bytesdiksha@lnwebworks

Issue fork spp-3425321

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Diksha@lnwebworks created an issue. See original summary.

diksha@lnwebworks’s picture

StatusFileSize
new415 bytes
diksha@lnwebworks’s picture

Hi @mustafasayilan

I have created a patch for the above issue
Please review it once

Thank you

diksha@lnwebworks’s picture

Status: Active » Needs review

norman.lol made their first commit to this issue’s fork.

norman.lol’s picture

Priority: Minor » Normal
Status: Needs review » Reviewed & tested by the community

Let's get this merged and released 🙏🏻

mustafasayilan’s picture

Status: Reviewed & tested by the community » Fixed

Fixed in Single Page Protection 1.0.7.

The module metadata now uses the standard Other package instead of Custom, and the project page/release metadata has been refreshed for Drupal 9.4, Drupal 10, and Drupal 11.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

mustafasayilan’s picture

Status: Fixed » Closed (fixed)

Closing as fixed now that Single Page Protection 1.0.7 has been released.

norman.lol’s picture

Please consider given credits to us at https://new.drupal.org/contribution-record?source_link=https%3A//www.dru... 🙏🏻

(You need to log in again first, as it's new.drupal.org and not drupal.org domain.)