Configurable max number of URLs in sitemap.
Enable/Disable XSL stylesheet
Settings page reorganization
View the_yke's plugins
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
Thanks for the updated version of this. Very useful plugin.
<sitemapindex>
<sitemap>
<loc>
http://www.domain.xx/elgg_folder/auto_sitemap/custom
</loc>
</sitemap>
<sitemap>
<loc>
http://www.domain.xx/elgg_folder/group
</loc>
</sitemap>
<sitemap>
<loc>
http://www.domain.xx/elgg_folder/auto_sitemap/blog
</loc>
</sitemap>
<sitemap>
<loc>
http://www.domain.xx/elgg_folder/auto_sitemap/other
</loc>
</sitemap>
</sitemapindex>
When go to http://www.domain.xx/elgg_folder/sitemap.xml then system message shows up: page not found
And do we need to insert this in robots.txt?
Sitemap: http://domain.xx/elgg_folder/sitemap.xml
i installed this on nginx and used the following instead of the htaccess lines:
rewrite ^/sitemap.xml$ /auto_sitemap/index last;
rewrite ^/sitemap.xsl$ /mod/auto_sitemap/views/default/auto_sitemap/sitemap.xsl last;
rewrite ^/sitemapindex.xsl$ /mod/auto_sitemap/views/default/auto_sitemap/sitemapindex.xsl last;
i believe these are the appropriate directives...
i am left with the url in the footer nav that was present in the previous version of the sitemap plugin i had installed (which i think was not coded by the same uploader here).. which points to:
mysite.com/xml_sitemap
and when i navigate there i am not seeing any sitemap.
i am also not seeing a sitemap at /sitemap.xml (nginx reports a 404 error)..
the /sitemap.xsl does exist and i downloaded it; it is relatively small and doesn't contain any site links.. i am imagining that is by design as i am not sure what that file is intended to hold.
i have cleared the cache, turned the css config option on and off and also restarted nginx.. does anyone know what i have maybe missed here?
thanks
xsurf:
have you updated your htaccess?
robots.txt has nothing to do with the sitemap.
ura soul:
sorry, cannot help you with nginx. but i'm thinking in give it a try. Any elgg problem with it and elgg, or some scary configuration trics? can be nginx work with APC ?
Tested in a clean elgg 1.8.12 install, with apache and this domain configurations:
http://www.example.com/
http://example.com/
http://subdomain.example.com/
http://www.example.com/elgg-folder/
the nginx config for elgg in the elgg documentation is not optimal, i created one after reading about how they are designed. with the correct config file nginx has been much more efficient and reliable than apache for me.
i'm not the best one to ask about apc, i haven't explored it in detail.
@the_yke
Yes I updated htacces first.
And I disabled for testing Liang Lees Metatags.
xsurf
can you share your sites's url?
@the_yke
Due to redundant inconveniences, I prefer not to share my site, here. :/
Thanks for understanding.
ura soul
why do you thisnk this version is coded by another one? just curiosity
@the_yke - On this new version is there a way to test to make sure its setup properly before I submit to any search engines? I can view the tree by visiting mysite.com/sitemap.xml in firefox, but I want to make sure its actually doing what its supposed to before I submit, how to be certain?
good idea
if you already have a static sitemap file in your site and you only want to test the plugin, yo can put this line in the .htaccess:
RewriteRule ^sitemap-preview.xml$ auto_sitemap/index [L]
instead of
RewriteRule ^sitemap.xml$ auto_sitemap/index [L]
and then visit http://YOURSITE.XXX/sitemap-preview.xml.
And once the plugin fits your requeriments, remove the "-preview" part in the .htaccess
This way, your sitemap.xml will still work, while you can ptest the plugin.
Can someone help me to explain this properly to include this in de documentation? I,ve noticed many people doesn't understand the plugin functionality correctly. Maybe my english? Any suggestion will be welcome
As I wrote, when I go to sitemap.xml (logged in), then I get the error: page not found.
But the errorpage then seems to be a loggded-out page. How could this be?
I don't need to log in then, I just have to click on homepage and I'm back to loggedin startpage.
I can't understand this... :)
i can't find any .htaccess file on my installation. i only see htaccess_dist and when i added the three lines of coding, i am still not seeing a sitemap at http://www.mysite/sitemap.xml (it reports a 404 error)... I'm using elgg 1.8.16,can anybody help please??
please, search for the .htaccess in your root directory. this is a hidden file.
Id this file really doesnt exists in your installation, check de install.txt doc of elgg.
i just noticed that the sitemap ignores privacy settings.. so non public entities are being included in the sitemap.. not so great.
this can be resolved by adding to line #76 in start.php :
$options['wheres'] = array('e.access_id = 2');
This is a great idea however it's not scalable. I've inherited a site that's using this plugin and they have over 100k users - the users sitemap generation fails with OOM
Thank you for making such a useful plugin!
good, on my site I get:
This page contains the following errors:
Below is a rendering of the page up to the first error.
as I fix this?
thank you
cadmeo, send me your site url. may be you have some white spaces at the begining of the file
cadmeo, I visited your site and you have a plugin that is prepending some html comment before the content. that's the problem, hope it helps
Hi, when I check my sitemap in Google webmarters tools y get an error:
"El sitemap es HTML"
"Tu sitemap parece ser una página HTML. Utiliza un formato de sitemap compatible"
I think the plugin is generating a sitemap with a wrong format, Any suggestion to solve this issue?
Thanks.
Hola Javier, puede que tengas el mismo problema que cadmeo. Tenia un plugin instalado que añadia espacios antes de la etiqueta xml.
Si me das la url de tu sitio quizás te pueda ayudar
Parece que tu sitio está redirigiendo al index. Has añadido las lineas en el htaccess?