media_tree_filenode is missing a site-field #25
Comments
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 24, 2013
… shold be selectable in that site.
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 24, 2013
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 27, 2013
Making sure that the image plugin use the site filter so that only images that are added to the current site can be used.
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 27, 2013
Also filter folders that has been registerred in the current site.
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 27, 2013
This reverts commit 8e8ec15.
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 27, 2013
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 28, 2013
Also fixing the site issue for the other plugins and use limit_choice_to to make admin pick up the limitations.
erlenddalen
added a commit
to erlenddalen/django-media-tree
that referenced
this issue
May 28, 2013
Make sure the get_current is not called when being read in imports.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A filenode object is not related to a site. This must be a design flaw, because if you have several virtual hosts running on a server, you would most likely have a separate media folder for each virtual host. But media_tree assume that all filenodes are stored in a global media folder.
This should be solved by adding a foreign key to django_site, much like django-cms do in cms_page.
The text was updated successfully, but these errors were encountered: