Mod un-editable to supporters/co-authors?
 

Alright, I'm not sure if this have ever been posted but it has come to my attention that supporters and/or co-authors of a specific hack are NOT allowed to edit and update a hack. Any idea why? You see, I'm already a supporter/co-author of a specific hack but aren't I supposed to have the ability to edit and update the hack, too? Otherwise what would be the use of the co-author/supporter thing?

Yes this has already been posted and no vbulletin.org won't implement anything for this

So what's the point in having that feature then, huh? I just don't get it.

I don't either. I guess to PM the co-author/supporter. Thats my only thought

I've brought this up before, too. In fact, there is absolutely no way to share, transfer, or otherwise collaborate on hacks on vb.org. It would actually appear from the feedback I've seen so far that vb.org, and perhaps Jelsoft itself frowns on developer cooperation for fear it will cause them extra work in some way.

Well, I'm not really impressed about this whole thing, you know. It's always a great idea to be able to edit, update, etc. hacks wherever you're the co-author/supporter of that hack. Can this ever be considered in the future, I hope?

However good or desirable this may be, it's unlikely to ever happen. Modifications are threads in a forum - and the whole way that forums work is that they are only editable by the thread/post owner (or by moderators). Changing this basic fact would mean a fair amount of work messing with a number of files and permissions, which is not something to be taken lightly - the potential for breaking something, or opening permission holes, outweighs the small potential gain (very, very few mods have real co-authors).

So the message: if some coder creates a very good hack to make this possible, vB.org might adopt this :D

Another thing: could it be possible for supporters/co-authors to see at least who installed the modification?

We would certain look at how such a system worked, that doesn't mean we would use it thoiugh. One thing to remember is that we avoid file edits as much as possible (I think we have three atm, which will hopefully drop to two when we move to 3.6.6 as it has at least one new hook we can use).

I assume you mean in the postbit ? - from memory on how that works then I don't think that would be too hard to implement, I'll take a look at some point.

I understand that fully, I do the same on my site to make upgrades painless. I'm going to look into this after my exams :D

Indeed, that's what I mean. It would be a really nice feature for supporters/co-authors.