🇺🇸United States @el1_1el

#15 was also missing node specific schema i think. updating from #16
+ unpublish_datetime:
+ type: string
+ label: 'Add a default for unpublishing'

I believe the above diff patch is missing and changes never get saved
+ $type->setThirdPartySetting('scheduler', 'unpublish_datetime', $form_state->getValue('scheduler_unpublish_datetime'));

also the issue described in #10 can occur with either NULL or '' so I did the following instead
+ if (!empty($unpublish_default)) {

New patch for 2.21 attached with those changes from #15

created alpha3 with 11 support

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

added manually at https://git.drupalcode.org/project/bulk_update_fields/-/commit/9478ef9b6... due to merge error

Created manually at https://git.drupalcode.org/project/entity_reference_exposed_filters/-/co... due to merge error. Now in dev branch

Merged to dev. Still requires review

el1_1el → created an issue.

#260 applied for me on Drupal 10.3.7 and
#262 did not
thanks @socialnicheguru

There are so many reasons this could happen I'd need more information.

Assuming you are using the default taxonomy view page look at /admin/structure/views/view/taxonomy_term first to check and test.

If you left the default Content Teaser display style in the view, you may want to take a look at the content type display at /admin/structure/types/manage/[content_type_machine_name]/display and see if the Teaser type if enabled is displaying anything.

Its also possible you modified some twig files.

Also verify that the converted nodes are still tagging the term and if not its possible that the term data was not mapped properly in the second step of the convert bundles form. The default is to remove the data if the field name is not the same. When it isnt the same field name you have to select a field to map the data to if one of that type exists.

If the last item is the case, hopefully you have backups or revisions.

Hope that helps

Added to developer role. I havent had much time to maintain obviously :-)

Please correct me if I'm wrong but I'm reasonably certain changing the name of the permission here requires updating existing permissions.

Fixed and released as 2.0.0-alpha2. Thanks everyone!

Symfony\Component\EventDispatcher\EventDispatcherInterface swapped args on the dispatch() method (object, string) instead of (string, object). That causes a fatal error in 10.

Attached patch fixes that and seems to work for me in canvas

Looks like i should get the query before adding the access check. doh! been a long month. new patch attached

el1_1el → created an issue.

If anyone else finds they have custom code relying on this commit as well as the api from the 1.0.x version, or is just having other issues with the 1-2 update, and needs to update to drupal 10, I've attached a patch that restores the 1x version on 2.0 for drupal 10.

Also note that you may need to apply the patch for field_group that removes its implements_alter function from the 3.4 version

el1_1el → created an issue.

I had this issue after an update from core 9.5.8 to 9.5.11 as well. I rerolled the diff patch to remove the empty .DS_Store differ binary.

fixed and released as alpha7

Here's a patch for 10.1.3 - yes it has coding style errors (its not going to be committed w/o tests anyway so ¯\_(ツ)_/¯ ).

Patch is designed to show that running $text through Xss::filterAdmin when the $tokens var is empty is what causes the issue. I may be totally mistaken or misunderstanding something, but the $build runs the xss filter anyway at return Xss::filterAdmin($children);, so I'm not entirely clear why showing raw twig to users when results are empty is necessary but again ¯\_(ツ)_/¯

And moreover - patch is to allow people who have this issue to update to 10.1.x without showing twig syntax to users (ie what my PM/UX manager referred to as "cool gobbly gook")

joseph.olstad → credited el1_1el → .

el1_1el → created an issue.

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

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

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

Hey there,

If you just patch it using the patch in this issue - https://www.drupal.org/project/entity_reference_views_select/issues/3287300 📌 Automated Drupal 10 compatibility fixes Fixed - and tell me its working I'll do another release.

Let me know. Thanks!

a couple of mistakes in hook_update_N from 3 that are fixed here

I ended up needing the flag/boolean for each calendar entity to check if datetime should be validated. this patch adds that change

added to 2.x branch and released as 2.0.0-alpha1

beta3 tagged and released

Sure, why not. beta3 tagged and released

Ive been using this patch successfully on a salary field for about three years now. It doesnt look to me like the gif is calculating on the correct field since the version numbers arent integers. Maybe the id?

Merged and fixed. Thanks everyone!

el1_1el → created an issue.

dont do the redirect when saving event entity from form

add an event_id to the method so we can check against existing events

el1_1el → created an issue.

el1_1el → created an issue.

el1_1el → created an issue.

el1_1el → created an issue.

el1_1el → created an issue.

Sorry for the obnoxiousness of this patch but there should be links between calendars and events so adding to the overall routing issue. Note that patch 5a with change to view will not apply due to upload changing characters ‹‹. patch 5 has other changes

el1_1el → created an issue.

Add edit and delete links to actions on calendar list and link to calendar. add edit and delete links to calendar events also

el1_1el → created an issue.

Add other routes so we can get consistency

missed CalendarForm

el1_1el → created an issue.

el1_1el → created an issue.

el1_1el → created an issue.

Thanks Kelsey!

I merged the first request after a visual review and its telling me "This merge request contains no changes." for the second. Let me know if thats wrong.

I'll leave in dev for community to review.

e

np. im content to just leave it in dev version if people want to try it. ive gotten too far behind on all mod maintenance in general due to other priorities so trying to at least get some dev versions updated for people

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

Hopefully... but I likely won't have time to do it anytime soon. Happy to merge patches or issue forks for those who have time :-)

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

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

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

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

alter title so it comes up in upgrade status link

el1_1el → created an issue.

update for 2.x-dev