The Arcive of vBulletin Modifications Site. |
|
|
#1
|
|||
|
|||
|
Do you really mean that a vB 3.5 and a vB 3.6 versions of the same hack should have different productids even if they are not much different or if they are not different at all? I don't think so. Why is it not permitted to define the same productid for two release threads?
|
|
#3
|
|||
|
|||
|
Quote:
|
|
#4
|
||||
|
||||
|
Maybe in the future we'll look at allowing an author to have duplicates (but no duplicates across authors), but it's a low priority request. Only 3.6 mods really need a productid atm as product links and version checking don't exist in older versions, so it's not a big issue.
|
|
#5
|
|||
|
|||
|
Quote:
You know what, now that I think about it - don't change it. The product id URL is more efficient. |
|
#6
|
||||
|
||||
|
There is no such feature as version checking in vB 3.5.
|
|
#7
|
|||
|
|||
|
Oh. Yes. I forgot about it. LOL.
|
|
#8
|
||||
|
||||
|
But there is a hack that allows it
|
|
#9
|
||||
|
||||
|
I apologise for the bump across the years, couldn't find a more recent appropriate thread. But would it be fair to say that this is more of an issue now? It's not just for 3.6 mods any more, worst case scenario is four different copies of a modification for the sake of two lines in a file and no better cross-version method of release.
|
|
#10
|
||||
|
||||
|
So I take it that multiple file versions will be the way to go for the forseeable future?
|
![]() |
|
|