Error 500

  • Resolved josenovo

    (@josenovo)


    2 years, 10 months ago

    Hola, estoy teniendo problemas para crear el mapa para el plugin wptv (Live TV Player).

    El mapa general de la web se crea bien pero cuando ingreso al de wptv me devuelve error 500 si presione varias veces F5 me devuelve el cartel de wordpress ′′Ha habido un error crítico en esta web.′′ si sigo presionando F5 termino ingresando al mapa (el programa si lo genera).

    Esto ocurre con todos los navegadores, ya he aumentado los limites de la web pero ocurre lo mismo.

    NOTA:
    En ese mapa se incluye 514 post, yo me imagino que esta generando este error por la cantidad de post que se indexa en esa ruta.

    Creo que la solucion mas logica seria dividir esos 514 post en varias paginas para que se indexe y no en 1 sola que genera el error.

    Hay alguna opcion para hacer esto (yo no lo encontre) ó alguna solucion, porque no me sirve tener un plugin para SEO si los motores de busquedas no pueden ingresar al sitemap.

    Gracias

    Hi, I'm having trouble creating the map for the wptv (Live TV Player) plugin.

The general map of the web is created well but when I enter the wptv it gives me error 500 if I press F5 several times it returns me the wordpress poster ′′There has been a critical error on this web.′′ If I keep pressing F5 I end up entering the map (the program does generate it).

This happens with all browsers, I have already increased the limits of the web but the same thing happens.

NOTE:
In that map 514 posts are included, I imagine that it is generating this error due to the number of posts that are indexed in that route.

I think the most logical solution would be to divide those 514 posts into several pages to be indexed and not just 1 that generates the error.

Is there an option to do this (I didn't find it) or a solution, because it doesn't help me to have an SEO plugin if the search engines can't enter the sitemap.

Thanks
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @josenovo

    If we’re understanding it correctly, the sitemap index is loading fine, but you are getting a 514 error when trying to access the sub-sitemap created with the WPTV plugin.

    Would it be possible for you to provide us with a URL to your sitemap, as well as any relevant error messages from your server’s log when you encounter the 514 error?

    We do know that the default limit for every sitemap is 1000 URLs. You can increase or decrease the limit (which might help) by referring to this article – https://developer.yoast.com/features/xml-sitemaps/api/#alter-the-number-of-sitemap-entries

    Thread Starter josenovo

    (@josenovo)

    Gracias por el soporte, finalmente lo que me funciono es colocar 50 url en varias hojas, de esa forma no me devuelve error 500.

    function max_entries_per_sitemap() {
    return 50;
    }
    add_filter( ‘wpseo_sitemap_entries_per_page’, ‘max_entries_per_sitemap’ );

    Seguramente mi configuración de ini.php corta la carga de la hoja por tener mas de 514 url y tarda en cargar, ahí es donde devuelve el error 500.

    Al tener que cargar solo 50 url en varias paginas, la pagina carga rapido y no devuelve el error 500.

    Algo para probar en laboratorio:

    Copie el codigo del sitemap cuando tenia mas de 514 url por hoja y lo coloque en un archivo .xml, lo subi al servidor y me cargo inmediatamente sin errores.

    Me párese que cuando alguien ingresa al sitemap, Yoast SEO analiza el mismo para actualizarlo o algo hace y eso genera que tarde en cargar y devuelve el error 500 para algunos usuarios.

    Recomiendo que se analice eso, porque yo me di cuanta cuando ingrese al sitemap para revisarlo, si no hubiera hecho eso, esas url no se indexarian nunca.

    Yoast SEO no deberia demorar la carga del sitemap ya que los bot reportarían problemas en las URL (ya me habia pasado antes), tambien estaría bueno tener esta opción de elegir la cantidad de url por pagina desde el admin, yo prefiero cargar menos url por pagina para que cargue mejor y que demoren menos los bot.

    Nuevamente gracias

    Thanks for the support, finally what worked for me is to place 50 urls in several sheets, that way it doesn’t give me the 500 error.

    function max_entries_per_sitemap() {
    return 50;
    }
    add_filter(‘wpseo_sitemap_entries_per_page’, ‘max_entries_per_sitemap’);

    Surely my ini.php configuration cuts the loading of the sheet because it has more than 514 urls and it takes time to load, that’s where it returns the 500 error.

    By having to load only 50 urls in several pages, the page loads fast and does not return the 500 error.

    Something to test in the lab:

    Copy the code from the sitemap when I have more than 514 urls per page and put it in an .xml file, upload it to the server and it loads immediately without errors.

    It seems to me that when someone enters the sitemap, Yoast SEO analyzes it to update it or something does and that causes a delay in loading and returns the 500 error for some users.

    I recommend analyzing that, because I realized when I entered the sitemap to review it, if I hadn’t done that, those urls would never be indexed.

    Yoast SEO should not delay the loading of the sitemap since the bots would report problems in the URL (it had happened to me before), it would also be good to have this option to choose the amount of url per page from the admin, I prefer to load less url per page so that it loads better and that the bots take less time.

    Thank you again

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Error 500’ is closed to new replies.

Tags