Joe Dolson

The default height of cells in the mini calendar is to fit the contents; you can apply custom styles to increase their height to a standard height using custom CSS. This is the default behavior of a table, so that’s why it happens with styles disabled.

This is actually a WordPress core issue; it’s being tracked on the WordPress core ticketing system. It’s scheduled for WordPress 6.7.1, which is currently expected for release on Thursday.

Looking at it right now, it appears to have the calendar displayed. Are you still not seeing it?

Those are coming from a style collision in ‘Spiffy Calendar’; both plugins use a class called weekend-heading, but don’t use it in the same way. If you need to continue using Spiffy Calendar, you can override those styles; but if not, it’ll be fixed just be disabling Spiffy Calendar.

Do you mean having them *only* show on mobile view? When switching to mobile view, the same navigation options should be visible as you see in the desktop view.

If you only want them visible on mobile, then you’d need to add some custom CSS to hide the category switching on larger viewports.

You certainly should be able to; but let me know if there are problems.

Looks like a style conflict in the twentytwenty My Calendar stylesheet; it’s setting the background color for dates outside of the current month to transparent, but the main styles are setting the color of dates with events to off-white.

You can adjust this by either disabling the twentytwenty stylesheet in the My Calendar design settings, or you can change the color & backgrounds for events with dates in the design settings, but it is a bug, and I should address it in the stylesheet.

Did you have any events that day? There’s nothing in the latest release that should change any shortcodes; the only changes were on the admin side.

Yes, I corrected an incorrectly named variable, but didn’t anticipate the fact that because a function now worked that hadn’t worked before, it would retroactively do a bunch of things it should have done long ago…

It will only happen once per ticket type, however, so by the time I’m able to get an update out, it may be irrelevant.

This should be resolved with today’s release.

I guess I’m going to close this issue as resolved, since it’s caused by an API limit change, and there’s really nothing I can do about it.

@rob006 Apparently they haven’t updated all of their documentation yet; thanks for sharing that. I guess it’s gone down – no real surprise. They really don’t want it to be useful at the free tier.

You shouldn’t need Pro for that; it’s doable with the [my_calendar_today] shortcode. That shortcode works basically the same way as the upcoming events, except it only shows events that are happening on the current day.

Thanks for reporting! Found the issue.

As of version 2.0.5, you can render an event’s location using either [ticket_venue] or by adding the ‘location’ attribute to [ticket].

See: https://github.com/joedolson/my-tickets/releases