vB3 Hacks

[filburt1]

This is just a reminder: while vB.org has now upgraded to vB3, you still may not discuss or post vB3 hacks publicly here. Such discussion will be allowed starting with the vB3 RC (release candidate).

[TheEDIGuy]

This is just a reminder: while vB.org has now upgraded to vB3, you still may not discuss or post vB3 hacks publicly here. Such discussion will be allowed starting with the vB3 RC (release candidate).
It bothers me a little that vb.org is able to design (or adapt) a front page portal for the vB3 site, but is unable to either release it or help other vBulletin owners do the same.

Maybe it's just me.

[Erwin]

It bothers me a little that vb.org is able to design (or adapt) a front page portal for the vB3 site, but is unable to either release it or help other vBulletin owners do the same.

Maybe it's just me.
Why should that bother you? We also had the licensing system, the hack database, the hack installation system, and lots of other code that has not been released since they are proprietary code, and not for public release. Many hacks have been released, and some have not.

[Logikos]

i not mad at all, i would be if vb3 was out of beta, but not now. And i dont seem to see the hacks database yet. Im sure your still in the middle of coding it

[TheEDIGuy]

Why should that bother you? We also had the licensing system, the hack database, the hack installation system, and lots of other code that has not been released since they are proprietary code, and not for public release. Many hacks have been released, and some have not.
I guess it shouldn't. But seeing that vBulletin 3.0 is apparently stable enough for both vBulletin's own support forum and vBulletin.org's forum to be run on it, and their active discouragement of anything requiring code change to even be discussed anywhere, much less released, has me a littel depressed.

Combine that with the fact that vb.org hackers are apparently confident enough in the stability of the vb3.0 code to create a front page portal system for vb.org itself, but still won't allow anyone to publish similar code modifications, and you may begin to see where I'm coming from.

If it's stable enough for you guys to hack, it should be stable enough for the rest of the hackers to start publishing code. That's all I'm saying.

But, I'll climb back in my shell until RC is out. After all, it was my decision alone to upgrade early, although I wanted to be part of the debugging process.

[filburt1]

I guess it shouldn't. But seeing that vBulletin 3.0 is apparently stable enough for both vBulletin's own support forum and vBulletin.org's forum to be run on it, and their active discouragement of anything requiring code change to even be discussed anywhere, much less released, has me a littel depressed.

Combine that with the fact that vb.org hackers are apparently confident enough in the stability of the vb3.0 code to create a front page portal system for vb.org itself, but still won't allow anyone to publish similar code modifications, and you may begin to see where I'm coming from.

If it's stable enough for you guys to hack, it should be stable enough for the rest of the hackers to start publishing code. That's all I'm saying.

But, I'll climb back in my shell until RC is out. After all, it was my decision alone to upgrade early, although I wanted to be part of the debugging process.
The whole point of a beta is to find bugs. You'll notice that practically nothing has been hacked here except for the license system; likewise at vB.com. Hacking now completely destroys the effectiveness of the beta program because foreign code completely changes the product.

[FWF]

im happy to see vb.org running smooth on 3.0.0 Beta i cant wait for the R C its going to be nice.

[Link14716]

That's hypocritical at best. No one may post or discuss vB3 hacks, which means that naturally you do not encourage hacking the beta. Yet vB.org is running vB3 Beta 6, and using hacks to power it. Yes, the license system is needed, as is the installed/uninstalled hacks, and obviously the portal is great as well. But that is still no excuse to be hypocritical.

Oh well.... *cough**cough*vbulletin.nl*cough*

Just my $.02.

[filburt1]

That's hypocritical at best. No one may post or discuss vB3 hacks, which means that naturally you do not encourage hacking the beta. Yet vB.org is running vB3 Beta 6, and using hacks to power it. Yes, the license system is needed, as is the installed/uninstalled hacks, and obviously the portal is great as well. But that is still no excuse to be hypocritical.

Oh well.... *cough**cough*vbulletin.nl*cough*

Just my $.02.
It wasn't my decision. I was offered to post the announcement and I did. You'll have to take your complaints to a manager of Jelsoft because we're merely their pawns.

[Xenon]

As filburt said already, it wasn't our descision.
vb dev's have asked us and as we want to support them, we don't allow vb3 hacking until RC.

Of course hacking itself is allowed, but not releasing it on vb.org now.

Regarding vb.org: we've just hacked in what's absolutely needed on vb.org, nothing more.
All "special" hacks will appear with RC, as it's also easier for us, regarding upgrades et al.

but as already said, we just try to help vb3 devs, so talk to them if you're not content with the actual situation :)

[WEForums]

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.

[Gavin B.]

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. :)

[Alcar Lazuli]

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 :)

[colicab-d]

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, :p

[Erwin]

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.

[Tony G]

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.
I believe without the hacking, the bug reporting process moves alot faster and in the end new versions are released faster with non-hacked beta forums. :)

[Link14716]

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.

[SnowBot]

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 :)

[Logician]

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.

[TheEDIGuy]

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.
I appreciate you pointing that out, Logician, and I hope that some entrepreneurial vB guru takes that offer to heart.

(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)

[Toky0]

Allowing the release of hacks while the program is beta will make bug reporting and fixing virtually impossible for hacked boards.

This is why people, we have "beta" versions. If they release a RC and its buggy people will complain. Sit tight and be patient.

[cka]

What about the crontab scripts I suggested a few months back? Technically, they're not hacks... ;)

[Xenon]

hmm, technically you're right here, so i think they're allowed. we'll discuss this :)

[Zach]

I can understand this, though the biggest loss is the community in general as people like myself hack things and move on, this time I was planning on writing everything down and throwing it out there, but I am a then and now person...so I do my hacks like I did before and like before they just sit in hiding in some little hole in the web because I am to busy to go back and figure out what I did and write it up so it makes sense.

[SmEdD]

hmm, technically you're right here, so i think they're allowed. we'll discuss this :)

And add ons that don't touch vB code are allowed right? I wanna put my Clan Tools hack in Beta and it only touches a few files but I can make it so it dosn't till RC.

That would be wicked if we could as I have seen some already.

[Ky Kiske]

I am such a vb newbie this whole thread flew right over my head.

[C.Birch]

And add ons that don't touch vB code are allowed right? I wanna put my Clan Tools hack in Beta and it only touches a few files but I can make it so it dosn't till RC.

That would be wicked if we could as I have seen some already.


You can post vb3 ADDON'S because i have done so with the messenger and one of the admin/mods send me a pm and asked if it was a hack or a addon so i said addon because it is so it was ok all i was asked to do was say it the topic that its a addon and does not edit any vb files or database.

[SmEdD]

You can post vb3 ADDON'S because i have done so with the messenger and one of the admin/mods send me a pm and asked if it was a hack or a addon so i said addon because it is so it was ok all i was asked to do was say it the topic that its a addon and does not edit any vb files or database.

Do you know if new templates will consider it a hack? No templates are edited but a couple are added.

[filburt1]

Do you know if new templates will consider it a hack? No templates are edited but a couple are added.
People, this is not open to discussion at the moment. Any discussion of or actual code modification or extension of vBulletin 3 beta is not allowed here. Sorry, but you'll have to wait until the RC. It's not that long a wait, and by not hacking, you will have a stable base on which to hack later.

[Toky0]

By not hacking, you will have a stable base on which to hack later.
Exactly my point for not hacking my board. Not only that if they change files that you hacked in the RC. Then you'll have to rewrite the code anyway.

[C.Birch]

Do you know if new templates will consider it a hack? No templates are edited but a couple are added.


I can not see there being a prob with that as your not editing any code or anything but your best asking a admin.