teknorah β credited arrow β .
Here!
teknorah β credited arrow β .
Present
Here!
Present
tekNorah β credited Arrow β .
There
Here!
froboy β credited Arrow β .
π¨βπ»
Woot!
nicxvan β credited Arrow β .
This seems to work as expected. One thing I noticed is that the description text for the setting requires the entity type to exist. When creating the new entity, the machine name does not yet exist so it is not populated.
I would also like to see someone test upgrading from the existing behavior to ensure that existing URLs for entities are maintained after the upgrade and that disabling URLs on those entities works as expected.
This issue has not had recent activity and is being closed so that focus may be directed at more recent and active issues and versions of ECK. If this issue is still relevant to recent/active versions of ECK, please feel free to return this issue status to "Active" and update the details accordingly.
This issue has not had recent activity and is being closed so that focus may be directed at more recent and active issues and versions of ECK. If this issue is still relevant to recent/active versions of ECK, please feel free to return this issue status to "Active" and update the details accordingly.
Merged and backported to 8.x-1.x branch. Thank you!
Yeah, that makes sense. I asked my coworker to double-check and ensure that they were logged in to Gitlab. They confirmed that they do in fact have the correct permissions while logged in on the Gitlab side. I wonder if there should be a note on the D.o administer maintainers page that clarifies that all (or which if not all) permissions must be granted to get the maintainer role applied in Gitlab.
I brought this up in the Drupal #infrastructure Slack and they were able to fix the permissions on this. 2.x is now the default branch.
@hestenet was able to resolve the immediate issue for me in the ifra Slack, but leaving this issue open for follow-up about what the expected behavior should be and whether it's working as expected.
Yes. We want to get a few outstanding issues/patches merged in then we'll tag 8.x-1.0
The project is now opted-in.
Clarify where and when the settings option can be found
π
I've updated the website to reflect the members in the email group
Attended
Here
I have arrived
tekNorah β credited Arrow β .
@Monster971 did you apply this patch to version 4.0.2 before uploading it to production? Did it apply to 4.0.2 successfully and cause issues? Did it fail to apply? Is further work needed on the code contained in the patch? Please try to be helpful with your comments. Open-source software is built by all of us working together to make things better.
Here!
Here!
volkswagenchick β credited Arrow β .
I vote "no masks" for speakers. Other camps have also had this policy for the accessibility concern.
I vote "masks optional" for attendees. Many are going to refuse to follow a mandate at this point in the timeline. I think we would be putting people at risk by advertising a mandate that many will disregard. If it's optional, people can make their own risk assessments and decide whether or not to attend rather than unexpectedly finding themselves in a room of unmasked individuals. Either the enforcement, or lack thereof, will certainly create a level of hostility. Hostility among those with differing views of the mandate as well as between organizers and those that oppose. I am personally unwilling to force someone to put a mask on or remove a person from camp for failing to do so. I think DrupalCon failed to consider that their mandate may do more harm than good to the notion of community. The very thing that sets Drupal apart. We shouldn't make the same mistake.