🇺🇸United States @bluegeek9

@kishor kumar v ,

I will restore Group v1 support, and make a new release.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

This issue seems to be the same as 🐛 "An anonymous user must be identified by session ID" crash on Drupal 10 Active .

Which version of Groups are you using? We recently dropped support for Group 8.x-1.x.

I tried using AccessResult::forbidden(), but other checks are not performed if a user has 'bypass node access'.

I think we can use hook_link_alter to remove the 'Clone' task.

bluegeek9 → made their first commit to this issue’s fork.

I added a permission 'clone _any content'. There is no equivalent 'create any content' permission. I want feedback from the community before completing the MR.

bluegeek9 → made their first commit to this issue’s fork.

Back to site link points to the last non-administrative page the user visited within the same browser tab.

Visitors is not an admin URL, it starts with /visitiors/.

I think you need to exclude the webform field to clone the node correctly.

bluegeek9 → made their first commit to this issue’s fork.

Quick Clone Node uses hook_node_access. This issue is outdated.

Does the user have the permission to create the content type?

#2979426: Permissions not respected →

If a user has the bypass node access permission, they are able to clone nodes.

The config require_revision_log_message.adminsettings is already deleted when the module is uninstalled, no need to do it in hook_uninstall.

bluegeek9 → changed the visibility of the branch 2.0.x to hidden.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch project-update-bot-only to hidden.

Is this feature needed? Would the "Exclusion list" options in Quick Node Clone's settings work, to exclude cloning the simplenews_issue field?

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

I think this might have been fixed, 🐛 Fatal error if content type who has clone permission is deleted Active .

Let us know if it is still an issue.

I think this might be a duplicate of 📌 deprecated class constant INITIAL_VALUES of class Drupal\address\Event\AddressEvents: Active .

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → created an issue.

The tests are failing with Group v1.

1) Drupal\Tests\quick_node_clone\Functional\QuickNodeCloneGroupIntegrationTest::testNodeClone
Exception: Deprecated function: Use of "static" in callables is deprecated
Drupal\group\Entity\GroupRole::postLoad()() (Line: 315)

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 3398866-use-route-access to hidden.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

bluegeek9 → changed the visibility of the branch 2979426-just-the-bug to hidden.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

bluegeek9 → made their first commit to this issue’s fork.

I can not reproduce the issue. This issue is outdated.

I changed the clone_status field to a set of radios.

• Default
• Original
• Published
• Unpublished

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 8.x-3.x to hidden.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 3200854-d7-coding-std-relation-ui to hidden.

bluegeek9 → changed the visibility of the branch 3200854-coding-standards-- to hidden.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 8.x-2.x to hidden.

I am seeking feedback on this feature before publishing a new release.

I think this is a duplicate of 🐛 Prevent infinite loop when sending messages with queue RTBC

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

bluegeek9 → changed the visibility of the branch 3483664-automated-drupal-11 to hidden.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 8.x-1.x to hidden.

Actually doing this would cause subject to go twice through strip_tags and html_entity_decode...

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → created an issue.

1. Workflow: CiviCRM has a similair status. I think this will be needed eventually. I imagine it would depend on the workflow module.
2. Do we want to have promote and sticky? Have them would like Nodes?
3. Duration field: I looked at the Duration field. I do not know if it will work. It does not support Drupal 11. Memberships of less than a day will be harder to implement.
4. Fixed or Rollover: Let us look at a monthly membership. Someone joins on the 15th of the month. With Fixed, the membership expires at the end of the month. With rollover, the membership expires on the 15th of next month.
5. CRM Membership Log: The CRM Membership entity corresponds to a Contact and a membership type. Each time a membership is created or renewed a Membership Log is created. Handling payments is out of scope now. It is like a payment record. E.g. Contact A renewed monthly membership for 6 months.
6. Multi-Person Membership: Not sure. Each Membership type defines which contact type can 'join'. This would allow households and organizations to join. How does that filter down, to the individual; I have no idea yet. My first thought was an unlimited entity reference field, with an item for each individual. That would work for households, but organizations will have issues; entity references do not scale. If memberships can have 'parent' memberships, that could also work.
7. Note sure. If we used entity references, each membership type could have a different limit.

@drupalbubb,

You need to add a relationship to your view, Visitor Counters. Three fields can now be added: Most recent visit, Total views, and Views today.

bluegeek9 → changed the visibility of the branch 8.x-2.x to hidden.

bluegeek9 → made their first commit to this issue’s fork.

bluegeek9 → changed the visibility of the branch 3429986-automated-drupal-11 to hidden.

I made Merge requests for bother branches: 8.x-2.x, 3.0.x