zinnia.models.author.Author uses get_user_model() at module import time, which is forbidden by Django 1.7 (https://docs.djangoproject.com/en/dev/releases/1.7/#app-loading-refactor). 1.7 is due for release soon (beta has been released), so a way to avoid this import time dependency should be figured out.

Hi! I'm using Django 1.10 and I'm trying to deploy blog Zinnia in a Python 3 virtualenv. I installed Zinnia 0.18 using pip, and followed the "get started" guide to set everything in my site settings.py and urls.py, then made the migrations. However, when I went to 127.0.0.1/weblog , the exception raised.

django.core.exceptions.FieldError: Cannot resolve keyword 'entries' into field. Choices are: avatar, comment_comments, comment_flags, date_joined, email, first_name, groups, id, is_active, is_staff, is_superuser, last_login, last_name, logentry, password, user_permissions, username

I looked up issues solved (or closed) before, but unluckily none of them works for me.

Apps I installed:

Django==1.10 Pillow==3.3.1 PyMySQL==0.7.6 beautifulsoup4==4.5.1 django-appconf==1.0.2 django-avatar==3.0.0 django-blog-zinnia==0.18 django-contrib-comments==1.7.2 django-mptt==0.8.6 django-tagging==0.4.5 django-xmlrpc==0.1.5 mots-vides==2015.5.11 pyparsing==2.1.9 pytz==2016.6.1 regex==2016.08.27

With this patch, the app's tests all pass in django 1.6 and python 3.3. The only remaining failures are query-counting related tests (which I believe are a result of django-tagging being weird. See https://groups.google.com/forum/#!topic/django-blog-zinnia/LRUzSxLlHTM ), two tagging-related tests (I believe this is django-tagging's fault), and tests that import custom_url_shortener.py and custom_spam_checker.py . (Both of which do nothing but raise exceptions, guaranteeing the tests will fail.) The remaining failures fail when using the most recent version of 1.5, under python 2, and using the your most recent version of django-blog-zinnia, so they are not new regressions. I think they could most easily be fixed by replacing django-tagging with a better-supported tagging app. I'd like to address that and the related failures with a later patch.

Some key changes: -Changes to how views/mixins/archives.py 's get_previous_next_published works. -Replacement of explicit unicode calls with six.text_type calls. -Changed how pearson_score works completely to match the algorithm found on the internet. The original version returned values that disagreed with wolfram's calculator. My updated version matches the online calculator's values. -in preview.py, we now return str(self.preview) instead of the soup itself. (Returning a non-string in str in python 3 raises an exception) -assert(Not)Equals calls converted to assert(Not)Equal to silence deprecation warnings -a new urlEqual function was added in tests/utils.py . This is intended to compare urls that have querystrings, where ordering doesn't matter. (So two urls with querystrings in different order should still compare equal)

