GatherPress

Hi Travis, 0.31.0 was just released and this data is now available to you in the WordPress REST API. Thanks and let us know if you have anymore questions or issues.

Hi Travis,

The start and end datetimes are stored in a separate custom table. It was done this way to scale GatherPress on larger sites with lots of data since meta data isn’t indexed in the database. We have discussed and are planning on including the datetimes as meta data as well for the reason you are running in to, but haven’t started that work yet. In the mean time, you may be able to leverage this API endpoint on your website.

/wp-json/gatherpress/v1/event/events-list?event_list_type=upcoming&max_number=10

event_list_type can be either upcoming or past. max_number is just the max number of events to return.

I’m not sure this API endpoint has everything you need, but hopefully it helps. I’ll see if we can get the meta data work into 0.31.0. Thanks!

Hi Travis, I’m going to mark this issue resolved as it is known, is on our roadmap, and a temporary fix was provided. Thanks and let us know if you have any other issues for us to look into!

Hi Travis, so GatherPress is being explicit about those blocks at the moment, but this is a topic that is being discussed both on the GatherPress team and Gutenberg to make this easier for non-devs. Here are a few tickets to check out on the topic.

https://github.com/GatherPress/gatherpress/issues/528

https://github.com/GatherPress/gatherpress/issues/626

https://github.com/WordPress/gutenberg/issues/53396

For now, I would follow one of the steps I listed in my previous comment until we land on a good solution here. We’re very happy you are excited about GstherPress. Thank you again for your feedback, it really helps us prioritize and shape the plugin to the needs of the WordPress community. Have a great weekend!

Thank you, Travis. I think I wasn’t fully understanding the issue. This is about the template pre-populating blocks for the single event when you create a new event, is that correct? That area of the plugin is something we need to revisit. It was introduced a while back before FSE was even a thing (believe it or not, we started work on the plugin 4+ years ago). We wanted to make it easy for someone to create an event by pre-populating the blocks they’d probably need.

We haven’t fully landed on how we are going to change this. Right now you have 2 options.

• You can delete the blocks when you create a new event. Tedious but it’s the lo-tech solution until we release something addressing this.
• If you are comfortable with adding pre-written PHP code to your site. This bit of code will remove the block template from the single event post type:

<?php
add_filter( 'register_post_type_args', function( $args, $post_type ) {
	if ( 'gatherpress_event' === $post_type ) {
		$args['template'] = [];
	}

	return $args;
}, 10, 2);
?>

A plugin like Code Snippets will allow you to add this code to your site within the admin making it easier. Definitely test this on a test site before adding to production.

Hope this answers your question and thank you for being patient with us as we continue to progress with the plugin. Thanks! ??

Thank you for the kind words! We are excited that others are enjoying the plugin. Lots of great stuff to come. ??

Hi Travis,

Just saw your post with the video. It looks like you aren’t including a pattern for Single Item: Event template. If you select a pattern that should help you with starting things off because there is an important Content block that will display the content from the single event you will need for displaying that content. Then after applying the pattern to the template you can edit around the Content block to add things you’d like to be specifically on that template.

Keep in mind we are still making major updates to the plugin (we are still in an alpha at version 0.29.3), so FSE with the plugin will be a much better experience as we progress. It’s also good to have this plugin that we make available on GitHub. This plugin fixes any breaking changes we make as we continue to develop the plugin and release new versions. This GatherPress Alpha plugin will continue to be used until we hit 1.0.0. Thanks and let us know if you have any more questions.

Got it, thanks Travis!

So this may be more a Divi issue then? I’m curious, do you have the same issue with FSE templates with other custom post types from different plugins? I haven’t used Divi, so I’m not sure why it might be doing this. It might be worth putting in a ticket for Divi explaining your issue if you see a pattern with the sites having used Divi in the past. Let me know what you find out. Take care!

Hi Travis,

I installed your theme and set my GatherPress version to match yours. I put this Loom together showing that I’m creating a Single Item: Event template, save it, then load the single event and see the change I made. It worked as I would expect, but let me know if you are doing something different that I am not considering. If you’re able to create a video showing steps that could help as well. Thanks!

Hi Travis, I was able to reproduce, but the issue I saw was a relic from an older version of GatherPress before we made some changes to the post type naming. Just to help us debug for you, can you provide the query string in the URL when you are editing the Single Item: Event template. For example, mine looks like this with the Twenty Twenty-Four theme: wp-admin/site-editor.php?postId=twentytwentyfour%2F%2Fsingle-gatherpress_event&postType=wp_template&canvas=edit.

The issue I originally ran into was that the old post type for events was gp_event, but we changed it to gatherpress_event. I’m not sure how far back you started using GatherPress, so just want to ensure it’s not the same issue I just saw. After I deleted that template and created a new one, I was seeing the correct template applied to Event post type.

• This reply was modified 7 months ago by GatherPress.

Thanks for checking out GatherPress, Travis!

I was able to reproduce your issue in the Twenty Twenty-Four FSE theme as well, so we’ll look into the issue and get a fix out. Thank you for reporting the issue. ??