Hi Sergei,
this has been brought up once before so this is something I am aware of.
The problem is that it’s an issue that affects an exceedingly small amount of users since having the VE disabled is not something the average user does. On top of that, implementing a solution adds a lot of development and complexity.
For example, to fix, I’d need to:
- Detect if the VE is disabled either globally or on the users profile settings. This will slow down page loads as it’s two additional queries
- If the VE is disabled, I need to stop the custom implementation of tinyMCE (WordPress’ VE – the “Classic Editor”) and implement an entirely different custom solution. Probably just a basic textarea box.
- Now we have more issues. The one other user I know of that has the VE disabled does so to use markdown format. So now I need to implement markdown formatting for this custom text area. Or what about HTML? Do you plan to allow for HTML tags like
strong
or em
or anything else? Now I need to clean and sanitize a textarea that allows for code – always a security risk.
So the short of it is that especially as just an independent developer doing this in my spare time, I just don’t think it’s worth the development time to make this a seamless experience for users like yourself who have the VE disabled – especially since as you’ve already discovered, there is a working solution for this (although I admit that it is super annoying to have to enable then disable the VE each time).
HOWEVER, maybe a “stop-gap” solution could be good? I’ll need to think about this more and look into how hard it would be to implement, but here is an idea that should at least make this a lot less annoying for you.
WHAT IF, I somehow detect when the tinyMCE fails to load (this way we don’t have to do the unnecessary query lookups on page load). If it fails to load, we assume the reason is that the VE is disabled. We can then show a toggle option that connects directly to the site’s global setting to disable the VE. This way you can toggle the VE on directly from HD Quiz. You’ll still need to disable from the global site settings page again, but this should still be a major improvement to the workflow. What do you think?