In Moodle 2.2.3, after 10-12 seconds TinyMCE (TinyMCE HTML editor; editor_tinymce; Standard; 2012030300) buttons will show up (loads very slowly). Where problem lies? Can't figure out how to speed up TinyMCE HTML editor loading time.
I have Moodle 2.2.3+ (Build: 20120519).
I found a solution. The cause, why it was slow, was because it was in estonian. I had to change whole user language into english and it fixed it.
I met the same problem: on my project tinymce loaded about 10 seconds. Solution to speed it up was to disable plugins, which I don't need.
For example:
at default config plugins option was:
plugins: "visualblocks,visualchars,pagebreak,layer,table,save,jbimages,link,emoticons,insertdatetime,preview,media,searchreplace,print,paste,directionality,fullscreen,noneditable,visualchars,nonbreaking,template",
After remove unused plugins it was:
plugins: "jbimages,link",
and editor loading became 2 seconds.
P.S. jbimages is a plugin to upload images.
Look at your caching. The tinyMCE JS files ought to be kept by the browser and recycled, but sometimes this doesn't happen. Use Firebug or Chrome developer tools to see if they are being loaded from cache or from the server. If from the server, you may need to tweak your web server settings so that JS files have an expires header.
Related
I am trying to design a Gantry template for Joomla with less. It doesn´t work. No updates.
I´ve tried every solution i've found on the internet now.
My less changes doesn´t work/updates.
This is what I done/do:
In Joomla: Turned off all Joomla cache functions in configuration and plug-ins. I clear cache both in Joomla configuration and Gantry Theme after updates. I also use NoNumber Cache Cleaner plug-in. In my index.php header I have entered: [header("Cache-Control: no-cache, must-revalidate");] and [header("Pragma: no-cache");]
In files: I use Gantrys file naming [menu.less -> menu-custom.less]. The files "Modified" time stamp on the remote server are right/updated. The code are right in those files.
But when I check the code with Firebug the old code is still there.
Browser: Private Browsning in Firefox
Nothing works. Updates doesn´t show up.
What more can I do?
Best regards
/Magnus
I am trying to set up the mapping feature in Chrome canary. I followed the screenshots in this answer.
The main feature works, when I inspect an element, it points me to my local sass file and when I edit it, the local file safes, and the `sass --watch' is triggered. However, the browser does not refresh, even though on the "General" tab in devtools I have checked "Auto-reload CSS upon Sass save".
Should the browser reload? Is there a way to get it to reload?
Ps - I have compass but I can not use that as it does not support mapping, so I am compiling sass through the terminal
Thanks
You probably forgot this step:
In the Sources tab, find your generated CSS file, right click on it and choose Map to network resource, and select the same file name in the shown dropdown:
and then choose the matching file from your workspace:
It could be that the Sass-file is still compiling when Chrome tries to reload the CSS. Setting the 'Auto-reload CSS upon Sass save' Timeout to 5000 ms fixed it for me. When Chrome triggers the reload, it can even prevent Sass from recompiling the CSS.
I solved the problem by installing tincr extention and now when I save locally, the browser refreshes.
I need a rich textarea in which we have the option to insert images from the local file-system and upload it to the server (also S3 - but it can done with a background task).
I am currently using tinymce but it does not have the feature to insert image from the local filesystem.
What can I use to get such a functionality?
NB - I am using PHP as the backend.
CKeditor seems quite good. I used it some time ago and it developed since... You would have to buy CKFinder probably (for $59 per Website...)
... and then there are the TinyMCE Plugins for this that cost almost the same:
http://www.tinymce.com/
If you are looking for a free plugin to TinyMCE or CKEditor with local file browsing google for TinyMCE and iBrowser, TinyFCK, Kae’s File Manager, Ajax File Manager, TinyBrowser. (I got the list from http://www.tyssendesign.com.au). I would go with the Tiny Browser or the Ke's Filemanager and keep TinyMCE because its already there (But Do have a look at CKEditor - its quite good and those two filemanagers can plug into it too)
You are not the first to stumble over this problem. Have a look here for a brief overview over solutions.
RESOLVED
Unbeknownst to me, Cloudflare defaults to caching all css/js files for 4 hours.
Scenario:
I add this to our front page:
<span class="test">hullo!</span>
and this to our css file:
.test { font-size:2.0em; }
I do a web deploy, OR full publish to Azure and the span appears on the front page, but not the styling. The css file for some reason does not get updated. FF, IE, Chrome and Safari all confirm it. However, after a seemingly arbitrary time, the css file get updated.
Even when I remote into the Azure VM and restart the app, the styling is unchanged. The app is running on one instance, one role. No Azure Caching is setup. Adding a querystring param to the css file link does not help. Seems like a caching issue but no clue how to resolve.
Any ideas?
"We are using Cloudflare which has a default set up to cache all CSS and JS files. It purges the cache every 4 hours which resulted in the arbitrary updates. So, even though I was adding a new query string to the end of the css file, Cloudflare still cached the old one"
Just a quick note that you should go to CloudFlare Development Mode when making changes to the static content files on your site. You can get to Development Mode to bypass the cache by going to: settings->Development Mode. You also have the option of purging your cache as an additional option, which we would only recommend if you really want to purge everything.
Looks like it's cached by your browser. Can you please try navigate to your site and press Ctrl+F5.
Maybe you can use Fiddler to see if the CSS had been cached, or not updated, or some error when download.
This issue is resolved.
We are using Cloudflare which has a default set up to cache all CSS and JS files. It purges the cache every 4 hours which resulted in the arbitrary updates. So, even though I was adding a new query string to the end of the css file, Cloudflare still cached the old one.
I have dealt with this and I will tell you that from my experience in Chrome you can set a setting that disables the cache in the developer tools, however, I've noticed that unless you have the dev tools window open when you hit Ctrl+F5 it doesn't reload the cache. In IE there is a global setting in the dev tools that will make it redownload everything every time. In Firefox there is also a setting in the dev tools that will require it to download and not use the cache.
One way that you can test this, and how I test this, is by running Fiddler and watching if it does a full download of all your files or if it's caching.
From what I've experienced is that this is truly a browser caching issue and not anything to do with Azure.
It looks like IE7 doesn't reload the latest version of my stylesheet each time I upload a new version on the server.
This is annoying as I am debugging my .css file to make it work on IE...
Tried to empty the browser cache but still not working.
Thanks for your help.
Ctrl-F5 - forcible way to reload in IE
Include your version number in the file name. myfile_v1234.css
When testing, every time you do an update you can just wite "stylesheet.css?r=98123"
As long as the query string is different, it'll be downloaded again.
If you need, you can use javascript to append Math.random(), to get the random number. Not required on production though, when updates would be stable.
2 Questions:
Does IE eventually load with the newer stylesheet?
How are you saving the changes to the server (SSH, Web Interface, etc.)?
I ask because I ran into an issue with a web-based file management system a while back where one browser would show the CSS just fine, the other wouldn't, and we noticed the issue of which browser played nicely depended on which browser we used to upload the CSS.
The reason turned out to be that IE gave the CSS file a different MIME type than Firefox. If you continue to notice the issue even when you've cleared the cache, check the MIME type of the file using Firefox by going to Tools > Page Info.
Also, if it is simply a caching issue, consider turning caching off in IE. I believe this should be an Advanced Option under Internet Options.
Also, you may want to try creating a special developer environment for IE (if it comes down to it.) Perhaps have another machine with IE7 and no caching and any other features turned off (A kiosk mode, perhaps), and then previewing the page on that machine.
Thanks to you all!
I did manage to solve my problem with the "stupid" Ctrl+F5, and by changing the Internet Parameters of Windows to reload content every new visit.