Upgrade - no calendar

[bradrice]

I tried upgrading our website with the new calendar. All of my events disapeared and I don't have any css. I'm trying to figure out what went wrong. Here is the calendar:

https://lafayetteumc.com/calendar/

I had a previous version installed. Those events are still in the backend, but nothing is showing on the website. This is how I installed:

3. Run pip install --upgrade --upgrade-strategy eager -r requirements.txt
4. Run ./manage.py migrate
5. Run ./manage.py collectstatic --no-input
6. Add any desired settings. For maximum consistency consider adding the following settings: JOYOUS_THEME_CSS = "/static/joyous/css/joyous_coast_theme.css" JOYOUS_DATE_FORMAT = "l jS \o\f F X" JOYOUS_DATE_SHORT_FORMAT = "j F Y" JOYOUS_TIME_FORMAT = "fq"

[linuxsoftware]

Hi Brad,

Have you also restarted Django? (I.e. restarted uwsgi or whichever application server is running Django).

If that doesn't help: Are you getting errors reported to your ADMINS email address? (Or could you try running with DEBUG=True just long enough to get a stack trace.) Could you share that? You can email the stack trace to djm @ linuxsoftware.nz if you don't wish to post it publically.

Also, you will need to change the setting JOYOUS_THEME_CSS to match how your static files have their own subdomain, so set JOYOUS_THEME_CSS = "//static.lafayetteumc.com/joyous/css/joyous_coast_theme.css". This style sheet is not even being included yet, but we may as well get it correct for when it is.

Nice website! I am Methodist too.

Best wishes, David.

[bradrice]

OK, I fixed the path to the css. I added DEBUG=True but it isn't throwing a stack trace error. One thing, my wagtail screens look different.

This is what I see for adding calendar events.

[image: image.png]

On Fri, Mar 20, 2020 at 5:18 PM David Moore notifications@github.com wrote:

Hi Brad,

Have you also restarted Django? (I.e. restarted uwsgi or whichever application server is running Django).

If that doesn't help: Are you getting errors reported to your ADMINS email address? (Or could you try running with DEBUG=True just long enough to get a stack trace.) Could you share that? You can email the stack trace to djm @ linuxsoftware.nz if you don't wish to post it publically.

Also, you will need to change the setting JOYOUS_THEME_CSS to match how your static files have their own subdomain, so set JOYOUS_THEME_CSS = "// static.lafayetteumc.com/joyous/css/joyous_coast_theme.css". This style sheet is not even being included yet, but we may as well get it correct for when it is.

Nice website! I am Methodist too.

Best wishes, David.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/linuxsoftware/ls.joyous/issues/29#issuecomment-601914980, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACCPYFPMTFOHOVNJZ3A2DTRIPMTBANCNFSM4LQT6KTA .

-- Brad Rice bradrice1@gmail.com

[linuxsoftware]

Hi Brad,

That image didn't come through.

BUT, I see at https://github.com/bradrice/lmc/tree/master/lmc/templates/joyous that you are overriding calendar_base.html, calendar_list_upcoming.html, event_base.html, and group_page.html. This is what I think is causing you trouble. Those templates have changed substantially since 0.8.3.

I see the goal was to add the class "joyous-calendar-content" to the content div so you can add extra padding. The simplest thing would be to take new copies of the templates and add that class again. Or maybe you can apply the padding in another way, (e.g. the joy-cal class might do, although it only applies to the calendar itself, not the title and intro.).

Hope this helps, David.

[linuxsoftware]

I'd be happy to add a joy-content class to Joyous, but you would have to wait for a couple of days for a 1.0.1 release.

[bradrice]

David, you are awesome. I forgot that I had over-ridden templates. I'm wondering now that I have it running. Is 1.0 only for django 3? I haven't moved to django 3 on that site yet. I would like to be running the most current joyous and stay current.

[linuxsoftware]

You are welcome.

No, 1.0 will work with earlier versions of Django. It definitely works with Django 2.2. Let me know if you have a problem with any earlier version too. Wagtail needs to be at least version 2.0 and Python needs to be at least Python 3.0.