After upgraded to 2.02. Start date & end date disappeared
  • Stranger
    Posts: 10
    Topics: 4
    Terrance December 9, 2011 Answered ✔ Closed ✘

    Hi,

    After I have upgraded both The event calendar & ECP to 2.02. The start date and end date disappear.

    Thanks.

  • Gatekeeper
    Posts: 3563
    Topics: 62
    Answers: 393
    Rob La Gatta December 12, 2011

    Hey Terrance – that shouldn’t be happening. Where are you seeing it? Single view, list view, grid view, etc? Can you share an example?

  • Stranger
    Posts: 10
    Topics: 4
    Terrance December 12, 2011

    Hi Rob,

    Thanks for getting back. It’s in both the Event list view and Single event view.

    Here is the example: http://www.runsociety.com/calendar/upcoming/.

    I have deleted away both The Event Calendar and ECP and install again, but the start date and end date still is not showing.

    Thanks in advance.

  • Power User
    Posts: 44
    Topics: 12
    Julien December 13, 2011

    Same problem for me !

  • Gatekeeper
    Posts: 3563
    Topics: 62
    Answers: 393
    Rob La Gatta December 13, 2011

    Thanks, guys. This sounds to be a bug in 2.0.2 – I’m unable to recreate it on my default 2011 install, but a few OS users have also brought it up. We’ve got a fix in the works for 2.1, and I’m going to have Jonah respond directly in here to see if there’s a short-term solution you can use until the fix is deployed.

  • Truth Seeker
    Posts: 23

    Answers: 4
    Nick Ciske December 13, 2011

    Can we get some info on the themes you’re using (for those getting the error)? If there’s a common thread there it might point to the issue.

    From what I can see, it’s probably something related to the $post object getting unset (or set to a non-event) somewhere in the page template before tribe_get_start_date() is called.

  • Tribal Help
    Posts: 3459

    Answers: 649
    Jonah West December 13, 2011

    Are you guys overriding the events list.php template file or using the default? Might help to get ftp / wp admin access from one of you to take a look at the code and see what’s there. You can email access to jonahcoyote [at] gmail [dot] com

    Thanks,
    Jonah

  • Truth Seeker
    Posts: 23

    Answers: 4
    Nick Ciske December 13, 2011 Answer ✔

    Confirmed as a bug that crept into Events 2.0.2. Fix to be released shortly.

  • Stranger
    Posts: 10
    Topics: 4
    Terrance December 13, 2011

    Thanks. Looking forward to it.

  • Gatekeeper
    Posts: 3563
    Topics: 62
    Answers: 393
    Rob La Gatta December 13, 2011

    Terrance: it’ll be a 2.0.3 release, hopefully no later than mid-to-late next week. We’ll keep you posted.

  • Truth Seeker
    Posts: 27
    Topics: 2
    Seth December 15, 2011

    I’m also in need of a (hopefully quick) fix to tribe_get_start_date() for reoccurring events. I see in the comments that it’s a known issue already.

  • Truth Seeker
    Posts: 23

    Answers: 4
    Nick Ciske December 15, 2011

    Here’s a patch you can use until 2.0.3 is released:

    http://tri.be/patch-for-the-events-calendar-2-0-2-date-bug/

  • Truth Seeker
    Posts: 27
    Topics: 2
    Seth December 15, 2011

    Well that solved one issue, the dates show up now which is good. However it is showing the date the reoccurring series originally started rather than this specific event’s start time.

  • Truth Seeker
    Posts: 23

    Answers: 4
    Nick Ciske December 15, 2011

    And that wasn’t the case previously (e.g. in 2.0)?

  • Truth Seeker
    Posts: 27
    Topics: 2
    Seth December 15, 2011

    It didn’t work in 2.0 either.

    The documentation right before the function tribe_get_start_date() mentions that the function does not work with a post ID for reoccurring events.

  • Truth Seeker
    Posts: 23

    Answers: 4
    Nick Ciske December 15, 2011

    If you want a version that supports recurring events, the feature request forum would be the place to note that so it can get on the roadmap for a future release.

    • Viewing 16 posts - 1 through 16 (of 16 total)
Sign in to add a Comment

This topic is closed