[Help test new version of stripe module]

Oh, and would it be possible to add the order number as https://docs.stripe.com/metadata?

[Help test new version of stripe module]

On 4/16/2024 at 9:16 AM, datakick said:

Anybody having issues with new version of stripe module so far?

I noticed that under https://dashboard.stripe.com/developers API overview it says: 

You may be using multiple API versions due to your client libraries or plugins.

And I see I'm using both API versions:

2023-10-16
2018-02-28

and not
 
2024-04-10 Latest

Here https://docs.stripe.com/building-plugins#set-api-version it says: 

Your plugin should use the setApiVersion function, which will set the Stripe-Version HTTP header on all requests. Your users will use their own API keys to access Stripe, but this header will be included with every request. We recommend that you use the most recently published version of the API. The current API version and details on our versioning policy can be found in the API reference.

New Stripe users automatically default to the latest version of the API. This header ensures that your connector is pinned to a specific API version, which keeps the occasional backwards-incompatible change from breaking your connector’s functionality.

Users can upgrade their own API version through the Stripe Dashboard. If your connector relies on webhook events, their data format and structure depend on the user’s account API version. You should instruct your users to set the version in their Dashboard to match your plugin.

Caution
API versions can’t be downgraded. You should regularly release new versions of your connector to correctly handle any changes to JSON responses.

[Buchhaltung]

Ich muss noch nicht bilanzieren, will mich aber darauf vorbereiten. Würde alles rund um die Bestellungen schön erfassen für: UmSt-VA, ZM, OSS.

[Buchhaltung]

Danke, vielleicht muss ich mir JTL genauer anschauen. Eigentlich suche ich nur etwas für die Buchhaltung. Zudem: Der Connector wird ja nicht weiterentwickelt. Prestashop allgemein (nicht nur 1.6) wird ja zunehmend weniger von Dienstleistern unterstützt.

Wenn ihr voll im JTL-System seid, wieso dann nicht auch den JTL-Shop?

[Matomo native module - use proxy script feature out of date?]

On 4/15/2024 at 7:11 PM, Adik said:

If you are using Matomo Web Analytics module add code to file: /modules/piwikanalyticsjs/views/templates/hook/jstracking.tpl (line 27)

Do you mean that

(...)
{if $PIWIK_USE_PROXY}
      _paq.push(['setTrackerUrl', u]);
    {else}

becomes 

_paq.push(['disableAlwaysUseSendBeacon']);
{if $PIWIK_USE_PROXY}
      _paq.push(['setTrackerUrl', u]);
    {else}

['native' Mollie module coming?]

Mollie v4.5.3 works!

[Buchhaltung]

Ich hole diesen Thread wieder hoch, vielleicht hat sich was getan in der Zwischenzeit.

[Webservice call resulting in a 401]

The solution was to enable CGIPassAuth On in the .htaccess.

[Webservice call resulting in a 401]

p.s. Are there any changes in the webservice between tb and PS 1.6 that might cause the problem in the third party's implementation?

[Webservice call resulting in a 401]

Thanks. ws_key works in the browser but the third party still isn't working. I'll trouble their support some more and if that doesn't work I'll submit a ticket with you.

[Webservice call resulting in a 401]

I am trying to connect a webservice to domain/api and get a 401 error. 

Using Insomnia, I see this reply:

< HTTP/2 401 
< server: nginx
< date: Tue, 09 Apr 2024 12:53:23 GMT
< content-type: text/html; charset=utf-8
< www-authenticate: Basic realm="Welcome to PrestaShop Webservice, please enter the authentication key as the login. No password required."

Does anybody have an idea would the problem could be?

When I try connecting via the browser https://www.domain.com/api?Authorization=KEY I get the pop up asking for username and password. I enter they key as username and no password and the pop up keeps asking.

[MailQueue module]

20 hours ago, datakick said:

This alone is a great performance improvement. Sending emails can take a lot of time. Because it is synchronous, it blocks response. By offloading this task from customer initiated request to backend thread, you will make your front office much faster. 

I am curious about this. Does that mean that eg all order confirmation emails should typically have a minimal delay? 

