Forum Discussion

michelle's avatar
michelle
Creator II
8 months ago

Aras 11SP9 Chrome remove XSLTProcessor

As Chrome plans to remove support for XSLTProcessor, Aras 11 SP9, which heavily depends on this technology, will be impacted. Could you please provide a hotfix or an alternative solution besides upg...
Aras Update
patricia_baxter_matrix_co_nz's avatar
patricia_baxter_matrix_co_nz
Ideator I
25 days ago

Hello Angela,

I am interested in the community based patch for Release 12SP9.  Could you please help.

Thanks,

Patricia

angela's avatar
angela
Catalyst II
25 days ago

Hi! I am working on a I12 version. I already have some of the fundamentals needed.

If I succeed, I will post my result. 
If I fail, there is a fallback that will give us more time. 

  • angela's avatar
    angela
    Catalyst II
    22 days ago

    I did some testing today with Chrome Canary.

    There is a flag that can be used to keep XSLT support available for another year. This at least ensures that users can log in, but Innovator will still be largely unusable.

    Reason: Search Modes. We will need to patch all Search Modes as well. This is not an issue for I14, but it does affect I12 and I11!!!

    I ran some initial tests and was able to restore the "Simple" search mode in I12, which provides a basic level of usability. However, all Search Modes will need to be reviewed and customized to fully address the issue. 

    Try it by yourself. Download Chrome Canary and tell me what you see!
    If in your test the grid doesn´t work, try this one. Remove the amlValidator from Simple SearchMode. It´s not a finished solution, but at least confirms that we have to update the SearchModes as well. 


    I am still working on an XSLT patch itself, using the XSLT flag is a workaround that gives us more time.

     

    • patricia_baxter_matrix_co_nz's avatar
      patricia_baxter_matrix_co_nz
      Ideator I
      14 days ago

      Thank you Angela. I was looking for a fix on Release 12SP9 (the older community version). We are doing some testing as well and will provide information if we find the fix for XSLT in Release 12SP9.

      Thanks,

      Patricia

      Tagging my colleague puneeth_makkapati_matrix_co_nz​ 

      • angela's avatar
        angela
        Catalyst II
        7 hours ago

        I made some progress and may have found a way to save a 12SP9 installation from its scheduled execution this November. At least, that's what my Chrome Canary tests suggest. 12SP9 is still an EOL version, but a dead horse isn´t really dead as long as we pump it full of steroids.☝️

        We need to patch a few files in the codetree. I use this approach: https://github.com/mfreed7/xslt_polyfill

        Using the polyfill seems to have a positive affect on this issue too: Edge upgrade kills search grid - find workaround here | Aras

        I still need to run a few more tests, but the initial results look promising.

        Question: Has anyone of you seen this warning in Edge? The red box appeared wherever XSLT was involved, for example in Signoff tabs and XSLT reports.

        One user reported it this week, but since than it´s gone and we never have seen it again: