dahousecat → created an issue.
I agree with dawehner, if a view is missing a warning should be logged.
I was also getting undefined index due to these lines in getTokenArgument:
return [
'type' => $match['type'],
'id' => $match['id'],
];
So this patch addresses that issue too.
Huh, actually the exception was thrown via trackUpdateOnEdition, not trackUpdateOnDeletion.
Updated patch to try catch that method too.
dahousecat → created an issue.
dahousecat → created an issue.
Patch 3 would not apply for me due to the "Information added by Drupal.org" bit so I've created a version with that it in.
I think that approach sounds very wise.
The patch I have will solve my use case for now, but once this feature gets added I can delete my patch :)
Example data-disabled-dates attribute:
data-disabled-dates="2024-12-17,2024-12-18,2024-12-19,2024-12-25,2024-12-26"
Sorry, wrong thread. Please ignore me.
dahousecat → created an issue.
My bad, I was still using vs 10.0.0 not 11 simplewebauthn/browser.
Now a load of other things are broken instead but I assume once I fix bugs those I'll have some base64 encoded ids!
dahousecat → created an issue.
Hi, thanks for the swift reply :)
The MR looks good to me, better than my patch as simpler.
Yes, it's a shame this update has so many breaking changes but thanks for the pointer - I'll review the updated documentation.
I did try and create an MR but I'm having some issues with permissions when pushing and it's late so will just attach a patch for now.
dahousecat → created an issue.
The last patch fails on 10.2.7 as LinkItem now provides it's config via annotation.
Could serializePublicKeyCredential() be updated to also accept PublicKeyCredentialCreationOptions?
Just found this: https://github.com/web-auth/webauthn-framework/issues/655
dahousecat → created an issue.
Updated patch to append "action" on end of the input url to the end of the iframe src.
For example if url ends with /interaction this is kept.
Updated regex in patch to support urls such as https://vimeo.com/event/xxxxxxx/embed/interaction
I think creating a new provider for Vimeo Event might be a better solution here as there would be no need to modify the existing Vimeo provider, and certainly not the ProviderPluginBase.
This also comes with the added benefit of allowing users to toggle event functionality.
dahousecat → created an issue.
dahousecat → created an issue.
dahousecat → created an issue. See original summary → .
dahousecat → created an issue.
I've just installed 2.0.2 and I can see commit ff1433c4f36758359cbc6816bd940ffc203d7562 changed the src fields from textfields to textareas (yay), but also added:
'#attributes' => [
'rows' => 1,
],
to all the src fields.
As a result of this I used to be able to see all the rules, as by default the textarea with patch #2 was 5 rows, however now I can only see the first row and have to manually extend all the fields.
This patch fixes that by just removing the rows => 1 bit.
This patch adds a "Allowed empty languages" field to the config form that is only shown if "Remove links if no translation is detected" is ticket.
It then doesn't remove any of the languages selected.
dahousecat → created an issue.
@skaught certainly.
In my case all child pages belong to properties.
Properties can enable and disable languages manually via a field.
Translations may get added for child pages at any point, however until we want to enable a language for a property none of the translations for child pages should show.
This means I need to apply custom logic specific to my application to alter the available links.
Also there are certain languages that we always want to show even if translations don't exist.
This patch alone will not achieve that as link will have already been unset by the time the alter hooks runs - so I think I'll create another issue for this too.
Patch to:
- Add call to moduleHandler->invokeAll for new hook_dropdown_language_alter_links hook.
- Add dropdown_language.api.php to document new hook.
dahousecat → created an issue.
As I was writing this patch I realized that this module only supported protecting one node and I need to protect multiple nodes so I ended up adding that to this patch too.
Sorry it's not in a separate issue but I just need to move really fast on this.
Hope it's useful.
dahousecat → created an issue.
dahousecat → created an issue.
dahousecat → created an issue.
dahousecat → created an issue.
This is the patch I'm using as I know I will only 1 have instance per page.
This patch won't work if you have multiple views on the same page all using this sorting plugin.
dahousecat → created an issue.
dahousecat → created an issue.
dahousecat → created an issue.
Module already has this.
I had a patch to remove it :(
dahousecat → created an issue.
I can confirm using the devel config editor to manually update the plugin to 'entity:delete_action:message' worked for me too.
dahousecat → created an issue.
dahousecat → created an issue.
dahousecat → created an issue.
This should do it:
$profile = Profile::load(123123);
$address1 = $profile->get('address');
$profile->set('field_address2', $address1->first()->getValue());
$profile->save();
Of course if this is multi cardinality replace first() with a loop.
Passing the preferredCountries to intlTelInput only works if countrySearch is turned off.
This is documented on this page under the preferredCountries section.
This is a simple 1 line change in js/webform.element.telephone.js to disable countrySearch when preferred countries are set.
I've attached a patch which is against 6.1.x.
Here is a patch to allow float values in the Slides to show field against the 8.x-2.x version.
dahousecat → created an issue.
dahousecat → created an issue.
dahousecat → created an issue.
dahousecat → created an issue.