A pesar de que, como dije en el post original, yo no había escrito originalmente las modificaciones de código para permitir el Soporte de qTranslate para el Plugin de WordPress Google (XML) Sitemaps Generator, decidí hacer algunas correcciones, abarcando los siguientes puntos:
- La página inicial ahora aparece en los diferentes idiomas en el sitemap.
- Las entradas no escritas en el lenguaje original ya no aparecen más en el sitemap. (Gracias Blutarsky por notificar el error)
Las modificaciones de código actualizadas y la descarga de la nueva versión se encuentran en el post original:
Support appreciated!
All the content offered in this website is, except noted otherwise, of free nature. This means you can share it wherever you want if you do it freely and stating its source.
If it was useful for you and you’d like to contribute, you can make a donation or, at least, visit one of our advertisers of your choice; they are all around the site.
Incoming search terms for the article:
- qtranslate wordpress
- The last run didnt finish! Maybe you can raise the memory or time limit for PHP scripts
- qtranslate Out of memory
- qtranslate codigo
- qtranslate plugin
- wordpress qtranslate
- qtranslate links
- wordpress Script execution halted: Out of memory
- no tiene los permisos wordpress qtranslate
- qtranslate usage
Hi there my friend, I have discovered thatlatest posts aren’t being included in the sitemap. How is that?
Hi man!
I think there isn’t any part of the code which may exclude some published posts…
Has the sitemap been regenerated properly last time?
Try to rebuild it in wp-admin/options-general.php?page=sitemap.php…
If it has, talk to me again and we’ll see which may be the problem…
The strange thing is that I’ve not had any problem of this kind…
Greetings!
NeoEGM.
Sorry I was wwrong, now the missing links are there!
Now it sounds better! 😀
If you have the plugin configured to “Rebuild sitemap if you change the content of your blog”, it may take some minutes after each update for it to get fully rebuilt…
‘Till the next time!
NeoEGM.
OT: wonder if Google gets bothered about continuous notifications or not. At the moment I have disabled notifications, although because Google is downloading daily the sitemap anyway.
Your thoughts?
No, there are no problems in pinging Google each time you update or create a post.
It has an intelligent enough alogorithm to avoid unnecessary downloads. And don’t forget the sitemap itself carries the “Last Modification Date” of each post.
There shouldn’t be any kind of trouble with that option set.
Anyway, the regeneration of the sitemap can take a considerable amount of time as you have more and more posts, tags, categories, etc. So you could regenerate it manually when you wish to lighten your server stress. (There is an option you can enable to be able regenerate your sitemap by just issuing a GET request).
Hope it helps!
NeoEGM.
I’m testing the sitemap build process; it looks like sometimes it is not updated instantaneously, when a new post is published. I have checked out the runtime: when no problem arises, the building process takes about 17.78 seconds to complete and uses 24.5 MB of memory. Reasonable.
But later on I have opened again the admin panel and found the following message:
Any hint?
Sometimes it throws that if you go to the plugin screen while it’s generating the sitemap…
Checked out the debug log, seems timing out when notifying Ask about the update; I have removed any notification….
Yeah… Ask.com sometimes does not work correctly… But not really often…