As luck would have it, my VPS where the website is hosted got a system failure before that particular article was backed up.
Nevertheless, I recreated it and I updated the link above.
I found myself getting blocked by this error on a Drupal 9 to 10 upgrade and I was able to fix it. I documented the process here https://condurachi.ro/unknown-timediff-filter-twigexpressionparser-getfi....
Sorry, I'm not sure I understand.
All I did was add a checkbox in the View, which disables the double click action (screenshot attached).
That's what my client needed. Not sure what drop down box you mean.
Patch attached.
Never mind. I was doing a ksort() on hook_form_alter() to find the form keys easier. Apparently that doesn't sit well with Form API.
All fixed.
I've set this to Critical because the module is unusable.
The patch in #55 fixed the same error I had on a 10.1.7 installation.
Works fine and fixes the error on Drupal 10.1.5.
Yes, please commit.
I can confirm the cause was empty aliases. In my case, empty taxonomy aliases.
Obviously, the patch I uploaded is useless at this point.
I can confirm the patch works fine.
Updated patch.
Patch attached.
The existing code takes care of full URL already. Check out src/UnsplashFetcher.php line 54.
I enabled pathauto and created a node without alias on a clean Drupal 10.1.1 site but I couldn't get the error.
What were your steps?
andreic → created an issue.
I've just tested with a clean install of 10.1.1 and when accessing admin/structure/taxonomy/manage/tags/overview it does not display the error.
It must be something with that particular client.
If I go to admin/structure/taxonomy/manage/tags/overview I also get it:
Deprecated function: str_starts_with(): Passing null to parameter #1 ($haystack) of type string is deprecated in Drupal\path_alias\PathProcessor\AliasPathProcessor->processOutbound() (line 54 of core/modules/path_alias/src/PathProcessor/AliasPathProcessor.php).
This is weird, I'm getting the error when accessing paths like taxonomy/term/327.
I've upgraded to 10.1.1 and now I get:
Deprecated function: str_starts_with(): Passing null to parameter #1 ($haystack) of type string is deprecated in Drupal\path_alias\PathProcessor\AliasPathProcessor->processOutbound() (line 54 of core/modules/path_alias/src/PathProcessor/AliasPathProcessor.php).
Patch file attached. Must get applied after https://www.drupal.org/project/media_entity_unsplash/issues/3373586 ✨ Allow adding by photo URL Needs work .
andreic → created an issue.
After applying the patch to the latest module version with composer.json, I fixed all the remaining errors when it gets applied and finally it's ready to use.
Ok, the patch is all good to go.
Typos fixed, patch updated.
Patch added.
Title corrected.
Another error fix, updated patch.
Patch was incomplete, updated it.
I've updated the patch to include only the State API changes.
Thanks, I will try to debug that part.
Attaching patch
andreic → created an issue.
It works, that fixed it!
Patch works great!
1. Must be something I overlooked.
2. Well, first, the keys should not be in config/install/media.type.unsplash.yml file because that goes to Config. Then, some helper functions (e.g. unsplashGetKey and others) and then at the end, changes for the unsplash library because the library does not use access_key or secret_key, it uses applicationId, secret and utmSource as required keys when making call.
3. The links you gave offer the same solution: State API, which is what I'm doing, too.
Updated patch for all exceptions with appropriate message/hint.
Updated patch.
Typo fixed.
Patch file.
Patch file.
Patch file
andreic → created an issue.
Actually, you were perfectly right: "The client column in the db is NULL for all of them.".
I've encountered this myself and after a few hours of debugging, the problem was in the src/Normalizer/RefreshTokenEntityNormalizer.php file. It didn't include the client ID.
I've attached a patch.
#3 works for me. thanks.