Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-4536

Plugin PlunetConnector JS Injection after Update to Plunet 10

XMLWordPrintable

    • Medium
    • Hide
      TRANSLATE-4536: Plugin PlunetConnector JS Injection after Update to Plunet 10
      - added header "Cross-Origin-Resource-Policy" and "Referrer-Policy" for JS injection;
      - new JS selector for T5-icon clone-original;
      - improved logging;
      - update T5 import-worker trigger;
      Show
      TRANSLATE-4536 : Plugin PlunetConnector JS Injection after Update to Plunet 10 - added header "Cross-Origin-Resource-Policy" and "Referrer-Policy" for JS injection; - new JS selector for T5-icon clone-original; - improved logging; - update T5 import-worker trigger;

      Problem

      After Update to Plunet 10 JS Injection can not be loaded any more. JS Error in Plunet is:

      Die Ressource unter "https://sylvi.translate5.net/editor/plugins_plunetconnector/plunetinjection" wurde aufgrund ihres Cross-Origin-Resource-Policy-Headers (oder dessen Fehlens) blockiert. Weitere Informationen unter https://developer.mozilla.org/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)#
      

      Solution

      adding the following header allows the Injection to be loaded:

      header('Cross-Origin-Resource-Policy: cross-origin');
      

      additional Problem

      sadly after Injection can be loaded again, tasks are submitted to Translate5 but Import does not work.
      Looks like preparation of data can not be finished. So may there are more changes in Plunet10 which affect the Plugin in a deeper way.

      Solution

      problem (luckily) was based on the recent reworks of triggering/starting the task import worker. Axel simply missed this place to rework.
      Now its changed and task now are transfered to Translate5 as expected.

            Stephan Stephan Bergmann
            Stephan Stephan Bergmann
            Axel Becher
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: