If source plugin extends another, create jobs through original plugin

Created on 9 September 2024, 7 months ago
Updated 19 September 2024, 7 months ago

Problem/Motivation

Using πŸ“Œ Avoid self:: calls to be able to extend the sources form ContentEntitySourcePluginUi class Fixed to extend the content source plugin to add a tweaked UI, let's call it extending_content, I discovered that jobs created through it showed up in the tmgmt_job_item table with plugin set to extending_content.

Subsequently, the job status didn't appear on the translate tab, in the content source UI, or even my new extending_content source UI (since it mostly extends the content source UI). This is because they expect the tmgmt_job_item plugin value to be content.

Steps to reproduce

Create a source plugin extending ContentEntitySource. In annotations set an ID and a UI class extending ContentEntitySourcePluginUi. Request a translation. The status for the job does not appear anywhere (translate tab, content source UI, new content source UI). In the tmgmt_job_item table see that the job item has as its plugin the ID you set for the new source plugin.

Proposed resolution

Add an annotation option that lets you submit jobs for another source plugin.

Data model changes

New source plugin annotation "source_type".

πŸ“Œ Task
Status

Closed: works as designed

Version

1.0

Component

Source: Node

Created by

πŸ‡ΊπŸ‡ΈUnited States charginghawk

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024