I upgraded to the latest sitemap 1.3 and was running vbseo 2.2.0
and was able to get to http://www.sportsrant.com/forums/vbseo_sitemap/
but when i upgraded to vbseo 2.3, i am unable to get to the sitemap
this has to be a bug
This is a discussion on cannot get to vbseo_sitemap within the Bug Reporting forums, part of the vBSEO SEO Plugin category; I upgraded to the latest sitemap 1.3 and was running vbseo 2.2.0 and was able to get to http://www.sportsrant.com/forums/vbseo_sitemap/ but ...
I upgraded to the latest sitemap 1.3 and was running vbseo 2.2.0
and was able to get to http://www.sportsrant.com/forums/vbseo_sitemap/
but when i upgraded to vbseo 2.3, i am unable to get to the sitemap
this has to be a bug
Hi,
did you added a new .htaccess file in site's root for root-level CRRs support as described in the announcement: vBSEO 2.3.0 Released
If so, have you replaced the highlighted "forum/" part with your REAL forums folder name?
Oleg Ignatiuk / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
well this seems to be for 3.5 which i am not running on my live forums yet.
So do i put that in my roots .htaccess, i know and think it says that, but just want to make sure
When forums reside in subfolder, it is NOT required step to put .htaccess to the site root (http://www.sportsrant.com/.htaccess) - if you have this "extra .htaccess", try to remove vBSEO rewrite rules from it and check if vbseo_sitemap/ works correctly.
Oleg Ignatiuk / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
okay i did this
my .htaccess prior to the vbseo changes:
after# deny most common except .php
<FilesMatch "\.(inc|tpl|h|ihtml|sql|ini|conf|class|bin|spd|the me|module)$">
deny from all
</FilesMatch>
<Limit GET PUT POST>
Order Allow,Deny
Allow from all
</Limit>
# Call CMS
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule . /index.php
RewriteRule ^sitemap.html news.php?do=newshome [L,NC]
AddType audio asx
AddType video x-ms-asf
# deny most common except .php
<FilesMatch "\.(inc|tpl|h|ihtml|sql|ini|conf|class|bin|spd|the me|module)$">
deny from all
</FilesMatch>
<Limit GET PUT POST>
Order Allow,Deny
Allow from all
</Limit>
# Call CMS
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule . /index.php
RewriteRule ^sitemap.html news.php?do=newshome [L,NC]
# vbseo addition to root
RewriteCond %{REQUEST_FILENAME} !forums/
RewriteCond %{QUERY_STRING} !vbseourl=
RewriteRule ^(.*)$ forums/vbseo.php?vbseourl=$1&vbseorelpath=../&%{QUERY_STRING} [L]
RewriteCond %{REQUEST_FILENAME} !forums/
RewriteRule ^(.*.php)$ forums/vbseo.php?vbseourl=$1&vbseorelpath=../&%{QUERY_STRING} [L]
AddType audio asx
AddType video x-ms-asf
and when i add that, it screws up my root site mod_rewrite
Any ideas
that makes no sense and contradicts the statement in the release message:Originally Posted by Oleg Ignatiuk
it clearly states that you need to add this to your ROOT(7) UPDATE: CRRs in Root (beta2) update - Several refinements have been made to the 'CRR in Root' beta feature. Also, a problem with redirection of old URLs from the root level has been corrected.
Note: This requires an additional step in the installation process. The following updated .htaccess directives must be added in the *root folder* (not vBulletin folder):
Code:
RewriteEngine On RewriteCond %{REQUEST_FILENAME} !forum/RewriteCond %{QUERY_STRING} !vbseourl=RewriteCond %{REQUEST_FILENAME} !-fRewriteCond %{REQUEST_FILENAME} !-dRewriteRule ^(.*)$ forum/vbseo.php?vbseourl=$1&vbseorelpath=../&%{QUERY_STRING} [L] RewriteCond %{REQUEST_FILENAME} !forum/RewriteRule ^(.*.php)$ forum/vbseo.php?vbseourl=$1&vbseorelpath=../&%{QUERY_STRING} [L]
Note: In the above "forum" must be changed to the actual name of the folder in which your vBulletin installation resides.
So please clarify that
Hm.. but if you remove vBSEOs rewrite rules from root .htaccess - does everything works correctly?
Edit: as it is stated, all this is related to a new "root CRRs" beta feature (i.e., it is optional to use):
(7) UPDATE: CRRs in Root (beta2) update
Oleg Ignatiuk / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!
Originally Posted by Oleg Ignatiuk
yes it does except i cannot get to the sitemap!
right but my whole point is that I upgraded the sitemap to 1.3 and then upgraded to the new vbseo 2.3, i did not want to use the option on the root becuase of my custom CMS. but once i upgraded to the new vbseo, i could not get to the sitemap
please close this as not a bug, i found the problem, i had some foreign text in my .htaccess, I am sorry
Ok, great!
Oleg Ignatiuk / Crawlability Inc.
Security vbulletin - Patch Level for all supported versions released!
Unveiling the NEW vBSEO Sitemap Generator 3.0. - available NOW for vBSEO Customers!