Skip to content

Loading…

problem with TinyMCE #218

Closed
jtbayly opened this Issue · 4 comments

2 participants

@jtbayly

I've made the transition to Barracuda with about 12 sites, a number of them using TinyMCE. one of the only problems I found was with .htm files in TinyMCE not loading properly. I modified the following line in nginx_simple_include.conf to allow for serving of htm and html files:

location ~* ^.+\.(?:jpe?g|gif|png|ico|swf|pdf|doc|xls|tiff?|txt|html?|cgi|bat|pl|dll|aspx?|exe|class)$ {

But I thought you'd want to take a look at allowing them "correctly" (ie in a more limited manner). The htm files are all inside the TinyMCE folder, obviously, so maybe somebody could show me how to limit it to only serving static htm files from that folder.

@jtbayly

Actually, I have a modification to make here. I believe the problem I am having with TinyMCE is really related to the fact that it has a jscripts folder, which all the htm files reside below, and 'script' is being limited in this line of the conf file:

location ~* (?:delete.+from|insert.+into|select.+from|union.+select|onload|script|.php.+src|system(.+|iframe|document.cookie|alert|\;|..) {

So to sum up, I believe the above line is breaking TinyMCE. But I don't know how to fix it.

@omega8cc
Owner

This known issue is already fixed in head/master, see below related commits:

ae1eb35

a5b838f

f9723b1

You could upgrade to the current head or wait for next stable (expected this weekend).

@omega8cc
Owner

BTW, current (head) configuration allows you to serve static .html? files for popular wysiwyg editors while still allowing you to use .html extension for your dynamic drupal content.

@jtbayly

Wow. That was fast. Thanks so much.

@omega8cc omega8cc closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.