to insert the variables into your site you have to manually edit the headinclude file.
You can add any of the following variables:
Code:
Total Number of Members: {vb:var numbermembers}
Total Number of Posts: {vb:var totalposts}
Total Number of Threads: {vb:var totalthreads}
Total Number of active users {vb:var numberusers}
Total Number of users currently online {vb:var totalonline}
Newest Member's Username: {vb:var newusername}
For instance, my headinclude looks like this:
Code:
<meta name="keywords" content="{vb:raw vboptions.keywords}" />
<meta name="description" content="Our {vb:var numbermembers} members have posted {vb: var totalposts} posts about SEO. Please welcome {vb:var newusername} our newest member! | SEO Forum | SEO Tools | SEO Blog | SEO Q&A!" />
USAGE LICENSE - COPYRIGHT - LEGAL NOTICE
Usage of this plugin is free, however you can not re-use the code and you CAN NOT REMOVE THE BRANDING FROM THIS PLUGIN.
should I just append the code to the headinclude or should I replace new code with this:
<meta name="keywords" content="{vb:raw foruminfo.title_clean}, {vb:raw vboptions.keywords}" />
<meta name="description" content="<vb:if condition="$pagenumber > 1">{vb:rawphrase page_x, {vb:raw pagenumber}}-</vb:if>{vb:raw foruminfo.description_clean}" />
you should replace the code currently in your headinclude file, as per the instructions - Im not sure what you are getting at with the code snippet above, just stick to whats in the instructions, get it working, then go from there.
Whats the difference between the gold ones, and the free ones here on vb.org?
1) they are branding free
2) fully supported in a private members area at seoforums.org
3) all new feature development is exclusively for the paid versions, the free versions will now get bug fixes, unless something is deemed absolutely necessary.
4) personalised seo advice from me, if you want it that is!
there's a bug.
When you have vbseo + vbseo sitemap 2.6 installed and visit www.yourdomain.com/vbseo_sitemap/ you will get the following error: Warnung: array_merge() [function.array-merge]: Argument #2 is not an array in [path]/global.php(29) : eval()'d code (Zeile 62)
and you can't login to vbseo_sitemap Panel.
there's a bug.
When you have vbseo + vbseo sitemap 2.6 installed and visit www.yourdomain.com/vbseo_sitemap/ you will get the following error: Warnung: array_merge() [function.array-merge]: Argument #2 is not an array in [path]/global.php(29) : eval()'d code (Zeile 62)
and you can't login to vbseo_sitemap Panel.
I will see if there is anything I can to to avoid this conflict, but it looks like its their product that causes this (hence why they released a bugfix, several years ago!)
there's a bug.
When you have vbseo + vbseo sitemap 2.6 installed and visit www.yourdomain.com/vbseo_sitemap/ you will get the following error: Warnung: array_merge() [function.array-merge]: Argument #2 is not an array in [path]/global.php(29) : eval()'d code (Zeile 62)
and you can't login to vbseo_sitemap Panel.
FYI: Im on 4.0.2 and sitemap 2.5, with no errors...
Does 2.5 still work on vb4? i thought i read somewhere that it didn't thats why they released the 2.6 beta? i could be mistaken but you should check that it's still creating new sitemaps since you upgraded
more of a bug with the vbSEO sitemaps plugin it would appear to me, especially given their fix for it is on their side:
I will see if there is anything I can to to avoid this conflict, but it looks like its their product that causes this (hence why they released a bugfix, several years ago!)
The cited thread is for vBSEO Sitemap version 2.0, nor for 2.6, which is what he is using. Anything less than 2.6 is not compatible with vBulletin 4.x.
Does 2.5 still work on vb4? i thought i read somewhere that it didn't thats why they released the 2.6 beta? i could be mistaken but you should check that it's still creating new sitemaps since you upgraded
Quote:
Originally Posted by djbaxter
The cited thread is for vBSEO Sitemap version 2.0, nor for 2.6, which is what he is using. Anything less than 2.6 is not compatible with vBulletin 4.x.
I will check what Im running now, although I thought it was 2.5