Testvb Guidelines?

[BulletxxProof89]

I was wondering since I want to host my "Testvb" on a different part of my server if I can host it as such "testvb.domain.tld" instead of "domain.tld/testvb" of course it will still be password protected and what not but I rather not have it in my web root for organizational issues and because my site is highly SEOed and Stat Tracked for every single request. Just wondering if it is possible.

[syrus.xl]

You're licensed to use one copy of vBulletin as a public board. You can install another copy of the same vBulletin as long as it is not publicly available - e.g. in a password protected directory. A locked directory cannot be spidered.

[BulletxxProof89]

Yea well the stats program I use that publically lists all my files and directorys is based on hits, if I hit my own testvb directory it will show in there. Which is what I'm tryin to avoid.

[Dilly]

So long as you put a htaccess file in to password protect the directory, noone will be able to enter it - so it won't matter if it shows in your stats program.

[BulletxxProof89]

Untrue, thats why I'm making this post, if I password protect it, IT WILL 100% SHOW UP IN MY PUBLIC STATS. Thats why I'm asking VBULLETIN TEAM lol

[Dilly]

You're wrong.

From the license agreement.

To make this clear to us and our license verification procedures, place it in a directory called 'testvb' and be sure to password protect it. It must not be accessible by the general public.

If you password protect it, the stats will find it, but it still won't be accessible by the general public because they do not know the password.

[Analogpoint]

You're wrong.

Dilly, I think you need to go back and re-read Bullet's posts. Be sure to understand the difference between a webserver's access log and the stats that are produced by it, and restricting access to a directory.


That being said, Bullet, some stats programs have the ability to ignore hits to certain directories. You could explore that option for hiding a /vbtest directory from the stats program.

[Fusion]

I was wondering since I want to host my "Testvb" on a different part of my server if I can host it as such "testvb.domain.tld" instead of "domain.tld/testvb" of course it will still be password protected and what not but I rather not have it in my web root for organizational issues and because my site is highly SEOed and Stat Tracked for every single request. Just wondering if it is possible.

As I understand it, you'd be okay using testvb.domain.tld, as long as it's clearly identified and linked to the registered domain, and password-protected, as has been mentioned. It cannot be generally accessible to anyone.

But that's my take on it. You'll probably get an official response on Monday. If not, I suggest you open a support-ticket and ask.

[Andy Huang]

You're free to put it on a test domain or even separate test server if you want, but the testvb part needs to stay as a directory. The rule is that it is not allowed to be publicly accessible (password protected using .htaccess + .htpasswd, IIS's user permissions, Active Directory / LDAP etc. anything as long as it is password protected from public), and must be in the /testvb/ directory.

You can consider these if you don't want it interfering with your main domain:

http://dev.site.tld/testvb/

http://testdomain.tld/testvb/

or even: http://localhost/testvb/

[BulletxxProof89]

Thank you for that, thats what I was looking for.

[Dilly]

Dilly, I think you need to go back and re-read Bullet's posts. Be sure to understand the difference between a webserver's access log and the stats that are produced by it, and restricting access to a directory.


That being said, Bullet, some stats programs have the ability to ignore hits to certain directories. You could explore that option for hiding a /vbtest directory from the stats program.

No, I read it correctly. I was saying what needs to happen from the license agreement, not in terms of him not wanting to have it show on stats.

Access needs to be prevented. Visibility does not.

[BulletxxProof89]

Thnx for that reply Dilly, thing is I want total invisability to my testvb, basically my community gets hyped about new features and the chit-chat, rumors, and stuff like that gets pretty insane, not to mention for organization of my server i want to keep it off my main mysql and apache since there under high load. I rather not test cumbersome features on my live server. and stuff of the sorts, i actually had like 10 good reasons to want to move it now that i did i cant remember half of them.... hahaha got my head stuck in the PHP manual... and the API docs...

speaking of which im low on asprin.