sitemap cron stoped working with RC4.

My sitemap server cron seems to have stoped running after I updated VBSEO to RC4. It runs fine if run directly but the server cron no longer functions. Anything change there?

what sitemap version are you running?

1.6

Thought so..

get 1.7

vBSEO v.3.0.0 Release Candidate 3 Released!

And where would that be?

Ah, my tired eyes see the link.

Still not working.

Code:

Cannot run sitemap generator directly: you should set "Run from vB Scheduled Tasks Manager ONLY" to "No" in admincp to allow

And before you ask, it is set to no.

Actually, it was set to no in 1.6. It doesn't even seem to exist in 1.7. I don't have that settings option anymore.

Looking at the code it looks like it is intended only to run in shedule task or directly now. Server cron will fail since it is looking for $_COOKIE data.

Hello,

there is the following code:

PHP Code:

    if(isset($_SERVER['REQUEST_URI'])) 


so it should work from command line (system cron) in any case.
If you want to execute sitemap generator from vbseo_sitemap/ interface, make sure that you have defined password in vB options (i.e. it's not empty).

mine has stopped running with rc4 sitemap 1.7
I can run manually, but I haven't gotten the emails saying sitemap has been submitting since I upgraded to rc4c
I haven't had time to look into this, but I seen this thread and wanted to throw my post in

Hi Brandon,

are you using system cron or vBulletin scheduled task?

Originally Posted by Oleg Ignatiuk

Hello,

there is the following code:

PHP Code:

    if(isset($_SERVER['REQUEST_URI'])) 


so it should work from command line (system cron) in any case.
If you want to execute sitemap generator from vbseo_sitemap/ interface, make sure that you have defined password in vBulletin options (i.e. it's not empty).

Well, it doesn't work in server cron. And it has not worked since RC4. It worked in RC3. RC4 changed something. Those are the present facts.

Please try changing REQUEST_URI to REQUEST_METHOD. If it still doesn't work, could you please open a support ticket with ssh access for troubleshooting?