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'
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | spp.patch | 415 bytes | diksha@lnwebworks |
| spp.patch | 415 bytes | diksha@lnwebworks |
Issue fork spp-3425321
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
Comment #2
diksha@lnwebworks commentedComment #3
diksha@lnwebworks commentedHi @mustafasayilan
I have created a patch for the above issue
Please review it once
Thank you
Comment #4
diksha@lnwebworks commentedComment #7
norman.lolLet's get this merged and released 🙏🏻
Comment #8
mustafasayilan commentedFixed 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.
Comment #10
mustafasayilan commentedClosing as fixed now that Single Page Protection 1.0.7 has been released.
Comment #11
norman.lolPlease 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.)
Comment #12
mustafasayilan commentedThanks. Credit has been granted to norman.lol in the contribution record.