Jaxel
Well-known member
Its not supposed to... If you created a directory called "sitemap", delete it.This addon simply does not create a directory called "sitemap" in the root directory.
Its not supposed to... If you created a directory called "sitemap", delete it.This addon simply does not create a directory called "sitemap" in the root directory.
Its not supposed to... If you created a directory called "sitemap", delete it.
XenForo doesn't create a directory at "/members" either, but that still works. Its the XenForo routing system.Could you please explain me, why the sitemap should be there, if your script does even not create a directory called with that name? How can it work, if this folder even does not exist by purpose?
Forget it. Rigel's sitemap tool does not work with large boards on shared servers. It is coded in a way so that you have after a few seconds a time out because his script just takes too much RAM (I have 100 MB RAM with 30 seconds CPU time). So we have to get this addon here working!
I just installed it and tried to run the cron manually. It gives me within 5 seconds a success message. If I look on the server, I can see in the /data/sitemap folder 7 different xml files.
if I type in my browser www.mydomain.com/sitemap it just gives me a blank screen. No messages at all.
On the server there is no directory of "sitemap" on the root level, by the way. Only within the data directory and this is not called sitemap, it is called sitemaps.
If I put this in my browser: www.mydomain.com/data/sitemaps
I get an error:
I changed the data directory and the sitemaps directory incl. all files to 777 by the way.
So what now?
ok, so i had a similar problem to snoopy5, but i managed to figure it out. what's happening is that for people that had rigel's sitemap generator installed, and switched to this one, there's a conflict between the route filter of jaxel's plugin and the folder 'sitemap' that get's left over by rigel's plugin.
so... these steps may vary for you depending on your setup, but what i did was un-install this plugin, re-install rigel's plugin, then un-install rigel's plugin, then install jaxel's plugin. i still had a 'sitemap' folder leftover from rigel's plugin, so the conflict was still occurring until i deleted it. you might have wildly different folder permissions than i do, but i had to login via ssh and delete the folder using sudo. after the sitemap folder is gone, i went to mydomain.com/sitemap and the list of sitemaps appeared as they should (and i was able to validate them in google webmaster tools).
just thought i would post what worked for me in case it helps anyone.
I have never spent so much time trying to get an add on to work. Your note was just what I needed to get this working. Many thanks.
I did the following:
- uninstalled rigel's plugin
- deleted /sitemap folder and its contents from /mydomain.com/sitemap
- installed jaxel's plugin
- set the options (google, bing, compress using gzip, etc.)
- I went to the cron and ran the job. Says cron job ran successfully.
Results:
- I do not see a sitemap folder. Is it now located somewhere else? To the best of my knowledge it did not generate a sitemap unless it is hiding somewhere.
- Hey, wait a minute, IT WORKS. My robots.txt now points to
http://www.amphicar770.com/data/sitemaps/forums_1.xml.gz Sure enough, it has generated the files.
Thats not the URL to your sitemap...- Hey, wait a minute, IT WORKS. My robots.txt now points to
http://www.amphicar770.com/data/sitemaps/forums_1.xml.gz Sure enough, it has generated the files.
I have installed this and setup the options as indicated.
I cannot find this folder /sitemaps
I find this folder but it has nothing in it /data/sitemaps
I find this folder but nothing in it that looks like a sitemap \library\EWRutiles\Sitemap\
I also don't seem to see any cron job listed either
Jaxel, will the latest version of this addon work with XF 1.2.4?Lower the "Sitemap URLs per Split" setting.
I just installed it on 1.3.3, so I think it will be fine.Jaxel, will the latest version of this addon work with XF 1.2.4?
We use essential cookies to make this site work, and optional cookies to enhance your experience.