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

Error loading TinyMCE scripts through wp-tinymce.php #7133

Closed
jeremyfelt opened this issue Jun 4, 2018 · 0 comments · Fixed by #9373
Closed

Error loading TinyMCE scripts through wp-tinymce.php #7133

jeremyfelt opened this issue Jun 4, 2018 · 0 comments · Fixed by #9373
Labels
Backwards Compatibility Issues or PRs that impact backwards compatability [Type] Bug An existing feature does not function as intended

Comments

@jeremyfelt
Copy link
Member

Describe the bug

Some servers may expect that TinyMCE is loaded with static JavaScript files rather than wp-tinymce.php.

In WordPress core, TinyMCE is loaded as "compressed" via wp-tinymce.php or uncompressed (?) via tinymce.min.js depending on a handful of conditions.

I haven't tracked down the conditions that are causing my server to request the uncompressed version, but I do know that at some point I applied an Nginx configuration that blocks direct access to PHP files in wp-includes/ and wp-admin/includes/. As of Gutenberg 3.0.0, the TinyMCE script results in a 403 forbidden and the editor doesn't work.

My guess is that this problem will go away when Gutenberg is merged into core, but in the meantime it may be good to use the same logic from class-wp-editor.php to load TinyMCE.

To Reproduce
Steps to reproduce the behavior:

  1. define( 'COMPRESS_SCRIPTS', false );
  2. Block public access to wp-includes/*.php
  3. Open new post screen.
  4. Click in first paragraph block.
  5. See error.

Expected behavior
I'd expect to be able to leave my server configuration the same and access the editor.

Additional context

  • Gutenberg 3.0.0
  • WordPress 4.9.6
jeremyfelt added a commit to washingtonstateuniversity/WSUWP-Build-Plugins-Public that referenced this issue Jun 4, 2018
@danielbachhuber danielbachhuber added Backwards Compatibility Issues or PRs that impact backwards compatability [Type] Bug An existing feature does not function as intended labels Jun 27, 2018
jeremyfelt added a commit to washingtonstateuniversity/WSUWP-Build-Plugins-Public that referenced this issue Jul 16, 2018
philcable pushed a commit to washingtonstateuniversity/WSUWP-Build-Plugins-Public that referenced this issue Aug 9, 2018
philcable pushed a commit to washingtonstateuniversity/WSUWP-Build-Plugins-Public that referenced this issue Aug 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backwards Compatibility Issues or PRs that impact backwards compatability [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants