{"id":1896713,"date":"2019-10-18T13:19:56","date_gmt":"2019-10-18T17:19:56","guid":{"rendered":"https:\/\/theeventscalendar.com\/knowledgebase\/troubleshooting-duplicate-imports\/"},"modified":"2026-04-21T12:31:01","modified_gmt":"2026-04-21T16:31:01","slug":"troubleshoot-imports","status":"publish","type":"post","link":"https:\/\/theeventscalendar.com\/knowledgebase\/troubleshoot-imports\/","title":{"rendered":"Troubleshooting Event Imports"},"content":{"rendered":"\n<p>Importing events with Event Aggregator is usually painless \u2014 but when something goes wrong, the failure mode matters. This article covers the most common import problems: duplicate events multiplying on your calendar, events that silently fail to import, and the error messages you may see when importing from another site&#8217;s REST API.<\/p>\n\n\n\n<iframe loading=\"lazy\" width=\"560\" height=\"315\" src=\"https:\/\/www.youtube.com\/embed\/eT9zPm1cVsU\" title=\"YouTube video player\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen=\"\"><\/iframe>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-how-event-aggregator-matches-events\">How Event Aggregator Matches Events<\/h2>\n\n\n\n<p>iCalendar feeds and ICS files contain information about events in a <a href=\"https:\/\/icalendar.org\/\">standardized format<\/a>, which allows those events to be imported to other platforms. Part of the information that is included for each event is a unique identifier, or UID.<\/p>\n\n\n\n<p>When you import events from an iCalendar feed or an ICS file, Event Aggregator uses an event&#8217;s UID to determine whether an event is new and needs to be created or has already been imported. If it finds an event on your site with the same UID, that event will be updated on your site or ignored, depending on your Event Update Authority settings under <strong>Events \u2192 Settings \u2192 Imports<\/strong>. If it doesn&#8217;t see an event on your site with that UID, it creates a new one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-preventing-duplicate-imports\">Preventing Duplicate Imports<\/h2>\n\n\n\n<p>A few habits go a long way toward keeping duplicates out of your calendar in the first place:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Use sources that provide stable unique identifiers.<\/strong> Each event should have a unique ID, URL, or UID (for iCal feeds). If your source feed doesn&#8217;t provide stable unique IDs, duplicates become much more likely \u2014 see the next section for specifics on which sources have this problem.<\/li>\n\n\n\n<li><strong>Stick with one source per calendar.<\/strong> Import from the same feed or file consistently. Switching sources mid-stream can cause Event Aggregator to misidentify the same event coming from two places and import it twice.<\/li>\n\n\n\n<li><strong>Don&#8217;t over-schedule imports.<\/strong> Frequent runs can amplify duplicate issues if event data changes between runs. A daily or weekly schedule usually hits the right balance.<\/li>\n\n\n\n<li><strong>Review your import settings.<\/strong> If you install the <a href=\"https:\/\/theeventscalendar.com\/extensions\/ea-additional-options\/\">Event Aggregator: Additional Options<\/a> extension, you&#8217;ll get an added option under <strong>Events \u2192 Settings \u2192 Imports<\/strong> for how previously imported events should be handled \u2014 overwrite, preserve, or skip.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-why-duplicates-still-happen\">Why Duplicates Still Happen<\/h2>\n\n\n\n<p>Typically, a UID remains the same in the source calendar, and each time you run an import, Event Aggregator sees a matching ID for events already imported. However, the UID doesn&#8217;t always stay stable. There are a few cases where it changes, which makes Event Aggregator see the event as new.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-some-sources-change-the-uid\">Some Sources Change the UID<\/h4>\n\n\n\n<p>In some cases, the source calendar provides a different UID each time the calendar is updated. When that happens, Event Aggregator sees the new UID and creates a new event. Outlook calendars are one such source \u2014 the UID changes regularly, so Event Aggregator can&#8217;t reliably detect changes.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-recurring-events-in-a-google-calendar\">Recurring Events in a Google Calendar<\/h4>\n\n\n\n<p>Google Calendars don&#8217;t change the UID when single events are modified, but recurring events are a different story. Say you create a recurring event in your Google Calendar that recurs daily, weekly, monthly, or yearly. In the iCalendar feed Google creates, this produces one event entry with a recurrence rule that looks like this:<\/p>\n\n\n\n<p><code>RRULE:FREQ=WEEKLY;WKST=SU;UNTIL=20190704T035959Z;BYDAY=WE<\/code><\/p>\n\n\n\n<p>Event Aggregator reads this and creates single events on your site using the recurrence information. However, if you modify one instance of that event, a new entry with a separate UID is generated in the iCalendar feed. Because the feed doesn&#8217;t include any data indicating that this new event is &#8220;linked&#8221; to the original, Event Aggregator sees two separate UIDs and creates a new event for the modified instance.<\/p>\n\n\n\n<p>Since recurring events import as single events, you can use the <em>series<\/em> feature included with Events Calendar Pro 6.0 and above to group related events together. Head to <strong>Events \u2192 Series \u2192 Add New<\/strong>, select the events you&#8217;d like to group, and you&#8217;ll have a dedicated event page for everything in the series.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-cleaning-up-duplicates\">Cleaning Up Duplicates<\/h2>\n\n\n\n<p>If duplicates have already made it onto your site, you have three options for cleanup depending on scale.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-quick-fix-hide-a-single-duplicate\">Quick Fix: Hide a Single Duplicate<\/h4>\n\n\n\n<p>For a handful of duplicates, the simplest option is to <a href=\"https:\/\/theeventscalendar.com\/knowledgebase\/ignored-events\/\">hide the old version<\/a> of each event, which prevents it from showing up anywhere on the front end.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-snippet-cleanup-for-many-duplicates\">Snippet Cleanup for Many Duplicates<\/h4>\n\n\n\n<p>For a larger cleanup, use the following snippet-based process:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Install the free <a href=\"https:\/\/wordpress.org\/plugins\/code-snippets\/\">Code Snippets<\/a> plugin.<\/li>\n\n\n\n<li>In your dashboard, go to <strong>Snippets \u2192 Add New<\/strong>. Copy <a href=\"https:\/\/d.pr\/n\/QkE2LD\">this snippet<\/a> and paste it into the field.<\/li>\n\n\n\n<li>Under the snippet field, select <em>Only run in administration area<\/em> (<a href=\"https:\/\/d.pr\/i\/aY3YCe\">screenshot<\/a>).<\/li>\n\n\n\n<li>Click the <em>Save changes and activate<\/em> button.<\/li>\n\n\n\n<li>From the Dashboard menu, click <strong>Events<\/strong>. The snippet will start to run and the page will take longer than usual to load. Stay on the page until it loads, and you&#8217;ll see the duplicates have been moved to <em>Ignored<\/em> status. This may take a while depending on how many duplicates there are.<\/li>\n\n\n\n<li>Go back to <strong>Snippets \u2192 All Snippets<\/strong>. Again, the page will take longer than expected to load. During this time the <em>Ignored<\/em> events will be permanently deleted.<\/li>\n\n\n\n<li>Deactivate or delete the snippet.<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-batched-cleanup-for-thousands-of-duplicates\">Batched Cleanup for Thousands of Duplicates<\/h4>\n\n\n\n<p>If you&#8217;ve got a huge number of duplicate events, processing them all at once can time out. In that case, use this batched variant \u2014 each run processes up to 1,000 events, and you repeat until you&#8217;re done.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Install the free <a href=\"https:\/\/wordpress.org\/plugins\/code-snippets\/\">Code Snippets<\/a> plugin.<\/li>\n\n\n\n<li>In your dashboard, go to <strong>Snippets \u2192 Add New<\/strong>. Copy <a href=\"https:\/\/d.pr\/n\/hTdF3P\">this snippet<\/a> and paste it into the field.<\/li>\n\n\n\n<li>Optional: adjust the limit in line 6 to set how many events will be processed per batch.<\/li>\n\n\n\n<li>Under the snippet field, select <em>Only run in administration area<\/em> (<a href=\"https:\/\/d.pr\/i\/aY3YCe\">screenshot<\/a>).<\/li>\n\n\n\n<li>Click the <em>Save changes and activate<\/em> button.<\/li>\n\n\n\n<li>From the Dashboard menu, click <strong>Events<\/strong>. Stay on the page until it loads, and you&#8217;ll see some duplicates moved to <em>Ignored<\/em> status. Reload the page and another batch will process.<\/li>\n\n\n\n<li>Refresh the page as many times as you need until the duplicate events are fully removed and you no longer see them under <em>Ignored<\/em>.<\/li>\n\n\n\n<li>Go back to <strong>Snippets \u2192 All Snippets<\/strong> and deactivate or delete the snippet.<\/li>\n<\/ol>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-the-event-aggregator-additional-options-extension\">The Event Aggregator: Additional Options Extension<\/h4>\n\n\n\n<p>For ongoing automation rather than one-time cleanup, the <a href=\"https:\/\/theeventscalendar.com\/extensions\/ea-additional-options\/\">Event Aggregator: Additional Options<\/a> extension adds a <strong>Delete Duplicate\/Removed Events for Scheduled Imports<\/strong> feature. When scheduled imports run, the extension checks for any current or future events from previous imports (from the same source). If those events aren&#8217;t present in the new import, it can take one of three actions based on your configuration:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do not delete duplicate\/removed events<\/li>\n\n\n\n<li>Send them to trash<\/li>\n\n\n\n<li>Permanently delete them<\/li>\n<\/ul>\n\n\n\n<p><strong>\ud83d\udca1 Note:<\/strong> This extension currently does not have the ability to delete upcoming events <em>prior<\/em> to the import running.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-when-imports-silently-skip-events\">When Imports Silently Skip Events<\/h2>\n\n\n\n<p>Sometimes specific events just don&#8217;t show up after an import. You check your feed settings, API limits, date ranges, and everything else \u2014 and still nothing. Yet the import logs look clean, with no errors. A common cause is a naming conflict with events in your <strong>Ignored<\/strong> or <strong>Trash<\/strong> folders.<\/p>\n\n\n\n<p>When an event name matches one already in Trash or Ignored, Event Aggregator and Eventbrite Tickets treat it as already accounted for \u2014 deliberately excluded \u2014 and skip the import. Even a trashed event can block a re-import until it&#8217;s cleared out or restored.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-diagnosing-the-silent-skip\">Diagnosing the Silent Skip<\/h4>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Identify which events are missing.<\/strong> Make a list of the events you expected to import but don&#8217;t see on your calendar. Note their names, dates, and any unique details.<\/li>\n\n\n\n<li><strong>Check the Ignored folder.<\/strong> In your WordPress dashboard, go to <strong>Events \u2192 Ignored<\/strong>. Search by event name \u2014 a match here may be blocking the import.<\/li>\n\n\n\n<li><strong>Check the Trash folder.<\/strong> Go to <strong>Events \u2192 Trash<\/strong> and search again. Even a trashed event can cause the system to treat the incoming event as a duplicate and refuse to reimport.<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/images.theeventscalendar.com\/kb\/uploads\/2025\/09\/Image-2025-01-12-at-9.37.40-AM.png\" alt=\"Ignored and Trash folders in the Events menu\"\/><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-clearing-the-conflict\">Clearing the Conflict<\/h4>\n\n\n\n<p>Once you locate the conflicting entry in Ignored or Trash, you have two options:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Delete permanently.<\/strong> Empty the trash or permanently remove the ignored entry. This clears the name conflict so the import can treat the incoming event as new.<\/li>\n\n\n\n<li><strong>Restore it.<\/strong> Restore the existing entry to Published or Draft status. The event then already exists, and the import logic may update it rather than skip it (depending on your import update settings).<\/li>\n<\/ul>\n\n\n\n<p>After clearing or restoring the conflicting event, re-run the import manually or let the next scheduled run execute. Watch the preview or logs to confirm the formerly missing event now appears in the list to be imported or updated, and check your calendar to verify it shows up.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-fixing-the-sorry-this-file-type-is-not-permitted-error\">Fixing the &#8220;Sorry, this file type is not permitted&#8221; Error<\/h2>\n\n\n\n<p>If you see an error saying <em>&#8220;Sorry, this file type is not permitted for security reasons&#8221;<\/em> when uploading a CSV, add the following snippet to your theme&#8217;s <code>functions.php<\/code> file:<\/p>\n\n\n\n<p>&lt;?php\nadd_filter( &#8216;upload_mimes&#8217;, function( $types ) {\n    $types[&#8216;csv&#8217;] = &#8216;text\/csv&#8217;;\n    return $types;\n} );<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-other-url-import-errors\">&#8220;Other URL&#8221; Import Errors<\/h2>\n\n\n\n<p>The &#8220;Other URL&#8221; import source lets you fetch events from another website running The Events Calendar. When that import fails, you&#8217;ll typically see one of the following error messages. Each one points at a slightly different problem.<\/p>\n\n\n\n<iframe loading=\"lazy\" src=\"https:\/\/www.youtube.com\/embed\/MXCxviZ3NX8\" title=\"YouTube video player\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen=\"\" width=\"560\" height=\"315\" frameborder=\"0\"><\/iframe>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-rest-api-not-supported\">REST API Not Supported<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The requested URL does not support The Events Calendar REST API.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The site you&#8217;re trying to pull events from is on an older version of WordPress or has disabled the WP REST API infrastructure.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-rest-api-disabled\">REST API Disabled<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The Events Calendar REST API is disabled on the requested URL.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The site you&#8217;re trying to pull events from supports The Events Calendar REST API but has disabled it.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-malformed-data\">Malformed Data<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but returned malformed data.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The site provided data that is malformed and differs to varying degrees from the expected format. This could be due to a communication error between the EA service and the source site, or due to a custom modification of The Events Calendar REST API that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-archive-control-data-error\">Archive Control Data Error<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but there was an error while fetching the archive control data.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> Similar to the Malformed Data error above, this happens when the archive page the EA service is trying to fetch provides inconsistent or bad data regarding page number, totals, or format. This could be due to a communication error between the EA service and the source site, or due to a custom modification of The Events Calendar REST API that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-total-event-count-error\">Total Event Count Error<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but there was an error while fetching the total number of events.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The EA service needs to know how many events exist matching a criteria. If the source site doesn&#8217;t provide that information, events can&#8217;t be pulled from it. This could be due to a communication error or a custom REST API modification that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-non-numeric-event-count\">Non-Numeric Event Count<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but returned malformed data in regard to the total number of events.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The EA service needs to know how many events exist matching a criteria. If the source site provides that information but it&#8217;s not a number, events can&#8217;t be pulled from it. This could be due to a communication error or a custom REST API modification that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-archive-page-fetch-error\">Archive Page Fetch Error<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but there was an error while fetching an archive page.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The data returned for an archive page the EA service requested was malformed or inconsistent. This could be due to a communication error or a custom REST API modification that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-empty-archive-page\">Empty Archive Page<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but returned an empty archive page.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The EA service knows when an archive page is going to be empty, but that knowledge depends on data the source site provides. If the reported data and the reality don&#8217;t align, the EA service can run into an empty archive page. This could be due to a communication error or a custom REST API modification that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-event-data-fetch-error\">Event Data Fetch Error<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but there was an error while fetching the event data.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The EA service could find the requested event but received inconsistent or malformed data when trying to fetch it. This could be due to a communication error or a custom REST API modification that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-empty-event-data\">Empty Event Data<\/h4>\n\n\n\n<p><em>&#8220;Events could not be imported. The URL provided could be reached and has The Events Calendar REST API enabled, but returned empty event data.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The EA service could find the requested event but received empty data when trying to fetch it. This could be due to a communication error or a custom REST API modification that provides a response in a format we can read.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-site-not-compatible\">Site Not Compatible<\/h4>\n\n\n\n<p><em>&#8220;ERROR: Event Aggregator cannot import events from this site.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> The website may be one of the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Not a WordPress website<\/li>\n\n\n\n<li>A WordPress website without the latest The Events Calendar plugin installed or activated<\/li>\n\n\n\n<li>A WordPress website on an older WP version that doesn&#8217;t support the REST API<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"h-connection-not-completed\">Connection Not Completed<\/h4>\n\n\n\n<p><em>&#8220;ERROR: There was an error fetching the results from your import: The connection was not completed correctly. This means the connection is having problems to complete \u2014 try with a smaller number of events or check if your connection is active.&#8221;<\/em><\/p>\n\n\n\n<p><strong>Cause:<\/strong> This can happen when the data source is not supported \u2014 for example, RSS feeds.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Importing events with Event Aggregator is usually painless \u2014 but when something goes wrong, the failure mode matters. This article covers the most common import problems: duplicate events multiplying on your calendar, events that silently fail to import, and the error messages you may see when importing from another site&#8217;s REST API. How Event Aggregator&#8230;<\/p>\n","protected":false},"author":5,"featured_media":1955565,"comment_status":"closed","ping_status":"closed","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":[126],"tags":[45],"stellar-product-taxonomy":[154],"class_list":["post-1896713","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-event-aggregator","tag-importing","stellar-product-taxonomy-event-aggregator"],"acf":[],"taxonomy_info":{"category":[{"value":126,"label":"Importing Events"}],"post_tag":[{"value":45,"label":"Importing"}],"stellar-product-taxonomy":[{"value":154,"label":"Event Aggregator"}]},"featured_image_src_large":["https:\/\/images.theeventscalendar.com\/kb\/uploads\/2023\/02\/social-share-1024x538.png",1024,538,true],"author_info":{"display_name":"Leah","author_link":"https:\/\/theeventscalendar.com\/knowledgebase\/author\/leahk\/"},"comment_info":0,"category_info":[{"term_id":126,"name":"Importing Events","slug":"event-aggregator","term_group":0,"term_taxonomy_id":126,"taxonomy":"category","description":"","parent":61,"count":8,"filter":"raw","term_order":"0","cat_ID":126,"category_count":8,"category_description":"","cat_name":"Importing Events","category_nicename":"event-aggregator","category_parent":61}],"tag_info":[{"term_id":45,"name":"Importing","slug":"importing","term_group":0,"term_taxonomy_id":45,"taxonomy":"post_tag","description":"","parent":0,"count":14,"filter":"raw","term_order":"0"}],"_links":{"self":[{"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1896713","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\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/comments?post=1896713"}],"version-history":[{"count":9,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1896713\/revisions"}],"predecessor-version":[{"id":1969656,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/posts\/1896713\/revisions\/1969656"}],"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=1896713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/categories?post=1896713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/tags?post=1896713"},{"taxonomy":"stellar-product-taxonomy","embeddable":true,"href":"https:\/\/theeventscalendar.com\/knowledgebase\/wp-json\/wp\/v2\/stellar-product-taxonomy?post=1896713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}