vBSEO Sitemap does not work anymore

[vBET]

About your access issue once again:
1. Make sure that your sitemap rule is before vBET ruels
2. Make sure that your sitemap rule is finishing one (has L in []), example:

RewriteRule ^((urllist|sitemap_).*\.(xml|txt)(\.gz)?)$ vbseo_sitemap/vbseo_getsitemap.php?sitemap=$1 [L,R=301]

On one of our forums which uses subdirectory in URL we modified rule adding forum directory at the beginning (because of dump redirects):

RewriteRule ^((urllist|sitemap_).*\.(xml|txt)(\.gz)?)$ /forum/vbseo_sitemap/vbseo_getsitemap.php?sitemap=$1 [L,R=301]

If you still have issue please let us know

[badawidollah]

Thanks for note - we miss this issue, because sitemap integration is our next step. Very draft solution - please open sitemap file which generates this error message and add there this code:

require_once(DIR. '/includes/vbenterprisetranslator_functions_vbseo.php');

Add it AFTER:

define('DIR', dirname(__FILE__).'/../'); 

Please let us know did it help

yeah
working

[vBET]

yeah
working

Please note - this is old one and not appropriate now (that was only quick fix). For actual integration instructions please go to integration section

[badawidollah]

Please note - this is old one and not appropriate now (that was only quick fix). For actual integration instructions please go to integration section

are important now
1. sitemap generator has been running
2. vBSEO is running
3. multiple languages is running

shortage
1. vbadvanced software can not run perfectly due vbadvance auto disable modules in index.php

[vBET]

are important now
1. sitemap generator has been running
2. vBSEO is running
3. multiple languages is running

shortage
1. vbadvanced software can not run perfectly due vbadvance auto disable modules in index.php

It is great that you configure your vBET and sitemap If you have issues please create separate threads for each one and do not spam about same issue in many places We see your vbadvance issue in other thread - please stay with this issue there. It has nothing common with issue in this topic which is already solved