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.
Use the Community Sharing forum for sharing Photos, Trips, Stories, etc.
Setup your Forum photo and profile here.
Jeff:
I'm unable to update Birder's Diary using the "Internet: Check for a program update" feature in the Help folder. When I choose this, I get the Check for Updates! pop-up window, and I click the OK button to proceed with the update. The Backup Data? pop-up window opens, and I select the NO button. Then the Check for Updates to Birder's Diary 6.0 window opens and I click the NEXT button. At that point, I get an error message (see attached screen shot).
If I press on the WEB PAGE button, it sends me to the Birder's Diary homepage, where I can navigate to the Downloads page, Forums, etc. I manually downloaded v44 and ran it (I was using v 43). It updated successfully, but still has the same Update Error when I run it. At this point, I think it should tell me that have the newest version, but I don't get that... just the same sequence I've already described. Please advise.
Hi Neill,
With a quick test, I also have the same issue.
Just heading out the door now. Back in a few hours and will troubleshoot then.
For the meantime, you did the right thing by going straight to the Downloads page.
fyi
Update: something has changed on my site server and I still haven't figured out what the problem is. Still working on it.
In the meantime, please update by going to the Downloads page. fyi
This problem is now resolved. Here is the text from my site provider.
The issue is related to a recently introduced security rule on our servers - the reason is that files with such extensions are usually not accessed directly via a web browser and doing so may indicate malicious activity. The security rule was added in order to block this type of request, thus improving the security of the websites on our servers.
Please note that you don't have control over the addition, removal, disabling, and enabling of these security rules, as they are part of our managed hosting infrastructure.
I disabled this security rule for your site and you should be able to access the file. Make sure to flush your browser's cache beforehand.
Jeff:
Nope, it still doesn't work. Same sequence, same results.
I wasn't sure if the note meant that you needed to flush your browser's cache or if each individual user does. I did flush mine...completely. I also did a cold start and still, same error message.
Does yours work now?
Ah - correct. It still fails from the update program. It was testing the failed file retrieval without the update program.
After much more testing, I now find that another change my provider made to my server configuration is that it no longer recognizes 'BirdersDiary.com' as valid. Only lower case - 'birdersdiary.com'. Which is not correct. RFC standards indicate that domain names are case-insensitive.
I am working with them to return my server to former functionality.
Stand by.
Update from host provider on this matter:
Thank you for the update.
I was able to replicate the issue and it seems to be related to the security rule discussed in ticket 4464570. While the rule no longer matches birdersdiary.com, it seems to match any other case combination of the domain.
I've reported this to our developers and we'll update the ticket once more information is available on the matter.
In the meantime, your patience is greatly appreciated.
Hi,
Well, my host provider is dragging their feet on this.
I have made changes in Build 45 and forward to work around these issues.
SOLUTION
The solution is to upgrade to the latest version (Build 45 or later now) of BD from the Downloads page. From Build 45 and later, once installed, the "Check for program update" feature will now work correctly.
Closing this ticket now.
Jeff:
I manually updated to 45 and then tried the update button. It correctly informed me that I was running the latest update, so thanks.
BTW the last message was not from me. I was being patient! 😆 😆
