Joe Dolson

The main shortcode (everything using [my_calendar]) is a time-based shortcode. So it’ll always show a period of time. You can limit it to a week to cut down on the number of events, but it doesn’t have options for showing a fixed number of events.

I suggest using something like Query Monitor to see what calls are being made heavily on that page. My Calendar itself doesn’t generally make a particularly high number of calls under normal operation, so I don’t have any immediate suggestions. However, if there are plugins adding actions to post content, that can potentially increase the load fairly significantly.

Another thing is that if all your calendar page loads are hitting the same page, then you’ll have a very high number of hits against that URL. Since you’re not using pretty permalinks (My Calendar > Settings > General), every My Calendar load is going to be on that URL. If you enable pretty permalinks, some of those loads will end up elsewhere. This might help give you better data about how your site is using processes.

Yep. Undefined element; will be fixed in the next release.

This is coming from your theme – it’s kind of a weird block of code, and I’m not sure what purpose it’s intended to serve. But the last block of JS in view-source:https://www.roamingshores.org/RRA1/wp-content/themes/RRA2016/script.js?ver=92544e3e743d7d16c3a8ff4ff6ca969c is inserting a link with no content after every header element. The link is absolutely positioned and sized to cover it’s parent, so it’s preventing the My Calendar buttons from being clicked.

This was introduced in the recent update, because before that My Calendar didn’t wrap events in article elements; but it’s really pretty bad code in the theme, because it’s applying to *every* header element, rather than targeting any specific cases.

It looks like it might be tied to a setting about making the header clickable, so you may be able to turn that off in the theme.

Same as https://wordpress.org/support/topic/calendar-listing-info-not-displaying/; will be fixed in next release.

In some quick testing, the code editor encodes comment characters if it doesn’t find both the start and end comment, but not if it does. That may be a change in the code editor itself, and not in the plugin; not sure. But probably makes more sense to remove commented code, anyway.

The design view uses settings options for display; the public view uses whatever options are configured for your page specifically. Do you have limits set in the shortcode or in the page settings for your calendar?