Welcome the Technical Support section. Help us in assisting you by providing us with a concise and descriptive elaboration of your issues. Be specific and if possible, provide us with a step-by-step instruction in replicating your problem.
As soon as the clock hits midnight on the day of an event, the event gets dropped from the "Upcoming Events" box in the Community. The only way I can see it is if I click on the event day in the calendar, and then it appears below it, in small font.
Is there a way an event can remain in that box until a specified time? Screenshot is attached to reference the upcoming events box.
I did change the "true" to "false" and an entire series of new events appeared in the Events box on the right side of the page. All I want to make sure is that the event stays in the main events section on the day it is occurring.
Screengrab to show the main events section is attached.
if that events still not ended yet. the events will stay on list with "ongoing" label on it. please provide me FTP and administrator access detail by editing your first post at this topic. put it under site info form. I need it for debugging purpose.
btw any reasons do you not want upgrade the jomsocial with latest one?
Sorry but I can't share FTP credentials as this site is hosted in a shared environment. I did upgrade to Jomsocial 3.2.1.5 and have implemented your change, however that did not do the trick. Rather it displayed ALL of my events on the right side.
I created a test event yesterday for today, and now that event is gone - how can I keep it visible until the event time is over?
I was able to get this working in the new version of Jomsocial. I specified the exact day and time of the event (provided it was the next day or any day therefafter) and changed the GMT time to US/Eastern. The event stayed in the box until it was over.
This issue seems to have come up again. We are running Jomsocial 3.2 and it appears that the event is not staying up on the day of the event - rather, it disappears. We had this issue in 3.1, which was fixed with the move to 3.2, but it's now happening again.