sv-wc-payment-gateway-payment-form.min.css.map error

  • Zade

    (@nothin7)


    1 year ago

    Hello,

    Would you be willing to change:

    /*# sourceMappingURL=sv-wc-payment-gateway-payment-form.min.css.map */

    to:

    /* # sourceMappingURL=sv-wc-payment-gateway-payment-form.min.css.map */

    in your sv-wc-payment-gateway-payment-form.min.css file?

    The lack of space after /* triggers a console error with every page load:

    https://www.alternativeradio.org/wp-content/plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/assets/css/frontend/sv-wc-payment-gateway-payment-form.min.css.map Failed to load resource: the server responded with a status of 404 (Not Found)

    I have duplicated this on another site running the latest version (3.0.4).

    Thanks!

    The page I need help with: [log in to see the link]

Viewing 10 replies - 16 through 25 (of 25 total)
1 2
  • lkraav

    (@lkraav)

    5 months, 3 weeks ago

    Yep, things like these really make me wish for an automated WP patch-on-updates solution like https://github.com/cweagans/composer-patches/ but for pure WP diffs.

    eddivalen

    (@eddivalen)

    1 month, 2 weeks ago

    Hey @nothin7 , were you able to generate the source map file to fix this issue? If so, how did you do it?

    Thread Starter Zade

    (@nothin7)

    1 month, 2 weeks ago

    @eddivalen Not sure what you’re talking about. Did somebody say that the authors won’t be simply adding a space to that CSS file and I have to generate a source map file instead?

    @gabrielfuentes Could you please refrain from marking this ticket “Resolved” until you have added a single space to that CSS file?

    eddivalen

    (@eddivalen)

    1 month, 2 weeks ago

    Oh, sorry, I thought you fixed the issue by generating the source map with the space you mentioned. I just wanted to know if you were able to do it.

    As for the developers, it seems this isn’t a priority for them since it’s been a while since the issue was opened.

    Thread Starter Zade

    (@nothin7)

    1 month, 2 weeks ago

    @eddivalen I still don’t understand why there’s any talk of “generating the source map”. The fix is to edit a CSS file that improperly comments out a reference to another file (a .map file), because while:

    /* #this */

    is a comment that’s ignored,

    /*#this */

    isn’t because there is no space between “/*” and “#”. But edits to plugin files are overwritten when the plugin is updated. So the plugin authors need to make this change to the CSS file so the fixed file gets published to the WordPress repository.

    Alex Williams

    (@noahjose)

    1 month, 2 weeks ago

    Yeah, these guys are clueless. I have opened a ticket about this, the last response was quite lengthy and tried to say that it was either because of my theme or because of minification I was running. That’s not the case. The problem is in the embedded asset that they ship which is the file at:
    /plugins/woocommerce-gateway-paypal-powered-by-braintree/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/assets/css/frontend/sv-wc-payment-gateway-payment-form.min.css

    Plugin Support omarfpg (woo-hc)

    (@omarfpg)

    1 month, 2 weeks ago

    Hi Alex @noahjose (and everyone interested in learning more),

    As mentioned in #8350291, the development team is aware of this issue, and we’ve previously flagged your fix for them to update. They’re aware of this forum thread and the number of users asking for this fix, so we’re hopeful that they’ll be able to address this within the next update.

    Thanks!
    -OP

    Jason

    (@galapogos01)

    2 weeks, 6 days ago

    This is still a problem that is tripping my IDS and causing all sorts of havoc. Please fix.

    Thread Starter Zade

    (@nothin7)

    2 weeks, 5 days ago

    @omarfpg As stated above, could you (and your entire team) please refrain from marking this ticket “Resolved” until you have added a single space to that CSS file? This is not resolved, so marking it as such is dishonest, and it makes your customers think you are no longer concerned about this. If you think about it, it would be faster to type one space in one file than to type yet another response in this thread, notifying everybody that is following and wasting even more time. So do the right thing for all of us, including you. Otherwise I guess we can all look for a more supported payment gateway. Thanks 🙂

    anastas10s

    (@anastas10s)

    2 weeks, 5 days ago

    Hi there @nothin7, thanks for reaching back 👋
     
    Just to reiterate, the development team are aware of this issue, and we’ve previously flagged your fix for them to update it.
     
    We’ve noted this forum thread once more to the developers, so that they may understand the scope of the issue that you are experiencing. 

    That said, while the support team and the development team are in constant communication, they are different teams. Also, each one has their procedures in place. As such, this thread was due to be marked as resolved at some point in time, due to inactivity – as the required actions here have already been taken.
     
    We’re hopeful that they’ll be able to address this within the next update.
    I trust this provides clarity. 🙂

Viewing 10 replies - 16 through 25 (of 25 total)
1 2
  • You must be logged in to reply to this topic.