psheld

Same here following upgrade to 4.1

Clicking DFW made no difference. Then I tried aaemnnosttv’s suggestion: turned off ‘enable full-height editor’ and then switched back on. No change. Hmm.

So then tried turning off ‘enable full-height editor’, then refreshed the page, then turned it back on. Now clicking DFW takes the columns away either side of the editor, but not the stuff above. And moving the mouse over where the side columns used to be brings them straight back.

Finally, I understand what you’re both saying!..

Min feed start date – the start of when to start grabbing events (not necessarily displaying them)

Max feed end date – the time which to stop retrieving events

Start date offset – The offset of the start day to show relative to the current day.

So set the offset date for the feed looking back in time to 1200 days, and voila, it works. May I suggest a clearer description of the start date offset, at least in line with how I now understand it…

Start date offset – the day, relative to today, from which you wish to display events.

THANK YOU.

Upgraded to 2.1.5. No change.

Thanks again aparente001. I thought the same re. your comment about (gobbledygook)@group.calendar.google.com, and I did double check at the time. But the id is correct, as Google’s HTML rendering of the calendar confirms. (Select 1st Sept 2014 to see some events.)

Nick, thanks for your question. In fact, there are no future events currently… a function of this quieter time of year. It’ll kick off again in the New Year.

For the feed looking back in time you say the API is returning events (how do you know?), but somehow this isn’t then being displayed. You suggest changing the “Display Start Date Offset”, although I’m not following the rationale. Regardless, I changed it to 1 day back to no effect I’m afraid.

Aparente001, both feeds are included on the page in question, both resulting in “No events to display.” Just scroll down a bit.

I have no problem using the current page as a test page.

Thanks v much for taking a look at the screenshots. If you follow the owly links and then click the image, you’ll see them full size.

The difference between the two feeds is that one looks back and one looks forward.

And thanks for the hyperlink explaining how to find the calendar id… and that’s exactly what I did.

Thanks aparente001. I can create a test page of course, but what’s the test?

The URL hasn’t changed Nick, it’s still:

https://www.eulerpartners.com/events/

Thanks Nick. It’s odd that the updater plugin didn’t do the honors, but just updated manually to version 2.1.3.

I could then see the option to paste in the Google API key, which I did.

I then double checked everything and reduced the cache to 3 seconds for both feeds, and cleared the caches. But alas still getting “No events to display” for both.

I’m not a WP newbie, or a tech newbie come to that. Don’t know why I mention that as still likely PEBCAK. Thanks for your help here.

Screenshots: https://ow.ly/i/7IkK2 https://ow.ly/i/7IkK9 https://ow.ly/i/7IkKc https://ow.ly/i/7IkKi

Hi Nick,

Thanks for your question. No, still not working.

Min and max dates are set, one feed goes forward three years and back zero, and the other feed back three years and forward zero.

Yes I agree. When a plugin changes this much, there must be a way to flag it for immediate attention!

Anyway, thanks for your comment here. I already have “Number of Events per Page” set to 100 Events, and I have the Feed IDs correct, and my Google feed still validates.

But “No events to display” is still all I’m getting. Hmm.

Hmm. Completely deleted the old calendar events feeds and created two new ones from scratch. Same result. “No events to display.”

For the record…

Hover over Performance, then click Dashboard. Click empty all caches.

You’ll usually get a faster and more useful response by going where the plugin developer hangs out.

The site isn’t serving for me ??

And https://www.downforeveryoneorjustme.com confirms it isn’t just me.

It shows for me too. Phew! Perhaps you had a cached version of the blog homepage? Or perhaps you use a caching service such as Cloudflare?