Jump to content
thirty bees forum

30knees

Gold member
  • Posts

    1,341
  • Joined

  • Last visited

  • Days Won

    29

Posts posted by 30knees

  1. I've noticed a couple of times now that customers from Spain mistakenly select Germany as the country (Germany is where the shop is based). This impacts the shipping price, the rate, and requires a manual correction of the address.

    I'm hoping this isn't some shipping fee scam but just a mistake by the customer. Is there any way to prevent this mismatch?

  2. I have a delay of 0, which means that the delay will depend on the cron job. Is this correct? Because at the moment the default queue isn't delaying anything, as far as I can tell.

    On 4/6/2024 at 9:09 AM, datakick said:

    yes, the delay depends on cron frequency. If you run it every minute, the longest delay should be a minute.

     

  3. 13 minutes ago, datakick said:

    At the time of payment order does not exists yet. We could store cart id there, though.

    I see ... I think for my purposes (payment reconcillation) cart id isn't helpful at the moment, but maybe for someone else? 

  4. 10 minutes ago, datakick said:

    Latest module of stripe uses api 2023-10-16 -- if you use stripe only with thirty bees, you should set this version as default in your stripe dashboard

    Found it, thank you. I was only able to upgrade to the latest. I couldn't select the version in the dashboard. I'm on the latest and did a test purchase, it worked. 

    The only breaking changes listed for the latest compared to 2023-10-16 are:

    PaymentIntents now has automatic_async as the default capture method when capture method is not specified during PaymentIntents creation. For more information about async capture, view the asynchronous capture guide.
    Fields under rendering_options for invoices are now migrated under rendering.
    Product ‘features’ has been renamed to marketing_features.

    I guess they don't affect the module? 

  5. 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.

  6. 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?

  7. 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}

  8. 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.

  9. 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? 

×
×
  • Create New...