Comments on: WYSIWYG editor in Django Admin http://djangodays.com/2009/05/14/wysiwyg-editor-in-django-admin/ A growing collection of all things Django Thu, 26 Aug 2010 13:23:11 +0200 http://wordpress.org/?v=2.8.4 hourly 1 By: Joost http://djangodays.com/2009/05/14/wysiwyg-editor-in-django-admin/comment-page-1/#comment-6858 Joost Thu, 29 Oct 2009 17:34:40 +0000 http://djangodays.com/?p=107#comment-6858 doesn't really matter as long as you put all the necessary files in the MEDIA_ROOT so you can access them doesn’t really matter as long as you put all the necessary files in the MEDIA_ROOT so you can access them

]]> By: Robert Vernon Phillps http://djangodays.com/2009/05/14/wysiwyg-editor-in-django-admin/comment-page-1/#comment-6857 Robert Vernon Phillps Thu, 29 Oct 2009 17:01:02 +0000 http://djangodays.com/?p=107#comment-6857 What does it mean 'put it in'? Should I just copy the tar.gz file to my MEDIA_ROOT and do tar zxvf there? Or should I extract it elsewhere and copy in some subset of the entire extracted tree? What does it mean ‘put it in’?

Should I just copy the tar.gz file to my MEDIA_ROOT and do tar zxvf there?
Or should I extract it elsewhere and copy in some subset of the entire extracted tree?

]]> By: Joe Devon http://djangodays.com/2009/05/14/wysiwyg-editor-in-django-admin/comment-page-1/#comment-5902 Joe Devon Sat, 08 Aug 2009 19:55:35 +0000 http://djangodays.com/?p=107#comment-5902 Was media+'/js/editor.js' a typo? Shouldn't that be: media+'/js/fancyedit.js' ? Was

media+’/js/editor.js’

a typo? Shouldn’t that be:

media+’/js/fancyedit.js’

?

]]> By: Jarom McDonald http://djangodays.com/2009/05/14/wysiwyg-editor-in-django-admin/comment-page-1/#comment-5884 Jarom McDonald Fri, 07 Aug 2009 21:59:50 +0000 http://djangodays.com/?p=107#comment-5884 Firefox (and perhaps other browsers) will never let you access element properties cross-domain. Since the development server is serving on a different port, even if the hostname is the same then Firefox, by default, treats it as two different sources. In production, though, things work very smoothly (for example, I'm running django through Apache's mod_wsgi), as both your django app and the static assets are now in the same domain and on the same port. Firefox (and perhaps other browsers) will never let you access element properties cross-domain. Since the development server is serving on a different port, even if the hostname is the same then Firefox, by default, treats it as two different sources.

In production, though, things work very smoothly (for example, I’m running django through Apache’s mod_wsgi), as both your django app and the static assets are now in the same domain and on the same port.

]]> By: christian http://djangodays.com/2009/05/14/wysiwyg-editor-in-django-admin/comment-page-1/#comment-4004 christian Mon, 22 Jun 2009 07:47:29 +0000 http://djangodays.com/?p=107#comment-4004 This looks straight forward, but I get security issues from the Ajax calls. Access to restricted URI denied" code: "1012 [Break on this error] (function(){var R=/((?:\((?:\([^()]+\)|[...(J,typeof K==="string"?K:K+"px")}})})(); jquery.min.js (line 19) Permission denied to get property HTMLDocument.styleSheets [Break on this error] var styles = this._doc.styleSheets[0]; When testing locally django runs on: http://127.0.0.1:8000/ and my static assets are served from http://127.0.0.1/~christian/ Do you use any particular settings to run it locally? This looks straight forward, but I get security issues from the Ajax calls.

Access to restricted URI denied” code: “1012
[Break on this error] (function(){var R=/((?:\((?:\([^()]+\)|[...(J,typeof K==="string"?K:K+"px")}})})();
jquery.min.js (line 19)

Permission denied to get property HTMLDocument.styleSheets
[Break on this error] var styles = this._doc.styleSheets[0];

When testing locally django runs on: http://127.0.0.1:8000/ and my static assets are served from http://127.0.0.1/~christian/
Do you use any particular settings to run it locally?

]]>