🇨🇦Canada @maursilveira

I've created a merge request with the deprecation fix.

maursilveira → created an issue.

I've just created a merge request with the change, which is quite trivial indeed.

maursilveira → created an issue.

I've just created a merge request with the adjustment.

maursilveira → created an issue.

I've created a merge request with the adjustment.

I've created a merge request with the fix, which is in fact quite trivial.

maursilveira → created an issue.

maursilveira → created an issue.

I've just created a merge request for both dev versions 2.0.x and 3.0.x with the change.

maursilveira → created an issue.

I'm sorry, I've just noticed this has been fixed in the dev branch. Closing this task.

Apologies for all the noise.

maursilveira → created an issue.

Ok, different browsers display different warning messages in the console, but after doing multiple tests, this is the message that I get only and in all situations when the error happens:

Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://js.stripe.com') does not match the recipient window's origin ('https://my-site-url-here').

Researching by this type of error returns many results, and apparently this may happen when the postMessage() function is called before the actual element in the DOM has finished loading, but I'm not sure that is the case here. This message is coming from the following function in https://js.stripe.com/v3/

function(e) {
    var t, n = e.targetOrigin, r = e.type, o = n;
    switch (r) {
    case "sibling":
        t = (0,
        l.Hb)(e.targetFrameId);
        break;
    case "child":
        t = window.frames[e.targetFrameId];
        break;
    case "parent":
        o = o || "*",
        t = window.parent;
        break;
    default:
        (0,
        s.Rz)(r)
    }
    if (o = o || u.jQ,
    t && "function" == typeof t.postMessage) {
        var i = e.message.delegate ? {
            targetOrigin: o,
            delegate: e.message.delegate
        } : o;
        t.postMessage(JSON.stringify((0,  // <= Error happens here
        c.Z)((0,
        c.Z)({}, e), {}, {
            __stripeJsV3: !0
        })), i)
    }
}

I'm not very familiar with how the checkout pane is built or how the Stripe library is called and executed, therefore it's been hard for me to find where a fix should go.

Any thoughts?

Hello,

Doing some more tests today, I was able to get the following error in the browser's console:

Uncaught IntegrationError: payment Element didn't mount normally.
    at e._handleMessage (v3/:1:88665)
    at e._handleMessage (v3/:1:101570)
    at v3/:1:87423

This is coming called from the following function:

this._setupPostMessage = function() {
    r._listenerRegistry.addEventListener(window, "message", (function(e) {
        var t = e.data
          , n = e.origin
          , o = e.source
          , a = (0,
        l.$G)(t);
        a && ((0,
        T.uW)(u.jQ, n) ? r._handleMessage(a, o) : (0,
        x.Z)(n))
    }
    ))
}

Which ends up in this case statement:

case "stripe-frame-error":
  throw new I.No(a.payload.message);

Any help is greatly appreciated!

maursilveira → created an issue.

Thank you @apaderno and @vishal.kadam for all your support with this. I really appreciate it.

The recommended changes have been merged into the main branch of the repository.

Marking this as fixed.

@vishal.kadam Thank you for the update, I wasn't familiar with the review process.

The changes have been committed into the main branch of the project:
https://git.drupalcode.org/project/field_label_override

@apaderno I applied the adjustments you recommended. They haven't been merged to the main branch yet, nor I have created a new release of the module. These adjustments are in the following merge request:

https://git.drupalcode.org/project/field_label_override/-/merge_requests...

Could you please review it and confirm the adjustments comply to the Drupal coding standards, and they should suffice? Then I'll merge the changes and create a new release of the module, which we can hopefully mark as covered by Drupal's security advisory policy.

Thank you.

maursilveira → created an issue.

@apaderno I really appreciate you taking this module into consideration, and even more the extensive review you reported in #7.

I'll carefully review your comments, and apply the necessary adjustments to the module. I'll keep you posted in this thread when I would expect you to review the adjusted code.

Once again, thank you!

Hello @vishal.kadam, thank you for your quick reply.

I agree, the module is quite simple/small, but mainly because the purpose of it it's pretty simple too: allowing administrators to configure different labels for fields per entity view mode.

