mpearrow's profile - activity
2016-06-15 06:10:04 -0500 | received badge | Nice Question (source) |
2016-06-03 08:06:00 -0500 | received badge | Notable Question (source) |
2016-04-23 13:40:11 -0500 | received badge | Popular Question (source) |
2016-03-18 13:58:40 -0500 | received badge | Student (source) |
2016-03-18 13:23:39 -0500 | received badge | Editor ( source ) |
2016-03-18 13:13:37 -0500 | answered a question | Why do I need to run fix_revisionless_posts frequently? I can re-create this error consistently by pasting the following into the body of the question and submitting: |
2016-03-18 13:12:31 -0500 | commented question | Why do I need to run fix_revisionless_posts frequently? A bit more information: here is the stack trace from the error (had to paste in an "answer" instead of a comment) |
2016-03-18 13:09:38 -0500 | received badge | Famous Question (source) |
2016-03-09 07:23:07 -0500 | commented question | Why do I need to run fix_revisionless_posts frequently? Django 1.8.10 and django.db.backends.postgresql_psycopg2 for database. |
2016-03-09 04:36:29 -0500 | asked a question | Why do I need to run fix_revisionless_posts frequently? We have recently set up an Askbot instance, which mostly works well, but frequently some questions appear to become corrupted, and I have to run manage.py fix_revisionless_posts to make that question work again. Here is the output from running that command. I’m glad to provide whatever info you need to debug further. root@help:/home/help# python manage.py fix_revisionless_posts WARNING!!! You are using a 'locmem' (local memory) caching backend, which is OK for a low volume site running on a single-process server. For a multi-process configuration it is neccessary to have a production cache system, such as redis or memcached. With local memory caching and multi-process setup you might intermittently see outdated content on your site. System check identified some issues: WARNINGS: django_authopenid.UserPasswordQueue.user: (fields.W342) Setting unique=True on a ForeignKey has the same effect as using a OneToOneField. HINT: ForeignKey(unique=True) is usually better served by a OneToOneField. group_messaging.SenderList.recipient: (fields.W342) Setting unique=True on a ForeignKey has the same effect as using a OneToOneField. HINT: ForeignKey(unique=True) is usually better served by a OneToOneField. have 1 corrupted posts |