Bug #12830

Docker: qtSwordPluginWorker ability never gets added to the worker

Added by José Raddaoui Marín 3 months ago. Updated 3 months ago.

Status:NewStart date:02/19/2019
Priority:LowDue date:
Assignee:-% Done:


Target version:-
Google Code Legacy ID: Tested version:2.4, 2.5
Sponsored:No Requires documentation:Yes


The qtSwordPlugin is disabled and its classes are not being loaded by default. When the plugin is enabled through the GUI, the classes are loaded and, after restarting the worker, the qtSwordPluginWorker ability is added to the worker.

That's true in an installation where the application and the worker are in the same machine, but it's not the case in the Docker environment, where both things are in different containers.

As a quick solution, and an option for a long term fix, the qtSwordPlugin could be enabled by default, by adding it to the initial plugins array:



#1 Updated by Dan Gillean 3 months ago

  • Assignee set to José Raddaoui Marín
  • Requires documentation set to Yes

Personally, I think that enabling the SWORD worker by default sounds like an acceptable solution if it will resolve this issue. Users can always choose to disable it after installation if desired. We could add a note to that effect in the documentation.

#2 Updated by José Raddaoui Marín 3 months ago

Okay, adding it to the initial plugins it can't never be disabled (like the Accessions and Elasticsearch plugins, for example). If that's okay the fix is easy, as mentioned in the description. Otherwise, this will require further analysis.

#4 Updated by José Raddaoui Marín 3 months ago

  • Assignee deleted (José Raddaoui Marín)
  • Priority changed from Medium to Low
  • Target version deleted (Release 2.5.0)

Discussed via email and enabling the SWORD plugin by default is not a desired solution.

Also available in: Atom PDF