I have some other contributions, which you can see on my Drupal.org profile, but really the vast majority of my code work as a Drupal developer and solutions lead is client work, which I acknowledge you don't have access to view. I can send the link of those sites, if that works, but I'm not sure if this is of any help.

I'd be honoured if I was granted the ability of opting projects into security advisory coverage, but honestly, that's not my main purpose at this moment, and I'm fine with opening a new issue like this in the future for any new module I eventually contribute. All I'm looking for at this moment is having this project Field Label Override covered.

Please let me know what we can do to achieve this.

Thank you very much.

maursilveira → created an issue.

@shwetaDevkate Thank you for creating the MR. The code overall works as expected. I made an adjustment to ensure the attribute colspan is only added to fields that do not have the label overridden when at least one field does.

I'm marking this issue as fixed, and I'll be creating a new release of the module soon.

Thank you.

I tested the patch #2 against the version 2.10.0 of the module, and it does fix the issue.

Thank you @thatguy!

@shwetaDevkate Thank you for looking into this issue and submitting a patch. This is much appreciated!

Following Drupal.org guidelines, we should prioritize merge requests over patch files, now considered deprecated. Therefore, I'll ask you to create a merge request with your suggested fix.

Thank you.

Release 1.0.0-alpha2 → has been created comprehending this fix.

Release 1.0.0-alpha2 → has been created comprehending this fix.

I noticed the same typo was present in the README.md file, which was also fixed.

maursilveira → created an issue.

maursilveira → created an issue.

This has been merged.

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

@mark_fullmer Thank you for your response. I wasn't sure if I was missing something or it was indeed a feature not implemented.

I'm changing the issue category to "Feature request", so we can look into implementing it, if possible.

maursilveira → created an issue.

Hello,

I second @Nicolas Bouteille on what was said in #3 about the risks and efforts involved in upgrading stripe/stripe-php from the currently used version 7.x to the latest one (13.x). At the same time, I am not an expert in either Commerce Stripe module or Stripe itself. However, perhaps if we were able to summarize what needs to be covered, we could split efforts and test the module against the latest library version. I volunteer to help out with this work, but would certainly need guidance from someone with experience in the module.

One example of issue I'm having now with the library's old version is that I'd like to search customers by their email addresses in a custom functionality, using Customer::search(), but I get the error message:

Search is not supported on api version 2013-02-13. Update your API version, or set the API Version of this request to 2020-08-27 or greater.

Restating what @Nicolas Bouteille said in the description, we are probably missing out sticking with an old version, taking the risk of having to run into an urgent upgrade if Stripe eventually stops supporting other functionalities, similar to the above.

maursilveira → created an issue.

@jonathanshaw Thank you for your response, but I've just figured out the cause of the issue: I am using Stripe Payment Element, and the patch #3 only adds the name item to the class Stripe.

I created a new patch that adds the name for both payment gateways. Moving the issue back to "Needs review" status.

Please let me know if you have any questions, concerns or comments.

Thank you.

@LeDucDuBleuet

Thank you for the patch, but I'm a bit confused here, and not seeing the expected result.

I applied the patch, and have Realname → configured in my site with [user:field_first_name] [user:field_last_name] as pattern. When I call ::getDisplayName() elsewhere I get the correct user name format. However, when I complete a purchase using Commerce Stripe for a new customer, it gets created in Stripe with the name empty. All I see is the email address and the description "Customer for ".

Am I missing something here? Do I need any other configuration for getting the user display name to have this working?

Thank you.

I tested the patch from #9 and it works as expected. It applies cleanly and fixes the issue with the aggregated CSS.

Thank you @jrglasgow!

Patch from #18 works for me and fixes the error.

Thank you.

I ran into this same issue, and the patch #14 fixes it.

I ran into the same issue in a Drupal 10 site, when testing this module for the first time (version 4.0.0).

Changing the version to 4.0.0, since version 8.x-3.x-dev works with Drupal 8 and 9, which are not supported anymore.

Leaving this note here, in case other have the same issue.

I had the same error when trying to execute database updates (via drush updb) after upgrading from 8.x-3.11 to 4.1.x. I noticed that I had a sitemap regeneration in progress in the Sitemap status. After simply clicking on "Rebuild queue", I was able to execute the database updates with no errors.

Hello,

I tested the patch #242 and it works as expected.

Thank you!