21309 Posts in 5738 Topics by 2603 members
General Questions
SilverStripe Forums » General Questions » SS3 + Safari and missing (tinyMCE) HTMLEditors in CMS
General questions about getting started with SilverStripe that don't fit in any of the categories above.
Moderators: martimiz, Howard, Sean, Ryan M., biapar, Willr, Ingo, swaiba, simon_w
|
Page:
1
|
Go to End | |
| Author | Topic: | 403 Views |
-
SS3 + Safari and missing (tinyMCE) HTMLEditors in CMS
29 August 2012 at 9:19pm
Hi,
Just wondering if anyone else is having issues with missing HTML Editors (TinyMCE) in the CMS when using Safari (6.0 on OSX 10.7.4). All HTMLEditor fields are missing.
I keep getting this error in the Javascript error console:
ReferenceError: Can't find variable: tinyMCE
No issues noticeable in other browsers e.g. Chrome & FireFox.
Thank you.
VWD. -
Re: SS3 + Safari and missing (tinyMCE) HTMLEditors in CMS
30 August 2012 at 2:57am
Just tested it on Safari in old iOS device (3.1.3) and it's having the same issue. So I'm assuming it's isolated to Safari?
Anyone else come across this issue?
Thanks.
VWD. -
Re: SS3 + Safari and missing (tinyMCE) HTMLEditors in CMS
1 September 2012 at 5:06am
No, not me. I don't use Safari and I don't have an iOS-powered device.
I'm answering just so you don't feel as lonely on your thread as I do on those that are mine.
Cheers. -
Re: SS3 + Safari and missing (tinyMCE) HTMLEditors in CMS
1 September 2012 at 12:02pm
This was related to a bug in the index.php fall-back if the rewrite rules can't be used. A fix is provided here or (if you're using Apache) make sure mod_rewrite's enabled and AllowOverride is set to All for the folder with your installation in it.
-
Re: SS3 + Safari and missing (tinyMCE) HTMLEditors in CMS
4 September 2012 at 5:06am
@vodoomoth - thanks for your post! Now I don't feel so lonely!
-
Re: SS3 + Safari and missing (tinyMCE) HTMLEditors in CMS
4 September 2012 at 5:15am
@simon_w - Thank you for your reply Simon. I can confirm that the server does have mod_rewrite enabled.
Actually, it turned out to be a strange problem in the end. It turned out to be a corrupt _combinedfiles/cmsmain.js that kept getting copied over the properly generated/combined cmsmain.js file.
Thanks very much for taking your time to respond, Simon.
VWD.
| 403 Views | ||
|
Page:
1
|
Go to Top |
