Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
sound Posted May 1, 2018 Posted May 1, 2018 Hi all There seems to be on my sites and others an issue with non-summer time dates in the week view and day view both in the past and future I reported this issue regarding v4,3 calendar via ticket about 5 days ago Despite passing on real world examples of this from owna nd other 4.3 invision sites I have had no joy with support in getting this resolved Can anyone who is running 4.3 and calendars help try and get this resolved by going to the url on their site as below insertyoursitehere/calendar/2018/3/1/ and confirm that they do see 28 Mar as the day displayed instead of 1st March ? that at least will either confirm that there may be an issue beyond the 4 (2 not mine) sites I have tested thanks
sound Posted May 2, 2018 Author Posted May 2, 2018 bug report simplified invision calendar 4,3,1 displays 01 Jan 2019 as falling on a Wednesday when it falls on a Tuesday example using ehrens public demo site https://ipsfocus.net/4x/index.php?/calendar/1-community-calendar/week/2018-12-31/ to temporary fix replace 4.3.1 applications/calendar/sources/sources/date/date.php with the 4.29 version 01 Jan 2019 then displays as falling on the correct day a Tuesday!
Nathan Explosion Posted May 2, 2018 Posted May 2, 2018 Go back to support and tell them to test it - that is way to easy to reproduce. Actually....send them this link from their own demo and ask them to then navigate backwards to March 25th, and wish them luck. http://c114615.try.invisionpower.com/calendar/1-community-calendar/2018/3/26
Rob ter Linden Posted May 14, 2018 Posted May 14, 2018 I am having the same issues. The date is on the wrong day ? Also filled out a support ticket, I am on the cloud instance so I am not able te place the php so easily. Another thing I noticed is when going to the calender on my website is shows last week instead of this week... Things seems to be messed up.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.