In firebug (in firefox) there is a "NET" tab that shows you all the stuff
that got loaded, including which ones 404.

When I was installing this stuff I made the mistake of installing as an
egg, and the media subdirectories didn't get pulled in.  Both tinymce
and filebrowser had problems like this.  At the very least, go to the
tar file to see what javascript/css/image stuff there is and be sure
that it is installed where your server can serve it, at the urls that the
packages are configured to use.  I don't remember that being the
last problem, but it's a start.

If all the media is working, make sure that the context pulls in an
appropriate top level js to configure tinymce.  We had this working
in one part of a site but not another, and the firebug NET tool was
very helpful in showing what was loaded in one context but not or
differently in the other.  I spent a long time setting breakpoints in
firebug, but it was an initialization issue (the plugin stuff was hard
to debug).

Bill

On Wed, Apr 28, 2010 at 9:01 AM, Bobby Roberts <tchend...@gmail.com> wrote:
> not sure how to do that...  i'm not really getting any javascript
> errors or anything.
>
> On Apr 28, 3:26 am, Xavier Ordoquy <xordo...@linovia.com> wrote:
>> Hi,
>>
>> Filebrowser is a bit tricky to setup.
>> Did you had a look at 404 requests made by your browser ? There should be 
>> something that isn't available at some point.
>> Took me some time to setup it up correctly the first time.
>>
>> Regards,
>> Xavier.
>>
>> Le 28 avr. 2010 à 04:57, Bobby Roberts a écrit :
>>
>> > hey group -
>>
>> > I've installed djangotinymce and filebrowser per the instructions.
>> > I've run across a strange issue.  When I go to insert an image, the
>> > image dialog pops up just fine with the button for filebrowser.
>> > However, when I click the filebrowser button, nothing happens.  Any
>> > idea what could be causing that?
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "Django users" group.
>> > To post to this group, send email to django-us...@googlegroups.com.
>> > To unsubscribe from this group, send email to 
>> > django-users+unsubscr...@googlegroups.com.
>> > For more options, visit this group 
>> > athttp://groups.google.com/group/django-users?hl=en.
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To post to this group, send email to django-us...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group 
>> athttp://groups.google.com/group/django-users?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to