The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
|||
|
|||
How is it hypocritical? Unless I am missing something, vB.org or vB in general has never stated that you cannot hack your forums. Likewise, vB.org isn't releasing any coding they've used to "hack" these forums. So, the same rule applies to them as it does us.
Besides, these guys are professionals and work for Jelsoft. Of course they should have special benefits in comparison to others. |
#12
|
|||
|
|||
There is no point releasing hacks for a beta product IMO, there are going to be code changes and whatever before the RC is released so any hacks you create now either may not work on the RC or will use code which is out dated. Not very hard to understand, and I would feel the same way about any other beta product.
And obviously vBulletin.org/.com want to be running their own software on their site, if they choose to install any added extra's themselves it's up to them! You can do the same to your vB3 board, no one has ever said they _have_ to share any code they have created above the actual vBulletin product. |
#13
|
|||
|
|||
In a way it is hypocritical, but vB.org needs it to run properly. It's their decision to upgrade now, and you don't have any say in that decision. You should use this spare time to create hacks for vB3, so that when vB3 hacks are supported here, you can upload them
|
#14
|
||||
|
||||
ach i dont mind.. ive got a ew hacks im not wanting to share on my forums.. there no reason for vb.org to not be allowed that chance. I think its there choice what end users see, its not like your subscribing to a hack db is it?no so just wait.
If vb.org needs to do some hacking then let em.. i think as part of the vb enterprise its fine. No doubt if there was no portal etc up then you be complaining about that, |
#15
|
||||
|
||||
Like Xenon and filburt1 said, this was not a decision by vB.org staff - it was a decision by Jelsoft, and since vB.org is an official vB site, we stand by that decision, and fully understand and support it. Personally, I don't care if vB3 hacks are released. But Jelsoft cares, so we abide by their decision.
Allowing the release of hacks while the program is beta will make bug reporting and fixing virtually impossible for hacked boards. |
#16
|
||||
|
||||
Quote:
|
#17
|
||||
|
||||
Either way I don't really care. I don't have a board anymore anyways, I'm just saying what was on my mind at the time.
I still think my suggestion in Site Feedback should be considered. |
#18
|
||||
|
||||
I can understand both sides but bug testing in beta stages is important so i understand why JS dont want people hacking a beta version. Its not going to be to much longer for the RC anyways
|
#19
|
||||
|
||||
BTW. a small note that the discussion is irrelevant for a "front page portal" which started it in the first place.
If carefully coded, a front page portal would be an add-on and could be created without hacking any VB files so if abides by this rule, there is no rule around that prevents anybody to share his VB3 front page portal here in vb.org. If this hasn't been done yet, do not blame the no hacking rule. |
#20
|
|||
|
|||
Quote:
(Of course, I look forward to the "real" hacks that I know will be forthcoming, but a front page portal would make the wait SO much easier to handle) |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|