[Laura Luttrell]

I think we’ve fixed this issue. It appears to have been an issue primarily with Advanced Custom Fields. I’m sure I couldn’t recreate the path by which the problem arose but recreating the missing fields in ACF restored the missing data entry fields populated with the existing data. I wouldn’t want to say for sure that this issue was 100% caused by ACF but it certainly appears to have primarily been an ACF issue.

For anyone else who might come across this thread, this old thread was part of the key to solving this problem: https://theeventscalendar.com/support/forums/topic/using-the-advance-custom-fields-plugin/

[Laura Luttrell]

Thanks. We had tribe-bar set to “false” but changing it to true does not resolve the problem. I did some more testing and figured out that our problem is specifically with the month view. If I shift to list view then the month heading (e.g., “August 2018″) shows up. For now I’ve turned off the tribe-bar false setting to eliminate that from the discussion. So, our complete shortcode is [tribe_events view=”month” date=”2018-08″]. You can see the results here http://rilandtrusts.org/landtrustdays/ (scroll down to the bottom of the page).

Thanks

[Laura Luttrell]

I found the solution. The default date was being set by the function function tribe_force_event_date
Bruce

[Laura Luttrell]

That worked. Thank you!

But as an FYI: If I put in “2016-08” (August last year) the calendar displays last year’s August events as it should but the heading above the calendar says “Events for August 2017.” This is not a problem for us, at least at this time, but it does appear to be a bug.

[Laura Luttrell]

I just uncovered another aspect of this issue. The code is working fine on the main calendar page. The issue arises when then calendar is displayed embedded in another page using the shortcode [tribe_events]. I confirmed that the problem still exists when using the twentyseventeen theme.

[Laura Luttrell]

Thanks Courtney. Unfortunately switching the default date setting to ‘2017-08’ does not fix the problem.

Bruce

[Laura Luttrell]

Note that where I said “The only change I made to the calendar was to replace ‘2015-10-01’ with ‘2017-08-01′” what I meant is that this is the only change I made to the code supplied on the page I linked to in my previous post.

[Author]

Posts