Some remaining questions: -CategoryAdminForm in admin/forms.py may or may not be right. The code used originally is not a part of the API so it's not documented at all. (It's not even documented in the source...) The solution currently provided makes the code run and appears to work. (It's the best guess of me and some people on the django-users IRC channel) -Why does the pearson_score function in comparison.py return 1-r instead of just r? (See the code for context) -test_vector_builder in tests/comparison.py badly needs to be looked at. I've made it disregard ordering now. I'm not sure if this is desired or not. Right now, the code assumes a stable iteration order over dictionary keys, which is not a valid assumption. I've done my best to fix it, but I don't really know if it matches what you intended or not. If the function wants to preserve order, it needs to be completely rewritten. -The changes to xmlrpc with respect to bytes vs. strings needs to be looked at. I think I did it correctly, but I'm not 100% sure. (Also tests/utils.py, TestTransport)

The Entry model is defined in the same module as the abstract entry model classes. This makes it impossible to create a custom Entry based on those abstract classes.

The documentation is also wrong as that zinnia.models.EntryAbstractClass does not exist anymore: http://docs.django-blog-zinnia.com/en/latest/how-to/extending_entry_model.html

The easiest fix for this would be to move the abstract entry model classes into a different module like zinnia.models_bases. Django Shop does it that way: https://github.com/divio/django-shop/blob/master/shop/models_bases/init.py

Update: An example project which triggers this problem can be found under https://github.com/bikeshedder/zinnia-custom-entry-example

When one of entry has a comment, it happend.

u"Your dictionary lacks key '1'. Please provide it, because it is required to determine whether string is singular or plural."

/usr/lib64/python2.7/site-packages/django_blog_zinnia-0.15.dev-py2.7.egg/zinnia/admin/entry.py in get_title {'title': entry.title, 'word_count': entry.word_count} reaction_count = (entry.comment_count + entry.pingback_count + entry.trackback_count) if reaction_count: return ungettext_lazy( '%(title)s (%(reactions)i reaction)', '%(title)s (%(reactions)i reactions)', reaction_count) % \ ... {'title': title, 'reactions': reaction_count} return title get_title.short_description = _('title') def get_authors(self, entry): ▼ Local vars Variable Value entry
<Entry: iPad mini 2 with Retina Display 使用感受: 发布> self
<zinnia.admin.entry.EntryAdmin object at 0x2bd0490> reaction_count
1L title
u'iPad mini 2 with Retina Display \u4f7f\u7528\u611f\u53d7 (25 \u4e2a\u5b57\u7b26)'

Hi, For multiples sites on the same code and db (example : bob.text.org, sam.text.org) the class views/entries/EntryDateDetail return 404 for not current site after click to read more. It happened because queryset = Entry.published.on_site() return None for current site with other id. After change to queryset = Entry.objects.all() everything is OK. Is it possible fix it?

Thank you a lot.

I have installed zinnia as per the docs and the same way I always have done.

I have synced and migrated my database and on standard pages not related to the blog, I get the error:

"Caught DatabaseError while rendering: relation "zinnia_entry" does not exist LINE 1: ...te", "zinnia_entry"."content_placeholder_id" FROM "zinnia_en... ^"

That relates to the "{% show_menu 0 100 100 100 %}" section of my templates.

Now on the page where zinnia is aphooked, I get the error

relation "zinnia_entry" does not exist LINE 1: SELECT COUNT(*) FROM "zinnia_entry" INNER JOIN "zinnia_entry...

Using postgresql + south

Apparently Zinnia 0.14 was tagged but it doesn't work under Python 3 due to its dependency from django-tagging (see #281). If the solution is difficult, may I suggest stating that in the documentation?

I am getting the following message. "TemplateSyntaxError at /admin/zinnia/ - Caught AssertionError while rendering: latest() requires either a field_name parameter or 'get_latest_by' in the model" Here is the Traceback: http://pastebin.com/2EqzPb84 I have installed Zinnia using "pip install -e git:/...", which means I have version 0.10. I get this error when I visit /en/admin/zinnia/. I tried executing "Entry.published.latest()" in the django shell and I get the same message.

I've got a fresh Django 1.8 installation, in a virtualenv with all deps successful. Running on Ubuntu 14.04.2 fwiw.

The settings is pretty much default - apart from the db settings and the zinnia needs I've not added anything (actually, not true - Django 1.8 has no 'django.contrib.sites' in INSTALLED_APPS - needed to add that). 'django.contrib.contenttypes' is in INSTALLED_APPS by default.

But I'm getting the error:

django.db.utils.ProgrammingError: relation "django_content_type" does not exist

?

Full output below:

(df)datakid@coburg:~/www/df/df-site$ python manage.py migrate /home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django_comments/init.py:4: RemovedInDjango19Warning: django.utils.importlib will be removed in Django 1.9. from django.utils.importlib import import_module

/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django_comments/models.py:2: RemovedInDjango19Warning: django.contrib.contenttypes.generic is deprecated and will be removed in Django 1.9. Its contents have been moved to the fields, forms, and admin submodules of django.contrib.contenttypes. from django.contrib.contenttypes import generic

/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django_comments/models.py:46: RemovedInDjango19Warning: Model class django_comments.models.Comment doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9. class Comment(BaseCommentAbstractModel):

/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django_comments/models.py:165: RemovedInDjango19Warning: Model class django_comments.models.CommentFlag doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded. This will no longer be supported in Django 1.9. class CommentFlag(models.Model):

/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django_comments/forms.py:3: RemovedInDjango19Warning: The django.forms.util module has been renamed. Use django.forms.utils instead. from django.forms.util import ErrorDict

System check identified some issues:

WARNINGS: zinnia.Entry.categories: (fields.W340) null has no effect on ManyToManyField. zinnia.Entry.related: (fields.W340) null has no effect on ManyToManyField. Operations to perform: Synchronize unmigrated apps: staticfiles, mptt, messages, django_comments, tagging Apply all migrations: sessions, admin, sites, auth, contenttypes, zinnia Synchronizing apps without migrations: Creating tables... Creating table django_comments Creating table django_comment_flags Creating table tagging_tag Creating table tagging_taggeditem Running deferred SQL... Traceback (most recent call last): File "manage.py", line 10, in execute_from_command_line(sys.argv) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/core/management/init.py", line 338, in execute_from_command_line utility.execute() File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/core/management/init.py", line 330, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/core/management/base.py", line 390, in run_from_argv self.execute(_args, *_cmd_options) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/core/management/base.py", line 441, in execute output = self.handle(_args, *_options) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 179, in handle created_models = self.sync_apps(connection, executor.loader.unmigrated_apps) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 317, in sync_apps cursor.execute(statement) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 79, in execute return super(CursorDebugWrapper, self).execute(sql, params) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/db/utils.py", line 97, in exit six.reraise(dj_exc_type, dj_exc_value, traceback) File "/home/datakid/.virtualenvs/df/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 62, in execute return self.cursor.execute(sql) django.db.utils.ProgrammingError: relation "django_content_type" does not exist

Hi,

I forked your project to add more django-cms plugins like search form, calendar, etc. This way I can add them to my cms in a more modular fashion, instead of having to integrate the whole toolbar..

This pull request adds a super simple plugin providing the search form.

Best regards Mauro

Bumps pillow from 7.0.0 to 9.3.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

What is the purpose of your pull request?

• [ ] Bug fix
• [x] New feature

Proposed changes

Warning

Before submitting a pull request make sure you have:

• [ ] Read the guidelines for contributing.
• [ ] Wrote some tests.
• [ ] Respected the PEP 8.

There are small typos in:

• docs/how-to/customize_look_and_feel.rst
• docs/how-to/rewriting_entry_url.rst
• docs/index.rst
• docs/notes/faq.rst
• zinnia/markups.py
• zinnia/models/entry.py
• zinnia/models_bases/entry.py
• zinnia/static/zinnia/admin/dashboard/js/masonry.pkgd.js
• zinnia/views/mixins/entry_protection.py

Fixes:

• Should read different rather than differents.
• Should read upon rather than uppon.
• Should read reimplementing rather than reimplemting.
• Should read optionally rather than optionnally.
• Should read multilingual rather than multiplingual.
• Should read initialized rather than initalized.
• Should read inheritance rather than inheritence.
• Should read implementing rather than implemeting.
• Should read implementation rather than implemention.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

This pull request brings this project up to date with the latest version of Django 4.0. Please go to DjangoBlogZinnia.com for documentation and other updates.

I just created a fork of this project and updated the code to work with modern versions of Django (including 4.0+).

Please visit https://github.com/arrobalytics/django-blog-zinnia if you want to contribute. Don't forget to star the project to show your support.

Visit the new site https://www.djangoblogzinnia.com for documentation, demo and other resources.