{"id":1962825,"date":"2024-09-12T10:01:08","date_gmt":"2024-09-12T14:01:08","guid":{"rendered":"https:\/\/theeventscalendar.com\/knowledgebase\/?p=1962825"},"modified":"2026-04-23T13:56:10","modified_gmt":"2026-04-23T17:56:10","slug":"customize-event-admin","status":"publish","type":"post","link":"https:\/\/theeventscalendar.com\/knowledgebase\/customize-event-admin\/","title":{"rendered":"Customizing the Event Admin"},"content":{"rendered":"\n<p>The Events Calendar adds various touches to the WordPress admin \u2014 menus, editor defaults, notices, and list views. You may want to adjust those touches to better fit how you work. This article collects admin-side customizations for The Events Calendar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-hiding-admin-ui-elements\">Hiding Admin UI Elements<\/h2>\n\n\n\n<p>The two customizations in this section are defined as constants in your WordPress installation&#8217;s <a href=\"https:\/\/codex.wordpress.org\/Editing_wp-config.php\"><code>wp-config.php<\/code><\/a> file, which is located at the root of your WordPress installation. Place each <code>define()<\/code> line above the line that reads <code>\/* That's all, stop editing! Happy publishing. *\/<\/code>, alongside any other <code>define<\/code> statements already in the file.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-remove-events-from-the-wordpress-admin-bar\">Remove Events from the WordPress Admin Bar<\/h3>\n\n\n\n<p>The Events Calendar adds a dropdown to the WordPress admin bar, giving you a quick way to manage events, settings, and your calendar from any page once logged in.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2014\/10\/kb-remove_events_admin_bar.jpg\" alt=\"The Events Menu in the WP Admin Bar\"\/><\/figure>\n\n\n\n<p>If you&#8217;d rather keep the admin bar uncluttered, this constant removes the dropdown:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/** Removes Events from WP Admin Bar *\/\ndefine( 'TRIBE_DISABLE_TOOLBAR_ITEMS', true );<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-remove-upsell-notices\">Remove Upsell Notices<\/h3>\n\n\n\n<p>After installing The Events Calendar, you may notice messages in your WordPress admin encouraging you to purchase add-ons or install Event Tickets. These are intended to help you get more out of the plugin, but we understand they can feel like they&#8217;re getting in the way.<\/p>\n\n\n\n<p>These notices appear in several places:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Settings page<\/strong> \u2014 a banner visible when you visit <strong>Events \u2192 Settings<\/strong>.<\/li>\n\n\n\n<li><strong>Admin Dashboard<\/strong> \u2014 a banner that appears at the top of the WordPress admin dashboard.<\/li>\n\n\n\n<li><strong>Event editing screen (Classic Editor)<\/strong> \u2014 an &#8220;Additional Functionality&#8221; section near the bottom of the event editor, below the Event Cost section.<\/li>\n\n\n\n<li><strong>Event editing screen (Block Editor)<\/strong> \u2014 a &#8220;Turbocharge your events&#8221; section in the event date picker dropdown.<\/li>\n\n\n\n<li><strong>Event Tickets one-click install notice<\/strong> \u2014 visible to users who have The Events Calendar but not Event Tickets installed.<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2019\/10\/Screen-Shot-2022-11-30-at-11.57.40-AM.png\" alt=\"The add-on upsell banner at the top of the Events Settings page\"\/><figcaption class=\"wp-element-caption\">The upsell banner at the top of the Events Settings page.<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2019\/10\/dashboard-upsell-banner-1024x272.png\" alt=\"The add-on upsell banner at the top of the WordPress admin dashboard\"\/><figcaption class=\"wp-element-caption\">The upsell banner at the top of the WordPress admin dashboard.<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2021\/06\/Screen-Shot-2021-06-07-at-11.45.49-AM-1024x221.png\" alt=\"The Turbocharge your events upsell section in the Block Editor event date dropdown\"\/><figcaption class=\"wp-element-caption\">The &#8220;Turbocharge your events&#8221; upsell in the Block Editor date dropdown.<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2023\/05\/oneclicktickets.png\" alt=\"The Event Tickets one-click install notice in the WordPress admin\"\/><figcaption class=\"wp-element-caption\">The Event Tickets one-click install notice.<\/figcaption><\/figure>\n\n\n\n<p>One line of code removes all of the above messages at once:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>define( 'TRIBE_HIDE_UPSELL', true );<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-customizing-admin-behavior\">Customizing Admin Behavior<\/h2>\n\n\n\n<p>The three customizations below are PHP snippets that hook into The Events Calendar&#8217;s filters and actions. Add them to your child theme&#8217;s <code>functions.php<\/code> file or use the Code Snippets plugin. If code snippets are new to you, start with <a href=\"https:\/\/theeventscalendar.com\/knowledgebase\/code-snippets\/\">Using Code Snippets to Customize The Events Calendar<\/a> for a walkthrough.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-add-an-event-status-column-to-the-events-list\">Add an Event Status Column to the Events List<\/h3>\n\n\n\n<p>On the <strong>Events \u2192 All Events<\/strong> screen, the Event Status (Scheduled, Canceled, Postponed, etc.) is not displayed by default. This snippet adds an &#8220;Event Status&#8221; column to that list and makes it sortable.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>if ( class_exists( 'Tribe__Events__Main' ) ) {\n    add_filter( 'manage_tribe_events_posts_columns', 'custom_tec_statuses_columns' );\n    function custom_tec_statuses_columns( $columns ) {\n       $columns&#91;'tribe-events-status'] = __( 'Event Status' );\n\n       return $columns;\n    }\n\n    add_action( 'manage_tribe_events_posts_custom_column', 'custom_tec_statuses_column', 10, 2 );\n    function custom_tec_statuses_column( $column, $post_id ) {\n       if ( 'tribe-events-status' === $column ) {\n          $event_status         = get_post_meta( $post_id, '_tribe_events_status', true ) ?: 'Scheduled';\n          $cleaned_event_status = ucwords( str_replace( '-', ' ', $event_status ) );\n          echo $cleaned_event_status;\n       }\n    }\n\n    add_filter( 'manage_edit-tribe_events_sortable_columns', 'custom_ce_events_sortable_columns' );\n    function custom_ce_events_sortable_columns( $columns ) {\n       $columns&#91;'tribe-events-status'] = 'tribe-events-status';\n\n       return $columns;\n    }\n\n    \/\/ Add the join clause\n    function tribe_events_custom_join( $join ) {\n       global $wpdb;\n\n       if ( is_admin() &amp;&amp; is_main_query() ) {\n          $join .= \" LEFT JOIN {$wpdb-&gt;postmeta} AS tribe_events_status ON {$wpdb-&gt;posts}.ID = tribe_events_status.post_id AND tribe_events_status.meta_key = '_tribe_events_status'\";\n       }\n\n       return $join;\n    }\n\n    add_filter( 'posts_join', 'tribe_events_custom_join' );\n\n    \/\/ Adjust the orderby clause in SQL\n    function tribe_events_custom_orderby( $orderby, $query ) {\n       global $wpdb;\n       \/\/ Bail, if not admin.\n       if ( ! is_admin() ) {\n          return $orderby;\n       }\n       \/\/ Bail, if not main query.\n       if ( ! $query-&gt;is_main_query() ) {\n          return $orderby;\n       }\n       \/\/ Bail, if it's not for events.\n       if ( $query-&gt;get( 'post_type' ) !== 'tribe_events' ) {\n          return $orderby;\n       }\n\n       $orderby_value = $query-&gt;get( 'orderby' );\n       if ( 'tribe-events-status' == $orderby_value ) {\n          $orderby = \"tribe_events_status.meta_value \" . $query-&gt;get( 'order' );\n       }\n\n       return $orderby;\n    }\n\n    add_filter( 'posts_orderby', 'tribe_events_custom_orderby', 20, 2 );\n}<\/code><\/pre>\n\n\n\n<p>Before adding the snippet, the list view shows no status column:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2024\/07\/events-admin-before-status-snippet.png\" alt=\"The events admin list view before adding the status column snippet\"\/><\/figure>\n\n\n\n<p>After adding the snippet, an Event Status column appears:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2024\/07\/events-admin-after-status-snippet.png\" alt=\"The events admin list view after adding the status column snippet\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-customize-default-event-times\">Customize Default Event Times<\/h3>\n\n\n\n<p>When you create a new event, the default start time is <strong>8:00 am<\/strong> and the default end time is <strong>5:00 pm<\/strong>. You can override these in the editor each time, but if most of your events happen at different hours, it&#8217;s easier to change the defaults globally.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2024\/09\/image-1.png\" alt=\"The default event start and end times shown in the event editor\"\/><\/figure>\n\n\n\n<p>This snippet sets a new default of 9:00 am for the start time and 4:00 pm for the end time. Adjust the times on the <code>return<\/code> lines to fit your own needs.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>add_filter( 'tribe_events_meta_box_timepicker_default', 'my_custom_timepicker_defaults', 10, 3 );\n\nfunction my_custom_timepicker_defaults( $default, $type, $date ) {\n    if ( $type == 'start' ) {\n       return \"09:00:00\";\n    }\n\n    if ( $type == 'end' ) {\n       return \"16:00:00\";\n    }\n\n    return $default;\n}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-auto-delete-featured-images-when-events-are-deleted\">Auto-Delete Featured Images When Events Are Deleted<\/h3>\n\n\n\n<p>When you delete a post in WordPress, the post itself disappears but its featured image stays in your media library. Over time this can clutter your site with unused images and make media management harder.<\/p>\n\n\n\n<p>This snippet automatically deletes an event&#8217;s featured image when the event is permanently removed, keeping your media library tidy with no extra effort.<\/p>\n\n\n\n<p><strong>\u26a0\ufe0f Note:<\/strong> This snippet only deletes the featured image when an event is <strong>permanently deleted<\/strong>, not when it&#8217;s moved to the trash. It also fully removes the file from your server, so the image cannot be recovered afterward.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/\/ Delete the featured image when an event is permanently deleted.\nadd_action( 'before_delete_post', function( $post_id ) {\n    \/\/ Get the post object.\n    $post = get_post( $post_id );\n\n    \/\/ Check if the post is an event.\n    if ( $post &amp;&amp; $post-&gt;post_type === 'tribe_events' ) {\n        \/\/ Check if the event has a featured image.\n        if ( has_post_thumbnail( $post_id ) ) {\n            \/\/ Get the attachment ID of the featured image.\n            $attachment_id = get_post_thumbnail_id( $post_id );\n\n            \/\/ Delete the attachment (featured image).\n            wp_delete_attachment( $attachment_id, true );\n        }\n    }\n}, 10, 1 );<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-change-the-orders-page-title-in-the-admin-dashboard\"><strong>Change the &#8220;Orders&#8221; Page Title in the Admin Dashboard<\/strong><\/h2>\n\n\n\n<p>This filter gives you control over the title displayed for the Event Tickets &#8220;Orders&#8221; page within your WordPress admin dashboard.<\/p>\n\n\n\n<p><strong>What it does:<\/strong>&nbsp;Customizes the page title in the admin backend.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: php; title: ; notranslate\" title=\"\">\nadd_filter( &#039;tribe_tickets_admin_order_page_page_title&#039;, function( $title ) {\n    return __( &#039;Event Registrations Overview&#039;, &#039;your-text-domain&#039; );\n});\n<\/pre><\/div>\n\n\n<p><strong>Result:<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"317\" height=\"467\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2025\/06\/Screenshot-2025-07-01-at-00.22.55.png\" alt=\"\" class=\"wp-image-1965825\" style=\"width:189px;height:auto\" srcset=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2025\/06\/Screenshot-2025-07-01-at-00.22.55.png 317w, https:\/\/images.theeventscalendar.com\/kb\/uploads\/2025\/06\/Screenshot-2025-07-01-at-00.22.55-204x300.png 204w\" sizes=\"auto, (max-width: 317px) 100vw, 317px\" \/><\/figure>\n\n\n\n<p><strong>Ref:<\/strong>&nbsp;<a href=\"https:\/\/docs.theeventscalendar.com\/reference\/hooks\/tribe_tickets_admin_order_page_page_title\/\" target=\"_blank\" rel=\"noreferrer noopener\">tribe_tickets_admin_order_page_page_title<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-granting-custom-user-roles-access-to-attendee-data\">Granting Custom User Roles Access to Attendee Data<\/h2>\n\n\n\n<p>If you\u2019re managing events and need to allow a user with limited permissions to view or export attendee data, you may notice that the Attendees menu or export button isn\u2019t available\u2014even when permissions seem correctly configured. This article explains why that happens and how to safely open up attendee access using a few small code snippets.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-understanding-the-issue\">Understanding the Issue<\/h4>\n\n\n\n<p>By default, the Attendees admin menu and its sub-pages (like Ticket Fieldsets) require the <code>manage_options<\/code> capability, which is typically reserved for Administrators. Users with other roles\u2014Editor, Contributor, or custom roles\u2014won\u2019t see the menu, and visiting it directly returns a &#8220;You do not have permissions to access this page&#8221; error.<\/p>\n\n\n\n<p>The <strong>Export Attendees<\/strong> feature has its own requirement: it\u2019s gated behind the <code>publish_pages<\/code> capability, which is typically available to Super Admins, Admins, and Editors. So even after a user can see the Attendees list, they may still not see the export button.<\/p>\n\n\n\n<p>Granting <code>manage_options<\/code> or <code>publish_pages<\/code> outright isn\u2019t ideal, since it gives broader access than needed. Thankfully, there\u2019s a safer approach that involves up to three steps: making the menu visible, granting the role enough capability to manage the content, and enabling the export button.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-enable-access-to-the-attendees-list\">Enable Access to the Attendees List<\/h3>\n\n\n\n<p>The snippet below lowers the required capability from <code>manage_options<\/code> to <code>edit_posts<\/code>, which Editors and Contributors typically already have.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: php; title: ; notranslate\" title=\"\">\n&lt;?php\n\/**\n * Lower the capability required for Tickets post type\n * can access the Attendees list and other subpages (e.g., Fieldsets list).\n *\/\nadd_filter( &#039;tec_admin_pages_capability&#039;, function( $capability ) {\n\treturn &#039;edit_posts&#039;;\n} );\n<\/pre><\/div>\n\n\n<p>With this in place, anyone who has the <code>edit_posts<\/code> capability will be able to view the Attendees list on the Tickets post type in the dashboard.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-add-permissions-to-read-edit-delete-or-publish-posts\">Add Permissions to Read, Edit, Delete or Publish Posts<\/h3>\n\n\n\n<p>The Attendees list is now visible, but users still won\u2019t have the permissions they need to edit, publish, or delete content on those pages\u2014like updating an attendee record. The following snippet grants a specific role the capabilities required to fully manage these posts.<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: php; title: ; notranslate\" title=\"\">\n&lt;?php\n\/**\n * Ensure a custom role can read, edit, and publish Ticket Fieldsets.\n *\/\nadd_action( &#039;init&#039;, function () {\n\t\/\/ Replace &#039;sample&#039; with your user role slug.\n\t$role = get_role( &#039;sample&#039; );\n\tif ( ! $role ) {\n\t\treturn;\n\t}\n\n\t$role-&gt;add_cap( &#039;read&#039; );\n\t$role-&gt;add_cap( &#039;edit_posts&#039; );\n\t$role-&gt;add_cap( &#039;edit_others_posts&#039; );\n\t$role-&gt;add_cap( &#039;edit_published_posts&#039; );\n\t$role-&gt;add_cap( &#039;publish_posts&#039; );\n\t$role-&gt;add_cap( &#039;delete_posts&#039; );\n} );\n<\/pre><\/div>\n\n\n<p><strong>Important:<\/strong> Be sure to replace <code>'sample'<\/code> with the slug of your target role (for example, <code>'contributor'<\/code> or your own custom role).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-enable-attendee-export-for-limited-or-custom-roles\">Enable Attendee Export for Limited or Custom Roles<\/h3>\n\n\n\n<p>The ability to <a href=\"https:\/\/theeventscalendar.com\/knowledgebase\/tickets-managing-your-orders-and-attendees\/\" target=\"_blank\" rel=\"noreferrer noopener\">export attendees<\/a> in the <a href=\"https:\/\/theeventscalendar.com\/products\/wordpress-event-tickets\/\">Event Tickets<\/a> plugin is controlled by the <code>tec_tickets_attendees_user_can_export_csv<\/code> filter. You can use it to extend export access to other roles\u2014for example, allowing users with the <code>edit_posts<\/code> capability (such as Contributors) to export attendee lists. Add the following snippet to your site:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: plain; title: ; notranslate\" title=\"\">\nadd_filter( &#039;tec_tickets_attendees_user_can_export_csv&#039;, function( $can_export ) {\n    \/\/ If current user can edit posts (is a contributor), allow attendee export.\n    return current_user_can( &#039;edit_posts&#039; );\n});\n\n<\/pre><\/div>\n\n\n<p>This lets users with limited permissions export attendees while keeping your overall site permissions tightly scoped. The same filter can also target a specific custom role\u2014just replace the capability check with logic that confirms the current user has your role slug.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-adding-custom-code-to-your-site\">Adding Custom Code to Your Site<\/h3>\n\n\n\n<p>You can add these PHP snippets to your theme\u2019s <code>functions.php<\/code> file, but we recommend using a dedicated code snippets plugin like <strong><a href=\"https:\/\/wordpress.org\/plugins\/code-snippets\/\" target=\"_blank\" rel=\"noreferrer noopener\">Code Snippets<\/a><\/strong> so your changes survive theme updates. For more details, see our guide on the <a href=\"https:\/\/theeventscalendar.com\/knowledgebase\/best-practices-for-implementing-custom-code-snippets\/\">best practices for implementing custom code snippets<\/a>.<\/p>\n\n\n\n<p>Once the snippets are in place, make sure the target role has the base capabilities (like <code>edit_posts<\/code>) enabled in your user role management plugin. Then log in as that user and confirm that the Attendees menu is visible and the <strong>Export Attendees<\/strong> button appears on the Attendees page.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Events Calendar adds various touches to the WordPress admin \u2014 menus, editor defaults, notices, and list views. You may want to adjust those touches to better fit how you work. This article collects admin-side customizations for The Events Calendar. Hiding Admin UI Elements The two customizations in this section are defined as constants in&#8230;<\/p>\n","protected":false},"author":3,"featured_media":1955565,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_swpsp_post_exclude":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"ep_exclude_from_search":false,"footnotes":""},"categories":[24,59],"tags":[],"stellar-product-taxonomy":[161],"class_list":["post-1962825","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-customizing","category-php","stellar-product-taxonomy-the-events-calendar"],"acf":[],"taxonomy_info":{"category":[{"value":24,"label":"Customizing"},{"value":59,"label":"PHP"}],"stellar-product-taxonomy":[{"value":161,"label":"The Events Calendar"}]},"featured_image_src_large":["https:\/\/images.theeventscalendar.com\/kb\/uploads\/2023\/02\/social-share-1024x538.png",1024,538,true],"author_info":{"display_name":"Jaime Marchwinski","author_link":"https:\/\/theeventscalendar.com\/knowledgebase\/author\/jaimetri-be\/"},"comment_info":0,"category_info":[{"term_id":24,"name":"Customizing","slug":"customizing","term_group":0,"term_taxonomy_id":24,"taxonomy":"category","description":"","parent":0,"count":67,"filter":"raw","term_order":"0","cat_ID":24,"category_count":67,"category_description":"","cat_name":"Customizing","category_nicename":"customizing","category_parent":0},{"term_id":59,"name":"PHP","slug":"php","term_group":0,"term_taxonomy_id":59,"taxonomy":"category","description":"","parent":24,"count":52,"filter":"raw","term_order":"0","cat_ID":59,"category_count":52,"category_description":"","cat_name":"PHP","category_nicename":"php","category_parent":24}],"tag_info":false,"_links":{"self":[{"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1962825","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/comments?post=1962825"}],"version-history":[{"count":8,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1962825\/revisions"}],"predecessor-version":[{"id":1970072,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1962825\/revisions\/1970072"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/media\/1955565"}],"wp:attachment":[{"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/media?parent=1962825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/categories?post=1962825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/tags?post=1962825"},{"taxonomy":"stellar-product-taxonomy","embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/stellar-product-taxonomy?post=1962825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}