[Need testperson for analytics. Any country]

Is this still current?

[Best theme for TB 1.5.1 + ?]

I've used Panda and Community. I'm now with Community. I found Panda to be better in terms of customisability but they stopped updating it, which is why I switched. I believe Panda has been updated in the meantime.

[Non ordered]

I'm getting a couple of these via PayPal. Did your customer use PayPal and are you using our tb native module?

[Wrong taxes for some intra-EU orders using Mollie - can others verify theirs? Also: Where does order_detail_tax get filled from?]

Does nobody else have any problems? 

[Matomo native module - use proxy script feature out of date?]

On 2/27/2024 at 7:23 PM, 30knees said:

I'm unable to get the use proxy script feature to work. While researching, I came across these instructions: https://github.com/matomo-org/tracker-proxy?tab=readme-ov-file

It doesn't look like the files mentioned that should be downloaded are installed via the tb native Matomo module:

Is this because the native module is out of date or is it because of something else?

As this is a tb native module, would you be able to help here, @datakick?

[Help test new version of stripe module]

No problems so far.

I see that the module offers Stripe Checkout: https://docs.stripe.com/payments/checkout I have selected it.

Does the Checkout integration use this feature? https://docs.stripe.com/payments/dashboard-payment-methods Because I cannot get Apple Pay to show, see here: 

 

If Apple and Google Pay don't work, is it a major thing to implement them, perhaps using the dashboard payment method? See: 

 

[Help test new version of stripe module]

Is it ready "enough" to test in a live site? Then I'd be happy to test it.

[Stripe module API integration being deprecated May 15]

Thanks. Please also let us know if you don't update the module so we can then look for another solution. 

[Prestashow modules any good?]

Thanks, Adik.

By the way, do a lot of customers sign up for SMS notifications? Might be a nice thing to offer. I've noticed that customers don't always check their emails.

[Stripe has release new API version not compatible with tb module]

The Stripe module looks good. I prefer to support our tb native / developer modules, though. I'm hoping our native Stripe will be updated (happy to pay for it, too).

[Stripe module API integration being deprecated May 15]

I got this email from Stripe about the tb native Stripe module rearding required changes. Will tb be updating the module and perhaps also adding other payment methods?

We’re reaching out about changes that are required to your Stripe integration. You are currently accepting giropay, Przelewy24, iDEAL payments using the Sources API, a legacy integration that will be deprecated on May 15, 2024. Starting May 15, all non-card source types will be turned off on the Sources API. In order to continue accepting giropay, Przelewy24, iDEAL, you’ll need to upgrade to the Payment Intents API.     How to update your integration     Follow the instructions in our Docs to upgrade to the Payment Intents API, and then add giropay, Przelewy24, iDEAL to your payment flow. You can visit the Stripe Dashboard to view your recent Sources payments and confirm that you have no remaining traffic on Sources once your migration is complete.     If you choose not to update your integration, we recommend that you remove giropay, Przelewy24, iDEAL from your checkout to avoid customer-facing breakages.       Additional benefits of upgrading to the Payment Intents API     Payment Intents is a simpler and unified payments API that supports a single, global integration for all payment methods. On Payment Intents, you can access our optimized payment surfaces like the Payment Element or Checkout, which offer:     Access to more than 100 global payment methods when using the Payment Element Ability to run A/B tests for payment methods to understand their impact across conversion, average order value, cost, and share of wallet, right from the Stripe Dashboard Compatibility with Link for one-click checkout, Radar for fraud protection, and Terminal for in-person payments We’ve provided answers to the most common questions on our Sources migration support page. If you have any further questions, please reach out to our dedicated support team by submitting this contact form.     — The Stripe team

[Editing Specific prices]

The  latest stable version is 1.5.1.

[Matomo native module - use proxy script feature out of date?]

And a follow-up question: Is there any analytical benefit to using the native Matomo module compared to just using the tracking code?

Also, sometimes when I visit the settings page I get this error and then suddenly it's gone again, without any changes being made:

Quote

Unable to connect to the API {"result":"error","message":"Unable to authenticate with the provided token. It is either invalid, expired or is required to be sent as a POST parameter."}