Subscribe to Mark Bolyard via RSS
Follow Mark Bolyard on Twitter
Over the course of the next week, I will be updating several vBulletin themes to 3.8.3 and making them available to download here at vBulletinPro. You may also notice the blog being changed / tweaked, so please bare with me and feel free to report any bugs using the contact us link.
Thank you.
To help prevent vBulletin from generating duplicate content, it is suggested that you add a robots.txt file to your forum root. The below code prevents search engines from crawling unnecessary urls and indexing duplicate content, along with other miscellaneous urls you don’t want to clutter your search listings with.
User-agent: *
Disallow: /clientscript/
Disallow: /cpstyles/
Disallow: /customavatars/
Disallow: /customprofilepics/
Disallow: /signaturepics/
Disallow: /customgroupicons/
Disallow: /images/
Disallow: /includes/
Disallow: /install/
Disallow: /archive/
Disallow: /ajax.php
Disallow: /announcement.php
Disallow: /attachment.php
Disallow: /calendar.php
Disallow: /converse.php
Disallow: /cron.php
Disallow: /editpost.php
Disallow: /faq.php
Disallow: /global.php
Disallow: /group_inlinemod.php
Disallow: /groupsubscription.php
Disallow: /infraction.php
Disallow: /inlinemod.php
Disallow: /joinrequests.php
Disallow: /login.php
Disallow: /member_inlinemod.php
Disallow: /misc.php
Disallow: /moderation.php
Disallow: /moderator.php
Disallow: /newattachment.php
Disallow: /newreply.php
Disallow: /newthread.php
Disallow: /online.php
Disallow: /payment_gateway.php
Disallow: /payments.php
Disallow: /picture_inlinemod.php
Disallow: /posthistory.php
Disallow: /postings.php
Disallow: /printthread.php
Disallow: /private.php
Disallow: /profile.php
Disallow: /register.php
Disallow: /report.php
Disallow: /reputation.php
Disallow: /search.php
Disallow: /sendmessage.php
Disallow: /subscription.php
Disallow: /threadrate.php
Disallow: /usercp.php
Disallow: /usernote.php
if you already have a robots.txt file, simply edit it, and add the above lines to your code (check for duplicates). If you do not have a robots.txt file, create one and add the above code to it. Save and upload to your forum root directory.
|
Originally Posted by Ohiosweetheart
(Post 1764551) Wait, just to be clear, members will not be able to purchase the blog and project tools separately, as they have been doing?
|
This is correct. Blog, Project Tools and CMS will not be distributed as separate products, but will be bundled with the vBulletin Suite.
In answer to some of the questions about this…
Why will these components only be available as part of the Suite?
There are two reasons for this change. The first is that with so many separate components, keeping them synchronized was unnecessarily inefficient from a coding standpoint. There’s just too much engineering overhead to maintain them all on separate development tracks. And since we want to be able to develop quickly and get releases out to you more frequently, we made the decision to keep all components in sync as part of a single code base.
The second reason is that it provides much greater opportunities for tighter integration between the products, such as the ability to convert blog posts (or forum posts) to articles, to have forum discussions attached to CMS content, etc.
The whole idea is to make vBulletin better, faster, and these changes will help us develop new features more quickly. They will also help as we dive into the deeper round of rearchitecture with 4.1 and 4.2.
Does that mean I’ll be running lots of extra code?
No. vBulletin runs only the code it needs for any given page load, so if you’re not using a component, its code won’t run and it won’t impact the performance of the application.
Can I turn off components I don’t want to use?
Yep, just turn them off from the Admin CP, and they’ll be disabled.
When? When?? WHEN???
Soon! As much as I would like to be able to provide a hard date, the home stretch to release is the hardest part. However, the biggest team to ever work on vB in its 10-year history is the group that’s working on it now; your vB4 is in very good hands.
That said, I believe that we are within approximately four to five weeks of starting alpha testing. That’s subject to adjustment, of course, but that’s my best estimate as of today.
If you’re on the alpha team, get ready; it’s coming soon.
If you’ve applied to participate in beta, sit tight for a bit. I’ve received a few hundred applications, and I haven’t gotten through them all quite yet.
More to come…
