Hyperkitty Archives - Sidebar years/months
Hello, I’m going through importing archives from mm2 to mm3. One of the lists I’ve imported has messages going back to 11/2013. I was able to successfully import the lists settings using:
mailman import21 lists@domain.com<mailto:lists@domain.com> /path/to/list/config.pck
This successfully imported lists owners, moderators, subscribers, & settings. I then imported the messages with the following command:
python /path/to/manage.py hyperkitty_import -l list@domain.com<mailto:list@domain.com> /path/to/list.mbox —since 10/01/2013
I used that date because it is older than the first message sent to the list: 11/13/2013
And followed that up with the update index command:
python /path/to/manage.py update_index_one_list list@domain.com<mailto:list@domain.com>
This successfully imported all the messages from 11/13/2013 through 09/30/2018. Here is where I’m facing two issues:
- Messages from October 2018 were not imported
- The sidebar only shows the year 2018.
Fdasfds If I modify the URL to go to https://my.domain.org/hyperkitty/list/list@domain.com/2013/11 the archived emails show up fine. October 2018 shows two test messages I’ve sent but not any of the messages from October 2018 that should have been imported. Is there something additional that needs to be done to show the previous years and months in the sidebar?
Thanks, Enrique
On 10/22/18 1:25 PM, Enrique Terrazas wrote:
If I modify the URL to go to https://my.domain.org/hyperkitty/list/list@domain.com/2013/11 the archived emails show up fine. October 2018 shows two test messages I’ve sent but not any of the messages from October 2018 that should have been imported. Is there something additional that needs to be done to show the previous years and months in the sidebar?
Are you running the periodic Django jobs? See <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required>
There have been and probably still are, depending on version, issues in this area. Many of these issues are fixed by the some of the Django periodic jobs
python /path/to/manage.py runjob xxx
where xxx is cache_cleanup daily_cleanup orphan_emails thread_order_depth and thread_starting_email.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you Mark I don't think the periodic Django jobs are running. I do see the cron job executing the jobs as scheduled but I am seeing errors being sent to /var/spool/mail/mailman (thats the user that runs the MM3 application) that say: /bin/sh: django-admin: command not found
If I run: django-admin --help
I get the following:
Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.).
I'm not sure how to go about correcting this. Thank you, Enrique
On 11/7/18 4:18 PM, Enrique Terrazas wrote:
Thank you Mark I don't think the periodic Django jobs are running. I do see the cron job executing the jobs as scheduled but I am seeing errors being sent to /var/spool/mail/mailman (thats the user that runs the MM3 application) that say: /bin/sh: django-admin: command not found
So whatever django-admin you are trying to run is not in the path of the cron job. Try an absolute path to django-admin instead.
If I run: django-admin --help
I get the following:
Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.).
I install Mailman in a virtualenv and the django-admin file I run contains
#!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@
The main things are the directory containing settings.py is /opt/mailman/mm and I export that as PYTHONPATH so my settings module can be found.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I am importing 25 years worth of archives from a list I am migrating. I seem to be able to get messages in from a converted Listserv archive format munged to a proper mbox format, and they turn up quite nicely in the all threads view. But with this many years of archives, it would be good to get the side bar panel to update. It does not at present.
How do I fix this?
Running the usual django-admin commands has no effect, but at least they don't fail.
Andrew
On Thu, Jun 20, 2019, at 3:52 AM, Andrew Bernard wrote:
I am importing 25 years worth of archives from a list I am migrating. I seem to be able to get messages in from a converted Listserv archive format munged to a proper mbox format, and they turn up quite nicely in the all threads view. But with this many years of archives, it would be good to get the side bar panel to update. It does not at present.
I don't exactly get what does do you mean by side bar panel to update?
Do you mean on the left or right?
What do you see and what do you expect to see?
How do I fix this?
Running the usual django-admin commands has no effect, but at least they don't fail.
Andrew
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
participants (4)
-
Abhilash Raj -
Andrew Bernard -
Enrique Terrazas -
Mark Sapiro