Blank WordPress editor

Hi,
The following directives in
/usr/local/nginx/conf/wpsecure_YOURDOMAIN.COM.conf

---

# Block PHP files in includes directory.
#location ~* /wp-includes/.*\.php$ {
# deny all;
#}

# Block PHP files in uploads, content, and includes directory.
# original location ~* /(?:uploads|files|wp-content|wp-includes)/.*\.php$ {
location ~* /(?:uploads|files|wp-content)/.*\.php$ {
deny all;
}
causes /wp-includes/js/tinymce/wp-tinymce.php not to load and the editor is blank.

The above code with added comments, comments out the lines that break tiny mc.

That allows the editor to work but removes the security, can we check for wp-login cookies and block if not logged in
a location if ! directive
I'll work on it later,

BR,
Sean

 

Eva,

I did not screenshot it. Just the text box area in the page/post editor would not load the html and the text/visual or the editing plugin button were grayed out. I looked in chromes developer console and it just said, "wp-tinymce.php not loaded". A hah!

BR,
Sean

 

Eva
I added that code and restored the original code and I am back to the blank text box and the dev console telling me

Failed to load resource: the server responded with a status of 403 (Forbidden)
post.php:4815 Uncaught ReferenceError: tinymce is not defined
wp-langs-en.js:235 Uncaught ReferenceError: tinyMCE is not defined
post.php:4810 Uncaught ReferenceError: tinymce is not defined
admin.js:83 Uncaught ReferenceError: tinyMCE is not defined

BR,
Sean
P.S How about only running that deny if not logged in?

 

Eva,

I find that things run differently on every platform. It's just part of the process weeding out the weird stuff and it's probably job security!

BR,

Sean

 

Matt,
That would be the latest as of Friday.

BR,
Sean

 

Matt,
It's 123.08stable. I deactivated all plugins, as per the usual and same problem. Restarted nginx. Same problem. The /usr/local/nginx/conf/wpsecure_YOURDOMAIN.COM.conf includes a deny for that dir and the console shows wp-tinymce.php as not available and browsing to the file is a 403. Commented out the "offending" code, restarted nginx and it's good to go.
BR,
Sean