developersociety / django-glitter-news Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 1.0 58 KB

Glitter News

License: BSD 3-Clause "New" or "Revised" License

Python 83.29% Makefile 16.71%

django-glitter-news's People

Contributors

Watchers

Forkers

axsapronov

django-glitter-news's Issues

pip doesn't install Taggit automatically

some-glitter-project$ pip install -e ~/Projects/django-glitter-news/
some-glitter-project$ ./manage runserver

glitter_news.Post.tags: (fields.E300) Field defines a relation with model 'Tag', which is either not installed, or is abstract.

Add option to make sticky posts not sticky in the main list view

Add ability to make posts sticky

Add glitter_apps.py

To integrate with Glitter's glitter-app feature.

Create new version to be used in cofeportsmouth

Enhanced support for filtering on tags in get_latest_news

Add tags in to the search results

Can't edit news posts in the future

allow_future is False, which is fine if you're a front end user - don't want users to see upcoming news posts. However this makes it impossible for staff to even edit a post, as they're taken to the live page to edit it.

This probably needs some additional mixins/documentation to explain the problem and work around it.

Add Makefile for easier releasing

Create some default templates

Would allow for quicker setup of Glitter News.

Templates would need lots of blocks and a sensible extend hierarchy, which can then be overridden as needed per project.

Add tox/tests

As a bare minimum, test migrations.

Allow news categories to be orderable

When displayed on the frontend, the categories are always displayed in alphabetical order.

Allow them to be orderable in the admin side, which then follows through to the frontend.

RSS feeds

Needed - currently in basic news but not this one.

RSS per category needed as well.

django-glitter-news broken by django-glitter and django-taggit

Hi, users are unable to run django-glitter-news due to dependency conflict with django package. As shown in the following full dependency graph of django-glitter-news, django-glitter requires django <1.10,>=1.8，while django-taggit requires django >=1.11.

According to pip’s “first found wins” installation strategy, django 1.9.13 is the actually installed version. However, django 1.9.13 does not satisfy >=1.11.

Dependency tree-----------

django-glitter-news - 0.3.3
| +- django-admin-sortable(install version:2.1.18 version range:>=2.0.0)
| | +- django(install version:3.0 version range:*)
| +- django-glitter(install version:0.2.10 version range:*)
| | +- django(install version:1.9.13 version range:<1.10,>=1.8)
| | +- django-mptt(install version:0.10.0 version range:>=0.7)
| | | +- django(install version:3.0 version range:>=1.11)
| | | +- django-js-asset(install version:1.2.2 version range:*)
| | +- django-mptt-admin(install version:0.7.2 version range:>=0.3)
| | +- django-taggit(install version:1.1.0 version range:>=0.21.3)
| | | +- django(install version:3.0 version range:>=1.11)
| | +- python-dateutil(install version:2.8.1 version range:>=2.6.0)
| | +- sorl-thumbnail(install version:12.5.0 version range:>=12.2)
| +- django-taggit(install version:1.1.0 version range:>=0.21.3)
| | +- django(install version:3.0 version range:>=1.11)

Thanks for your help.
Best,
Neolith