I tried a new 1.10-beta3 install on a different server with its own SSL cert. This time, however, I had a hard time getting MicroTiny to start-up for content textareas. I just found the "problem" and thought that, while technically it may not be a bug, at the very least, it should be mentioned in the 1.10 release notes. That said... there is a simple code change that would make this a non-issue. More on that after a description of the problem...
It seems that MicroTiny init. code is cached in /tmp/cache in files with names that match this regex: '^mt_[0-9a-z]{32}$'. Such names are a problem if you happen to use a particular mod_rewrite rule taken from doc/htaccess.txt:
Code: Select all
# 301 Redirect all requests that don't contain a dot or trailing slash to
# include a trailing slash
RewriteCond %{REQUEST_URI} !/$
RewriteCond %{REQUEST_URI} !\.
RewriteCond %{REQUEST_METHOD} !POST$
RewriteRule ^(.*) %{REQUEST_URI}/ [R=301,L]
Code: Select all
GET /tmp/cache/mt_0f3d9d7e1635a606aa639e5d24f0575b?t=1316595595 HTTP/1.1
...
HTTP/1.1 301 Moved Permanently
...
GET /tmp/cache/mt_0f3d9d7e1635a606aa639e5d24f0575b/?t=1316595595 HTTP/1.1
...
HTTP/1.1 404 Not Found
There is another issue related to this test case, but I'll create a separate post for it so that it can be tracked separately.
Hope this helps,
Fred P.