BUG: Activity Log - Camping days and nights are calculated incorrectly when entering

When adding Camping activity to a calendar event, the calculated days and nights that are entered in the entry fields by default are one less than the correct value.

For example, for a campout from 5pm Aug 21 to 12pm Aug 23, the default days is 2 and nights is 1. It should be 3 and 2, respectively.

@MichaelHoch - those days/nights are not a fixed amount. But I would consider it 2/2 as it is 5pm friday. The days/nights are a starting point.

I realize that they can be adjusted. However, I would bet slushie money that many leaders don’t pay attention when adding activity logging to events.

I can see your point about the partial days when arriving in the evening and leaving in the morning… but all of the camping activity requirements/criteria tend to use ‘camping nights’, so that’s what matters most.

This seems like an easy fix to a faulty calculation in the code. I’d hope this gets fixed quickly.

@MichaelHoch - in messing around with it I have found that if you start on Friday at 5pm and end sunday at 6pm it will give you the 3/2. So what ever time you set as the start the calendar will set the end time as +1 hour on that last day and that appears to let it default 3 days 2 nights.

You can also check the All Day Event box and not worry about the times

Additional method is to enter in via the activity log and link to the calendar which presents a blank slate for days/nights.

This seems like an incorrect way to calculate camping nights. It’s not hours/24, it’s end date - start date. You can be particular about calculating partial camping days, but the nights happened when they happened… not after 24 hours of the event.

I see that there is a related topic on this from 2025. Can’t believe this hasn’t been fixed by now.

@MichaelHoch - i do see that from 2025. I see that it was being check if there was a story for it. But do realize that we are all volunteers here and the development team is not on the forums. Looking at how many forum questions that come up I think it may have been missed.

@MichaelHoch - this has been reported. Please watch the change log for the fix.