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

WYSIWYG editor not displayed in production #339

Open
ctiller15 opened this issue Nov 7, 2021 · 0 comments
Open

WYSIWYG editor not displayed in production #339

ctiller15 opened this issue Nov 7, 2021 · 0 comments

Comments

@ctiller15
Copy link

Bug report

Describe the bug

  • the same as described over in Wysiwyg is not displayed in production keystone#3376. Essentially I receive different behavior wrt the WYSIWYG editor in both local and production. In local it displays, in production it does not. I have tested by connecting both to the same mongo database. The only differentiating factor is the editor display.

To Reproduce

Best guess -
1: Create application w/ wysiwyg editor
2: Deploy application to digitalocean or similar
3: ???
4: Observe that wysiwyg editor does not display on production but does display on local.

Expected behaviour

The same behavior between both prod and local. The WYSIWYG editor should both display and function.

Screenshots

System information

  • Browser: Firefox
  • OS linux Ubuntu 20.04 (both environments)

Additional context

I currently have the following error over in prod:

The script from “https://{website-name}/tinymce-assets/themes/silver/theme.js” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type.

Upon checking the firefox debugger in both local and prod it appears that under the site name in local the folder tinymce-assets exists, while it does not in production. This project has been in production for (several) months now untouched and only recently did the WYSIWYG editor stop showing, and all of the other fields are displaying fine. On top of that the data is fine and has appeared untouched.

So has there been a fix for this? Does it require updating the tinymce keystone package? Or is there some build setting that has been unaccounted for?

Current node dependencies:

"@keystonejs/adapter-mongoose": "^10.0.1",
    "@keystonejs/app-admin-ui": "^7.3.9",
    "@keystonejs/app-graphql": "^6.1.3",
    "@keystonejs/auth-password": "^5.1.17",
    "@keystonejs/fields": "^20.1.3",
    "@keystonejs/fields-cloudinary-image": "^2.1.0",
    "@keystonejs/fields-wysiwyg-tinymce": "^5.3.14",
    "@keystonejs/file-adapters": "^7.0.8",
    "@keystonejs/keystone": "^17.1.1",
    "cross-env": "^7.0.2",
    "dotenv": "^8.2.0"
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

1 participant