Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TinyMCE API key requirement message hides the menu #262

Open
Makaopior opened this issue Nov 29, 2023 · 5 comments
Open

TinyMCE API key requirement message hides the menu #262

Makaopior opened this issue Nov 29, 2023 · 5 comments

Comments

@Makaopior
Copy link

Describe the bug
After opening TestCases tab with registered Test Cases, a message about TinyMCE API registration appears and hides the app menu.

To Reproduce
Steps to reproduce the behavior:

  1. Open TestCases tab
  2. If there are no test cases, register one
  3. A message about TinyMCE API key registration appears in the left-top corner, hiding the menu.

Expected behavior
No warning messages are shown

Screenshots
Expected behavior:
image

Actual behavior:
image

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser Chrome
  • Version 119.0.6045.160

Additional context
It looks like TinyMCE begins to require API key in the next year. At least there should be a way (maybe through config file) to provide this key to the TinyMCE Editor component. But as the developer states on their official site https://www.tiny.cloud/pricing/ , free plan only includes 1000 loads / month. I don't know what counts for 1 load (there are multiple requests to TinyMCE CDN for each test case, the more steps it contains, the more requests are issued. Is each one considered as 1 load?), but it may be too restricted for some scenarios.
So, maybe you should consider using the different CDN to avoid API Key requirements (such as https://cdnjs.com/libraries/tinymce ), or move to different open-source HTML Rich editor component.

@jamolloy
Copy link

Bump on this. Quack is great and an extra bump goes to the "move to different open-source HTML Rich editor component."

@prashant-td
Copy link

prashant-td commented Feb 7, 2024

Facing the same issue.How to move to different HTML rich editor? Any setting ?

@melowody
Copy link

Bump, we're running into the same issue and the text boxes are completely unusable due to it. If there's no way to put in an API key or switch to a different rich editor component then quack has essentially become useless for us.

@azee
Copy link
Collaborator

azee commented Feb 28, 2024

@melowody are you using an open source local version or a cloud one?
In case of a local one just add your own key valid for your own domain as it was done here
687e87a

For cloud the solution is on the way

@azee
Copy link
Collaborator

azee commented Mar 2, 2024

Fixed in cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants