Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
- This topic has 9 replies, 2 voices, and was last updated 8 years, 11 months ago by Gilbertmi.
06/24/2013 at 1:35 pm #263502Len JohnsonGuest
The latest update appears to have inserted a database error for birthdays. The upcoming birthday short code is now showing them one day off, and there are two birthday entries in each contact. Our admin doesn’t want birth years, and had changed the date to ‘9999’. The new entry is one day earlier and uses the current year instead of ‘9999’ for the new entry.06/24/2013 at 9:43 pm #263548
The database is fine, I believe this issue is related to a timezone issue as I can not replicate it. I’m certain this issue popped up because the dates can now be properly internationalized.
Another user resolved the issue by manually setting the timezone with this function: date_default_timezone_set
They’ve kindly given me access to the server and site so I can debug this.
As for putting the date in as 9999 … the upcoming list calculates the next date, not the actual date. For example lets say a persons birthday occurs in April, since it is now June, the birthday will show up as the date in April 2014. Conversely, if the person’s birthday is in July, it will show up with a 2013 date in July.07/02/2013 at 10:43 am #264078Len JohnsonGuest
Thanks Steve. I took a look at the connections_data table and I see what you mean about the DB. Regarding the date, I was talking about the ‘manage’ area of Connections management. You see two birthdate entries for any user you choose, one the 9999 (or whatever you entered when creating the entry originally) and a second birthdate preceding it with the upcoming birthdate (as you describe) which we can’t get rid of. There are two such entries for every user. This was like the problem we had earlier which you fixed for us.
I don’t believe I killed the access I gave you before. If you want to get in and don’t have it, I’d send it to you by email.
I’m not sure what the function you referenced does for me- the timezone is selected in WP settings, and it appears to be correct. Are there timezone settings I should place elsewhere? (I haven’t done much coding in years, and never in php.)07/02/2013 at 11:56 am #264082
I think I solved the issue with the birthdates. I’m converting the time to GMT which, I think, was throwing off the timezone offset. Working with dates and timezones is annoyingly difficult, especially when you throw in internationalization into the mix.
If you’d like, send me the temp WordPress admin account and I’ll take a look…
One thing that still does not make sense is the double date. I’d have to see that.07/05/2013 at 4:45 pm #264364Len JohnsonGuest
You should receive an admin user acct at the help desk email addr.07/06/2013 at 9:40 pm #264402
Ok, I think I narrowed the issue down and made a hotfix to your site. Can you check to make sure the dates are correct? Also, I did edit the dates in testing for both Donna A. and Connie B. I think I’m certain I get used to correct date, but I suggest double checking me.07/15/2013 at 4:37 pm #264879Stewart SavageGuest
I am having the same problem except that some of my entries have double birthdays and others do not. I found that the entries I imported into Connections display only a single birthday. However, as soon as an entry is modified in some manner and updated, two birthdays are displayed in the entries.07/16/2013 at 4:22 pm #264934
The update, 0.7.8, I will be releasing in the next couple day should address this. Please let me know if it does not.07/17/2013 at 2:30 am #264960Len JohnsonGuest
IT looks good Steve– I’ll put the update in and let you know how that looks. Thanks!10/11/2014 at 7:29 pm #306859GilbertmiGuestThis reply has been marked as private.
You cannot reply to this support topic. Please open your own support topic.