pip install django-filer

ls site-packages/filer/

no media dir found

The File/Image Widget does not handle selecting files correctly if it is a dynamically (Javascript) added record in an ModelInline (new in django 1.2)

Users should be able to have a list of favorite folders for fast access

When using a FilerImageField in a stacked inline in the admin, when you select the 'Add another..." button to get another inline the FilerImageField will no longer work.

When you select your image, the pop-up flickers and I get the following js error:

document.getElementById(img_name) is null
[Break On This Error] document.getElementById(img_name).src = chosenThumbnailUrl;
Line: 12 popup_handling.js

I'm running the following:
django==1.2.5
django-cms==2.1.3
django-filer==0.8.2

The only error stoppong filer to work on python 2.4

Looks like there might be a typo in this file on line 64:
filer/templates/admin/filer/folder/directory_listing.html

Originally:

<span class="small quiet">({% blocktrans count folder.children_count as counter %}1 folder{% plural %}{{ counter }} folders{% endblocktrans %}, {% blocktrans count folder.file_count as counter %}1 file{% plural %}{{ counter }} files{% endblocktrans %})</span>

Changed to:

<span>{% if is_popup %}{% else %}<a style="display: block; float: right;" class="changelink" href="{% url admin:index %}filer/folder/{{ folder.id }}/" title="{% trans "Change current folder details" %}">{% trans "Change" %}</a>{% endif %}</span>

Seemed to fix the link problem i had.

It seems like django-filer tries to separate images and other files, but it does not really succeed. For example, in main folder list there is a count of images, but if I open a folder, it counts images. In both cases it displays the same number and it is a number of all files. But as it seems from this error:

https://github.com/stefanfoulis/cmsplugin-filer/issues/#issue/11

There is some notion of difference between files and images? So it would be possible to display count for both images and files?

Prevent certain files from being downloadable if you don't have permissions.
This could be implemented with the "x-sendfile" header for most hosting situations. While in development files can be served directly by the development server.
Public files could be served separately without going through the django app for performance.

seems to be a js bug

Files should be displayed grayed out in the folder view of they are in the clipboard (and not removed from the folder as soon as they are added to the clipboard)

https://github.com/stefanfoulis/django-filer/blob/develop/filer/admin/imageadmin.py#L30

and replace them with python logging, where appropriate.

The popup for a image field should only display images (or make it clear what can be selected in some other way)

In filer/settings.py, several variables such as FILER_STATICMEDIA_PREFIX are being defined and run through os.path.normpath() at the last step. Where settings such as settings.MEDIA_URL are absolute urls, i.e. starting with 'http://' (as they are welcome to do, and is recommended for separate media servers), normpath() collapses 'http://' to 'http:/', breaking the link.

allow replacing a file with a new version. that way all apps that link to the file instantly have the new version.

This is tricky because it gets added by django admin automatically and outside of the scope of the widget (it gets recognized as a ForeignKey).

in frontend:
display placeholder
in backend:
inform about missing image. allow replacing.

some files may be in non default locations if a migration happened from image_filer or some other system

with elFinder (or maybe custom with jsTree)

some js is loaded directly from jquery.com and is chaotic. Load it with the Media class on admin.

In imagemodels.py, the following lines require "hard-coding" the media directory to be /media:

def rel_image_url(self):
    'return the image url relative to MEDIA_URL'
    try:
        rel_url = u"%s" % self._file.url
        if rel_url.startswith('/media/'):
            before, match, rel_url = rel_url.partition('/media/')
        return rel_url

If you wish to use a different format, eg: /site_media/media (as Pinax does), then this code renders <img src=""> instead of the actual URL.

Might I suggest that since the description states: 'return the image url relative to MEDIA_URL', that the function actually use settings.MEDIA_URL?

• one clear "insert" link (no more clicking on title or thumb to insert)
• allow change_view of image in popup (needs clean popup propagation)

zips, tar.gz, bzip, ...
should be possible to "unpack" from the ui.

When running on Windows, the "upload" button does not appears.
The reason is wrong code in settings.py

FILER_STATICMEDIA_PREFIX = os.path.normpath( getattr(settings, 'FILER_STATICMEDIA_PREFIX', os.path.join(settings.MEDIA_URL,'filer/') ) ) + '/'

On windows delimiter of path is ''. And now on Windows this code generates url like \media\uploads/filer/

I think there shouldn't be os.path functions at all or they should be wrapped by urllib.pathname2url

Another symptom of this was reported by @hipikat in #60:
In filer/settings.py, several variables such as FILER_STATICMEDIA_PREFIX are being defined and run through os.path.normpath() at the last step. Where settings such as settings.MEDIA_URL are absolute urls, i.e. starting with 'http://' (as they are welcome to do, and is recommended for separate media servers), normpath() collapses 'http://' to 'http:/', breaking the link.

• strict by date? (2010/01/13/myfile.jpg)
• by some UUID type random part (AE/B8/myfile.jpg)
• constantly rename and move based on the sligified foldernames and filename?

to see what gets deleted due to cascading before deleting

e.g.
Profiles: the profiles app mounts itself into the "Avatars" Folder in Filer. All avatars are saved there.

TV-Shows: A TV-Shows app mounts itself into the "TV-Shows" Folder. Subfolders are automatically populated: "Battlestar Galactica" > "Season 1" > "Episode X"

CMS plugins make a virtual folder "CMS" -> "Page 5" with all the media used in plugins on that page.

the popup should open in the folder where the current image is

collections are lists of files that can be created in admin and can be used by other apps. e.g for a slideshow or download list.
collections should be dynamic. e.g add all images that are in folder X these two files and all files that have tag Y.

Having a harsh time trying to install this app. There are no instructions that I can find.
I cloned from git, did a setup and added 'filer' to my INSTALLED_APPS. Managed to run syncdb okay. All seems fine.
When I go into admin, I see the "Image Filer" section. I can go into "Folder permissions", but not anywhere else.

Here's the error message I get. Will hack further, but have little time.

TemplateDoesNotExist at /admin/image_filer/folder/

image_filer/directory_listing.html

Request Method: GET
Request URL: http://ddm.cms/admin/image_filer/folder/
Django Version: 1.2.1
Exception Type: TemplateDoesNotExist
Exception Value:

image_filer/directory_listing.html

Exception Location: /usr/local/lib/python2.6/dist-packages/django/template/loader.py in find_template, line 138
Python Executable: /usr/bin/python
Python Version: 2.6.4
Python Path: ['/usr/local/lib/python2.6/dist-packages/django_cms-2.1.0.beta3-py2.6.egg', ... '/usr/local/lib/python2.6/dist-packages']
Template-loader postmortem

Django tried loading these templates, in this order:

* Using loader django.template.loaders.filesystem.Loader:
* Using loader django.template.loaders.app_directories.Loader: 

I've got django-filer up and running with Django 1.2.4, but with Django 1.2.5. files won't show up in the clipboard. An error is displayed in the clipboard instead: "upload failed". So I cannot assign uploaded files to any folder.

Although files are uploaded to the file system and written into the folder "filer_private".

there are js errors with IE7 and IE8

the change should likely be done here: https://github.com/stefanfoulis/django-filer/blob/develop/filer/models/imagemodels.py#L128

Apologies if this has already been fixed - I'm using an older version, but I haven't seen any reference to this, so maybe it's still an issue.

If the image is square or wide, then the focal point works well. If the image is taller than it is wide, though, what happens is that values generated by the focal point tool are incorrect by height/width.

So if the image is 2000x3000, the values will be divided by 1.5.

that is displayed in the change_view of filer in the admin