vBSEO Sitemap Update with 3.2.0 Release Candidates

Verification is not related to sitemaps though, it allows you to get access to other site tools in webmaster account.

This SQL error is generated from a cron process isn't it? I was befuddled by the table name, as I thought all the vbseo tables had a vbseo_ prefix.

Originally Posted by TnTU

This SQL error is generated from a cron process isn't it? I was befuddled by the table name, as I thought all the vbseo tables had a vbseo_ prefix.

It's from running the pre-vBSEO3.2 Sitemap Generator against the post-vBSEO3.2 database.

3.2 replaces the linkback table with the vbseo_linkback table.

thanks for this

try to upadated to latest

Im getting this error in some of my xmls I have 62 with 40,000 urls in each.

XML Parsing Error: not well-formed
Location: http://www.toontowncentral.com/forums/sitemap_10.xml.gz
Line Number 94660, Column 18: <priority>0.58<>0.3</priority>
-----------------^

Originally Posted by NickFritz

Im getting this error in some of my xmls I have 62 with 40,000 urls in each.

XML Parsing Error: not well-formed
Location: http://www.toontowncentral.com/forums/sitemap_10.xml.gz
Line Number 94660, Column 18: <priority>0.58<>0.3</priority>
-----------------^

Please create a support thread at vBSEO Sitemap Section. This thread is not for support however you can solve that by re running vbseo sitemap generator from vbseo_sitemap/ interfrance

Originally Posted by newguy

I got a database error. Came to the vBSEO forum and searched my error

PHP Code:

linkback' doesn't exist 


and found this thread. Its fixed now. Thanks

x2. thanks.

Cool! This solved my problem. Nice work you guys!

teşekkürler mert bey

excellent works a treat now after receiving 4 failure mails i thought it time to investigate and found this thread

Using the sitemap plugin now, make sure you CHMOD to 777 and not 666...666 didn't work and strained my server with errors...

in general, 777 is bad to leave. It's ok do set it, make your change, and then reset to 644.

In most cases, 766 is the optimial solution

Originally Posted by briansol

in general, 777 is bad to leave. It's ok do set it, make your change, and then reset to 644.

In most cases, 766 is the optimial solution

I got PHP gzwrite errors with 666 and 766..

Teşekkürler Mert bey.