These plugins require a paid TinyMCE subscription

[sarina]

Hi, as far as I can tell from Accessibility Checker plugin | TinyMCE Documentation this is a paid premium feature, although that’s not stated anywhere in this post or within the README of this repo.

How would an Open edX instance go about getting a paid subscription?

Note that openedx/frontend-app-authoring#783 references the PowerPaste functionality as being paid, and this commit references the a11y checker as paid.

cc'ing involved people to see if anyone knows more: @kenclary @jesperhodge @KristinAoki have either merged to this repo or reviewed a PR.

As an editorial, I don't think features requiring a paid subscription should be in the core.

[sarina]

Note: When resolved, please update #27 with instructions on how to pay for a subscription, or, remove the doc if this feature is removed from core.

[jristau1984]

@sarina for clarity, this is the openedx portion of the paid plugin. There is also a corresponding private repo that contains the actual plugin contents. This was a requirement of getting this feature into Studio at the time, but the approach may no longer be preferred with the advancements in frontend plugin framework.

[sarina]

Thanks @jristau1984 . So basically this feature is unusable by the community? If so I'll be removing the https://docs.openedx.org/en/latest/educators/references/accessibility/accessibility_checker.html page, and you should back it up for inclusion with the partner-specific docs.

[jristau1984]

https://edx.readthedocs.io/projects/edx-partner-course-staff/en/latest/accessibility/accessibility_checker.html is the edx.org specific copy of that, which looks to have been auto-copied at some point. Removing it from openedx docs works for me. Thanks!

[sarina]

Great, thanks, I'm leaving this ticket open though because private code shouldn't be in the public project, so removal should be addressed at some point.

[jristau1984]

Is private code in the public repo? I was under the impression it is just placeholder code, needed to create an older version of a "plugin slot" to handle our private addition.

[sarina]

The community cannot use this feature - there is no explanation of how I could get the Accessibility Checker or PowerPaste features in my instance if I wanted them. So yes this should be converted to a more general plugin slot when possible. Right now I thought I was going crazy trying to understand why this checker was imported and had documentation, but wasn't showing up for me anywhere.

[jristau1984]

Tagging @schenedx - evolving this feature is something that can be added to the T&L backlog... this is an old approach to private plugins, and has been since replaced with the frontend plugin framework approach. Thanks!

[kenclary]

Is private code in the public repo? I was under the impression it is just placeholder code, needed to create an older version of a "plugin slot" to handle our private addition.

I believe that is true, or was true at the time. The public repo should only contain placeholder "stubs" for the plugins. This was always ripe for architectural refactoring.

(Hello :)

[sarina]

Thanks everyone (and hi @kenclary !)