🇺🇦Ukraine @knyshuk.vova

It works for me as well.

Runs smoothly on D11.1.5 for me

Merge request !27
I was able to configure the module and send an email using version 2.0.0 of the module.

knyshuk.vova → changed the visibility of the branch 3451175-automated-drupal-11 to hidden.

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

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

anybody, It's a good idea.

I also suggest resolving the issue with complex IDs {entityType}:{id} and the template first. This will prevent unnecessary work with MR rerolling. We have few issues with changes to the same conflicting files. Like this one 3196119

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

#41 accidentally deletes the flag-count-text.html.twig template, that's causing an error.

amanire, I have also noticed an issue where the patch (from MR > Download > Patches) from the merge request is not applying, but the diff (from MR > Download > Plain diff) applies successfully.

As for now, the MR 46 diff is applied correctly.

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

Diff from previous patch:

• replaced if with nullish coalescing operator
• added some comments.

The reason why we have this issue:

4.0.0-alpha5
$(this).val(e.effect.value);
val(undefined) in jQuery sets the value to an empty string (""), not string "undefined".

4.0.0-alpha6
this.value = e.effect.value;
e.effect.value is undefined, the value property is set to string "undefined"

The patches in this issue modify same line as another issue: 3421076.
It mentions that "a module can't rely on the route in hook_css_alter".
I prefer to use that solution instead of this one.

Probably this issue can be closed as duplicate.

The patches above indeed allow replication only for selected content types. However, they also break replication for other entity types (the route access for /replicate). This is because the logic for nodes is applied to other entity types as well (but should not). Patch #8 had the correct logic regarding this, but the newest patches - not. We should apply the node logic only if there is a node object.

The patch is from the current merge request #10, no changes, just to keep it here.

#20 fixes the issue for me, but it can't be applied for 8.x-4.0-beta6.

The patch can be used as a temporary solution while a better approach is not implemented yet.

I updated the #20 patch to be compatible with 8.x-4.0-beta6 and changed the variable names.

knyshuk.vova → created an issue.

I confirm that "_type" handling here in contrib is needed. So we have to handle it like '{' . $entity_type->id() . '_type}'

Its due to another examples:
"add-form" = "/group/add/{group_type}",
"add-form" = "/feed/add/{feeds_feed_type}",
"add-form" = "/store/add/{commerce_store_type}",
"add-form" = "/product/add/{commerce_product_type}",

About logic related to "_blank", I propose creating another issue that will allow configuring where to open the link.

Attaching a patch against 4.3.4.

Thanks for bringing it up. Would really appreciate a patch if you have time to work on this feature.

knyshuk.vova → created an issue.

You can use this module instead https://www.drupal.org/project/voice_recorder →
It allows the recording button replacing, check the template. It also provides more features.

You can use this module instead https://www.drupal.org/project/voice_recorder →

The merge request has an error, it should not remove logic related to 'aria-describedby', just change assignment of 'accept'

The issue still exists in drupal 10.
$element['upload']['#attached']['drupalSettings']['file']['elements']['#' . $id] = $extension_list;
Here we actually have selectors for div and input tags.

knyshuk.vova → created an issue.

@jeffam, (or others who will continue the issue),
Please check the method RestClient::getVersions(), it is also in use in setting form. Maybe we can just reuse it to reduce the code duplication in your merge request.

I had the same error. Thanks for the patch. +1 RTBC

Marked the interval fields as required.

The attached patch adds timestamp value push support by converting timestamp into supported by Salesforce format.

The code originally from the last patch in old discussion branch https://www.drupal.org/project/salesforce/issues/3122412#comment-14116705 🐛 Mapped date fields are not properly syncing data. Closed: outdated ,
additionally fixed bugs
- 'date' salesforce type converting
- possibly missing requested drupal field definition (due to 'drupal_field_value' may have not a drupal field name value)

Tests coverage still needed.

Confirm that solution from #5resolves the issue.

I agree that the example should be added to SalesforceExampleSubscriber

added patch according to above comment

@audiomason, nice job for finding such an issue. I have some adjustments for your patch.

It's better to use a setter method setEntityValue(), which indicates that change is intentional and controlled, rather than getting the reference of the value and change it directly.

  public function __construct(&$value, SalesforceMappingFieldPluginInterface $fieldPlugin, MappedObjectInterface $mappedObject) {
    $this->entityValue = &$value;
    // rest of code...
  }

  /**
   * Setter for entity value.
   *
   * @param mixed $value
   *   The value to be assigned.
   */
  public function setEntityValue($value) {
    $this->entityValue = $value;
  }

knyshuk.vova → created an issue.