cmkl

Screencast is here: https://drive.google.com/file/d/1teit71CeFATgVwui9P8o8gkPcMYQiBqM/view?usp=sharing

I have not modified the plugin.

cmkl

Hi John.

Thanks for the reply.

I’ve put a screenshot of the calendar’sadvanced tab here:

https://drive.google.com/file/d/1y7PBZB0wiE30hNm6LK8uBBrth5yPY84f/view?usp=sharing

cmkl

The month view calendar displays as expected when it’s not in a tab.

I tried a couple of different plugin suites (Kadence and Spectra) and the calendar events do not display expanded in either. What’s more clicking on the dots or the day square does not expand the dots or show anything.

The month view calendar is also broken when placed inside the ‘accordion’ block of the Kadence block suite.

So if the conflict is between Simple Calendar and multiple block plugins, who’s supposed to fix that?

Thanks Chouby. That worked.

cmkl

Hi Rohit. It’s nice to see this plugin has some legs under it. It’s especially good because so many of the other calendar plugins have become these huge bloated things that do way more (and cost way more) than I need.

The gridview shortcode is the same for mobile, desktop and tablet.

Is the best thing to do to create different shortcodes for desktop, mobile and tablet?

If so, what settings do I use for the gridview shortcode to force the events to display on load without the user having to resize their browser window?

That’s extremely helpful. Thank you so much. I will take it up with the Qubely people.

cmkl

So the problem seems to be that when you limit the length of the description field, you run the risk of cutting off the close tags for HTML formatted content or indeed even anchor tags for hyperlinks.

The only way I’ve found to get it to work consistently is to run with no limit to the length of the description, html=”no” and autolink=”yes”.

This way at least viewers get the hyperlinks, the page looks reasonably clean. The downside is that people can be pretty wordy in their descriptions and there’s nothing I can do about that.

Well the update that you rolled out in the last few days gets past the page with the external URL redirect when generating Critical CSS. The progress bar gets all the way over to the very end but then I see a red notice appear with:

An error occurred while sending Critical CSS generation results to the server: Unexpected end of JSON input

I can dismiss the notice, but I still see the ‘Generating Critical CSS’ notice above the progress bar and I get warned that Jetpack Boost is still generating critical CSS and I shouldn’t navigate away from the page.

So… progress, sort of.

I believe it’s in the theme, which is a child theme of Astra, aka https://wpastra.com/

(I put the site into troubleshooting mode and with only Jetpack Boost enabled, the Critical CSS function works. When I switch from Twenty Twenty to the site’s theme, it chokes on the same URL.

I would like to take this up with the theme developers. It’s great to have a single URL to use as a starting point for troubleshooting, but is there any way to know what Jetpack Boost is choking on? What content it’s ‘failing to fetch’.

Where can I find any more detail about the error?

This is awesome. Thank you so much.

It is. I assigned that class to the mobile-only Gutenslider block in the block editor for that page so that I would have something in my child theme’s style.css that would be unique and allow me to override declarations as necessary.

Regrettably, the site is behind httpd auth right now as it’s in development. I can give you the credentials if there’s a way to send them privately.

But yes, it seems like the problem viewport widths are in the 600px range. I was first able to reproduce the problem using the ‘iPad vertical’ setting in Chrome’s dev tools, which Chrome tells me is 724 x 1024. Don’t know if that’s device pixels or viewport. Similarly, Chrome’s “Surface Duo” landscape setting (720 x 540) shows the problem, whereas its vertical setting shows only the mobile video.

I put this query in my child theme’s style.css to hide the mobile video on midrange tablets:

@media screen 
  and (max-width: 1024px) 
  and (min-width: 600px) 
{
div.included-mobile-slider {display: none !important}
}

…and that seems to do the trick, but it would be better if the Gutenslider UI worked as expected.

cmkl

Yes! Thank you! Such a relief. I appreciate the fast action enormously.

Thank you so much! This makes creating and arranging block patterns significantly easier.

Yes. The circumstances of the reported problem certainly resemble what you describe. Do you happen to know if I can revise my rating. You deserve at least another star for the support.