Cinnamon Hummingbird

Welcome to the Birder's Diary Forum for Support And General Questions

Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
Setup your Forum photo and profile here.

Trip Date Range err...
 
Notifications
Clear all

[Solved] Trip Date Range error

6 Posts
2 Users
1 Likes
24 Views
Posts: 13
Topic starter
(@rewebster)
Active Member
Joined: 2 years ago

Hi Jeff et al.:

Recently, on creating a Trip in the desktop version, and then entering sightings with the name of the trip entered, when I try to submit sightings, I get a "Date of Sighting is Outside of Trip Date Range" error.  Well, on the sightings page, I have 07/30/2022 and in the trip dialogue box I have modified the 03-July-2022 that is there to be 30-July-2022, so I don't see an error; this has happened on several different dates, so it is not just 30 July.  I have entered the range of hours on the Trip dialogue, but I have not checked the hour box on the sightings page next to the 07/30/2022. 

I can get around this by not putting the trip name into the sightings page when I enter the sightings and then pull up the sightings I have entered for that date and place, select all, and modify to add the trip as I have named it, and everything works, but that is cumbersome and not what I think you wish to have happening.

 

Thanks,

Richard 

Reply
5 Replies
Jeff
Posts: 550
 Jeff
Admin
(@jeff)
Creator & Technical Support
Joined: 2 years ago

Hi Richard,

Thanks for posting and for all the details.

It seems as though some recent changes I made to support new functionality has had some far-reaching issues. Sorry about these.

One thing. What version are you running? Are you at v5.3.25?

As I understand this from your post, I cannot recreate the problem.

I enter a trip as shown...

image

Is that about what you have?

Then I enter a sighting attached to that trip as such...

image

It works without any problem.

Let me know if you are doing this differently.

It may be that I have fixed this already per some other posts about similar issues. 

Reply
Posts: 13
Topic starter
(@rewebster)
Active Member
Joined: 2 years ago

Hi Jeff:

What you did is pretty close to what I did, except I was using Checklist, not Keyboard, entry.  I just tried adding another species by Checklist entry, and I got the same error message again.  I then tried adding the same species by using Keyboard Entry, and it worked for the first time, using the same trip, date, etc.  Could the problem lie in that difference?

 

Richard 

Reply
Posts: 13
Topic starter
(@rewebster)
Active Member
Joined: 2 years ago

Jeff, sorry, I should have added that yes, I am using 5.3.25 and have been throughout this issue. 

Reply
Jeff
Posts: 550
 Jeff
Admin
(@jeff)
Creator & Technical Support
Joined: 2 years ago

Hi Richard,

It still works for me in Checklist mode. With the same trip I created above in my previous post, adding the sighting below has no problems.

image

I notice now that you said...

Posted by: @rewebster

I have entered the range of hours on the Trip dialogue, but I have not checked the hour box on the sightings page next to the 07/30/2022. 

So I set a start/end time for this trip now.

image

Now if I try to enter the sighting without specifying a time between 9am and 10am, it fails. As it should.

By default, no time means all day for Trip start/end dates.

Also, by default, a sighting with no time defaults to midnight on that date: "00:00:00". Which, of course, falls outside of 9am to 10am.

So, you can either remove the Time portion from the Trip start/end dates, or add a time to your sighting that falls between those times.

Make sense?

Reply
Posts: 13
Topic starter
(@rewebster)
Active Member
Joined: 2 years ago

Hi Jeff:

Yes, it makes sense.  Thank you for taking the time to look into it and explain it.  I can now see a way to navigate through your program (and forces outside of it, like cell phones that take their time signals for apps from towers across the state and international borders near me!).  Again, thanks,

Richard 

Reply
Share: