Links inserted into header that cause 404 errors

Home Forums Ticket Products Event Tickets Plus Links inserted into header that cause 404 errors

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #1586078
    Paul Long
    Participant

    Hi, hope you can help

    I’m using Calendar Pro and Events Tickets Plus. On all Event pages on my site, a link similar to the below is being inserted into the <head> section which, by my limited understanding, is something to do with the REST API:

    <link rel="https://theeventscalendar.com/" href="[mydomain]/wp-json/tribe/tickets/v1/tickets/[id]" />

    The problem is that all of these link targets result in a 404, more specifically (when viewed in a browser):

    {"code":"rest_no_route","message":"No route was found matching the URL and request method","data":{"status":404}}

    Whilst this won’t cause any obvious problems to users, they obviously all look like broken links when I audit my site, and I’m concerned that my site will appear to be riddled with broken links which cannot be good from a search engine perspective.

    Can you shed any light on it?

    thanks in advance
    Paul

    #1587050
    Cliff
    Member

    Hi, Paul. I visitedĀ https://londonstreetsphotography.co.uk/event/thames-bridges-300918/ and didn’t see what you reported. Are you still needing assistance with this issue?

    FYI: I noticed you’re not on the latest versions. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

    #1587069
    Paul Long
    Participant

    Thanks Cliff…

    Yes, I’m still seeing the same problem, and as far as I’m concerned, WP core and all of my Tribe plugins are already at the latest version. I’m running:
    WP v4.9.7
    The Events Calendar v4.6.20.1
    Event Tickets v4.7.5.1
    Event Tickets Plus v4.7.5
    Events Calendar Pro v4.4.29.2.

    These all match the latest versions downloadable from my Tribe account. Am I missing something?

    As for the issue itself, I’ve just opened that page, viewed the page source, and Line 176 includes the following:

    <link rel="https://theeventscalendar.com/" href="https://londonstreetsphotography.co.uk/wp-json/tribe/tickets/v1/tickets/2172" />

    That link results in the 404 error I mentioned.

    Are you saying that you can’t see that link at all, or that it doesn’t return a 404?

    thanks
    Paul

    #1588118
    Cliff
    Member

    Oh, missed that. Sorry. I searched your page source for “rest” and forgot to search for “wp-json”.

    I see the core WP REST API is enabled, sinceĀ https://londonstreetsphotography.co.uk/wp-json/ works.

    And I was able to replicate the same 404 error on my testing site so thanks for reporting this bug.

    I marked this thread as Pending Fix, which means it should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

    I apologize for this issue and appreciate your understanding and patience.

    #1645964
    Cliff
    Member

    Hi, Paul.

    This is what I see on my own localhost (my Event Post ID is 154) using the latest releases of each plugin:

    • ET v4.8.2.1
    • ET+ v4.8.2
    • TEC v4.6.24.1
    • PRO v4.4.33

    <link rel="https://theeventscalendar.com/" href="http://tribe.local/wp-json/tribe/tickets/v1/" />

    <link rel="https://theeventscalendar.com/" href="http://tribe.local/wp-json/tribe/events/v1/events/154" />

    Neither is a 404 for me.

    Could you please confirm if this issue is resolved for you?

    #1646505
    Paul Long
    Participant

    Thanks Cliff – yes, it looks like the link that had the ‘tribe/tickets/v1/tickets’ path has been removed, so the problem goes away.

    thanks for following up
    Paul

    #1647087
    Cliff
    Member

    Good news. Thanks for confirming.

Viewing 7 posts - 1 through 7 (of 7 total)
  • The topic ‘Links inserted into header that cause 404 errors’ is closed to new replies.