• Resolved wanner

    (@wanner)


    Prestoplayer seems to generate a conflict with Yoast SEO at the sitemap level, which generates an error in Google’s search console

    The sitemaps concerned are those of the pages and posts

    below the error generated by on my sitemap of pages

    This page contains the following errors:

    error on line 87 at column 6: XML declaration allowed only at the start of the document

    Below is a rendering of the page up to the first error.

    @supports not (aspect-ratio: 16 / 9) { presto-player:not(.hydrated) { height: 0; padding-bottom: 56%; position: relative; } } presto-player:not(.hydrated) { position: relative; background: rgba(0, 0, 0, 0.1); width: 100%; display: block; aspect-ratio: 16 / 9; } presto-player:not(.hydrated) .presto-loader { display: block; } .presto-block-video:not(.presto-sticky-parent) { border-radius: var(–presto-player-border-radius, 0px); overflow: hidden; transform: translateZ(0); } .presto-block-video.presto-provider-audio{ overflow: visible; } .presto-block-video .presto-sticky-parent { overflow: auto; transform: none; } .presto-sticky-parent { z-index: 99998 !important; } .presto-player-fullscreen-open { z-index: 9999999 !important; overflow: visible !important; transform: none !important; } presto-playlist, presto-player-skeleton, presto-timestamp, presto-video-curtain-ui, presto-search-bar-ui, presto-player-button, presto-cta-overlay-ui, presto-video, presto-action-bar-ui, presto-youtube-subscribe-button, presto-email-overlay-ui, presto-player-spinner, presto-action-bar, presto-cta-overlay, presto-email-overlay, presto-bunny, presto-dynamic-overlays, presto-search-bar, presto-youtube, presto-audio, presto-business-skin, presto-modern-skin, presto-muted-overlay, presto-stacked-skin, presto-vimeo, presto-action-bar-controller, presto-cta-overlay-controller, presto-email-overlay-controller, presto-dynamic-overlay-ui, presto-player, presto-playlist-item, presto-playlist-overlay, presto-playlist-ui { visibility: hidden; } .hydrated { visibility: inherit; }

Viewing 4 replies - 1 through 4 (of 4 total)
  • Just activated Presto Player.

    I’ll see if I get the same error.

    Any update on this?

    Thanks

    Hello there! Apologies for the delayed response, and thank you for providing an update.

    Could you please try deactivating the Presto Player plugin to see if the issue persists? Additionally, you may find the following Yoast documentation helpful in checking for plugin conflicts:

    https://yoast.com/help/how-to-check-for-plugin-conflicts/

    Hope this information proves useful. Feel free to let us know the outcome.

    Best Regards,
    Paula

    JohnCleary

    (@johncleary)

    I have this issue too… when I deactivate Presto Player Pro and Presto Player the issue goes away.

    With Pro deactivated Presto Player creates a Fatal Error when attempting to view the XML. With both PP & PPP activated, I see the same error as above.

    • This reply was modified 1 year ago by JohnCleary. Reason: Clarity
    Plugin Support prajna

    (@prajnajogi)

    I’m sorry to hear that you’re experiencing errors with Presto Player. Since you are receiving the error mentioned in this thread when Presto Player Pro is active, Unfortunately, as per the rules set by WP.org, we’re unable to offer support for the Pro version here.

    However, we’re committed to assisting you in resolving this issue. To receive dedicated assistance, could you please open a support ticket using the following link: Support Ticket. Our support team will be delighted to work with you to resolve the error swiftly.

    Best regards,

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Presto Player conflict with Yoast SEO ?’ is closed to new replies.