Skip to content

Settings and activity

2 results found

  1. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Bianca Glasner shared this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Bianca Glasner supported this idea  · 
    An error occurred while saving the comment
    Bianca Glasner commented  · 

    We have another use case which would require a language specific configuration, but not related to translations.

    For our product, we require to have an account on our backend for each language. So every sales channel and language combination needs different account IDs and different API keys within the plugin configuration.

    To make it possible in the current state, we needed to implement a different config handling with an additional database table including a "language_id" column. It also required us to implement a customized config page.