“Events List” Gutenberg block not displaying on mobile

This issue still exists. I also verified if I disable all other plugins except The Events Calendar as well as switch from the custom theme to a built-in one such as Twenty Twenty-Two, the same issue exists. I’m also not seeing any errors in the devtools console when testing in Safari. I can provide you a link to the site, but not publicly. Do you have a way to share this privately?

I just tried with the Twenty Twenty theme and have the same issue. If you click on the link below it will take you to a secure note where the link will be available that goes to our dev site which I currently have configured with the Twenty Twenty theme and all plugins disabled except The Events Calendar and our security plugins.

https://privnote.com/WjsGyE2z#tIx5FQ5Oz
^ This link will expire after 24 hours.

If I view the link on Chrome, I see the Upcoming Events listing appear at below the native “Sample Page” (immediately after the “Have fun!” text).

Note that we also have an Upcoming Events widget in the footer at the bottom of the page and that appears to be loading without issues, just not the one in the main content area.

However, if I view the site in Safari or on my iPhone I do not see the Upcoming Events widgets after “Have Fun!” and only see it at the bottom of the page in the footer area.

I just tested and saw the same result on the frontend that you saw, but this was definitely not the case when I tested in my previous message. Today when I checked the backend I was seeing the following errors when editing that page…

And in the DevTools Console there were these possibly related errors…

So I have deleted the Events List Gutenberg block and re-added and the “tribe-widget-events-list” error and the “rest_invalid_widget” errors went away (“core/legacy-widget” error remained). Of note, I ran into this in the past as well and couldn’t figure out why after adding the block it seemed fine, no error, and then at some unspecified point later on the block just stopped working without any cause that I could identify. The sample page I sent previous is now saved with the new block and reproducing the same error I originally reported if you want to try again.

I only had 2 security plugin installed along with the Events Calendar plugin. I have tested disabling the security plugins so the only plugin activated was The Events Calendar. However the issue persists. The site is also now updated to the latest version of WordPress (6.3.1) and The Events Calendar plugin (6.2.3).

In case it’s relevant, this site has been using the Events Calendar for a number of years now. Is it possible some legacy information in the database from old versions of the plugin could be causing this issue somehow? I’m grasping as straws here since it is a very odd bug I haven’t been able to track down yet.

• This reply was modified 2 years, 8 months ago by Fetch Designs. Reason: Added more details of which errors went away

I’ve debugged further and figured out the issue. Apparently the Events Calendar “Event List” Gutenberg block encodes the information in it using one of the Keys or Salts defined in the standard wp-config.php. Example of the encoded output of the block in the page content…

<!-- wp:tribe/events-list -->
<!-- wp:legacy-widget {"idBase":"tribe-widget-events-list","instance":{"encoded":"YTo2OntzOjU6InRpdGxlIjtzOjA6IiI7czo1OiJsaW1pdCI7czoxOiIzIjtzOjE4OiJub191cGNvbWluZ19ldmVudHMiO2I6MDtzOjIwOiJmZWF0dXJlZF9ldmVudHNfb25seSI7YjowO3M6MTM6Impzb25sZF9lbmFibGUiO2I6MTtzOjIwOiJ0cmliZV9pc19saXN0X3dpZGdldCI7YjowO30=","hash":"ca15e859235f5626beb4332fc1644c4d"}} /-->
<!-- /wp:tribe/events-list -->

However, this is problematic because we have our keys further secured by additionally salting them with more dynamic information including $_SERVER['HTTP_USER_AGENT'], $_SERVER['HTTP_HOST'] and date('F') which is why the block wasn’t working in a different browser and even after a period of time (the next month).

Is there a reason the block information here needs to be encoded? It seems unnecessary and we’ve never had issues with any other plugin with our method of additional salting of the keys.