Don't display Azure requirement error if other services are used as default

Created on 26 February 2024, 10 months ago
Updated 15 March 2024, 10 months ago

Problem/Motivation

I have configure Alttext.AI to be used with this module.

I don't use the Azure service, but I still get this error:

Steps to reproduce

  1. Install the module
  2. Configure the module to use Alttext.ai
  3. Go to 'Status Report' page on the site
  4. See the error

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Fixed

Version

2.0

Component

Code

Created by

🇮🇳India dipakmdhrm

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @dipakmdhrm
  • 🇮🇳India dipakmdhrm

    I had some trouble with MR workflow, so here's the patch removing all requirement error code.

  • 🇮🇳India dipakmdhrm

    This patch removes all requirement error code.

  • 🇩🇪Germany slowflyer

    Removing all requirement code can not be the solution.

    No matter which provider is used, configuration is needed.

  • 🇷🇸Serbia miksha

    As this module initially had only one service provider (Azure) and was later extended to support Alttext.AI I would rather go with updating requirement message to something more generic because message about missing Azure configuration is now a bit misleading. Also not sure if module gracefully handles missing provider configuration. But to me more sense is to inform site developer that this module needs config to be set than to allow enabling module without proper config.

  • Status changed to Fixed 10 months ago
  • 🇩🇪Germany slowflyer

    Kept messages and made them more general.

    @dipakmdhrm: The submodule auto_alter_translate has no alternative provider. No need to remove any hook at all.
    @dipakmdhrm: The reason why you received the error message was that no URL is defiend for Alttext.ai. Fixed that in code.

    @miksha: Totally agree

    New version available.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024