The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Is shoudl be absolutely mandatory to put which line to find the sought code
The most annoying thing when installing a hack is when the programmer neglects to say which line in a file the code that needs to be raplced is found. In a file with thousands of lines it could take 5-10 minutes of searching. It would take a mere 5 secs to put this info into the hack readme. Why don't they do this? The worst is when not only is there no line # but the code mods are not even in chronalogical order!!!
VB.org should make this a mandatory thing when posting a hack. Do you know how many hours you'd save people? |
#2
|
||||
|
||||
This is due to one thing, say if you have a highly hacked global.php and they do not, they could say line 89 and yours would be 230.
So most use a find this method which is very easy to do via a find option as it is with a line number. |
#3
|
|||
|
|||
You know all this time and I didn't even realize I coudl search a file for a line of code.
Anywyas I still think that more often than not it might help people. Most forums probbaly are not hacked too much. |
#4
|
||||
|
||||
You may be shocked, and thankfully with the new vBulletin many code hacks are no longer needed thanks to the hook system.
But I remember old threads in vB 2 where they would put line numbers and half the replys where people who could not find them. |
#5
|
|||
|
|||
Quote:
|
#6
|
|||
|
|||
Even small hacks are enough to mess up the line numbers to the point that they become useless. Searching for the code itself is the best way.
|
#7
|
||||
|
||||
Quote:
How hilarious. |
#8
|
||||
|
||||
Quote:
|
#9
|
||||
|
||||
Ctrl+f is my friend
|
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|