vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin.org Site Feedback (https://vborg.vbsupport.ru/forumdisplay.php?f=7)
-   -   Hack Properties: Min / Max vB Version (https://vborg.vbsupport.ru/showthread.php?t=132282)

akanevsky 11-23-2006 03:40 PM

Hack Properties: Min / Max vB Version
 
The questions like "does this 3.6.0 hack work with 3.6.1" are never going to end, unless... you guys implement a minimum / maximum vbulletin version properties. :) What you say?

RedTyger 11-23-2006 04:20 PM

Isn't it easier to just update a hack's version? I don't do it as soon as vB release a version, but if I've visited a thread to read the question it takes 10 seconds to do it while I'm there.

akanevsky 11-23-2006 04:41 PM

Quote:

Originally Posted by RedTyger (Post 1123733)
Isn't it easier to just update a hack's version? I don't do it as soon as vB release a version, but if I've visited a thread to read the question it takes 10 seconds to do it while I'm there.

No, because the question will then change in the following way:
"Does this 3.6.1 hack work with 3.6.0?"

Marco van Herwaarden 11-23-2006 05:46 PM

The problem is that an author will fill out the info when he releases the modification, and at that time he does not know yet until which version it will work.

Nothing is stopping an author to add a text "This will only work until x.x.x" if he wants.

akanevsky 11-23-2006 05:50 PM

Quote:

The problem is that an author will fill out the info when he releases the modification, and at that time he does not know yet until which version it will work.
Yes he does, at least if he releases the hack using the latest version of vBulletin available. (and why would he do otherwise?).

Marco van Herwaarden 11-23-2006 05:58 PM

But he does not know when the next vB version will be released, what it will be named/numbered or if his modification will still work on that future version.

akanevsky 11-23-2006 06:01 PM

Quote:

Originally Posted by Marco van Herwaarden (Post 1123806)
But he does not know when the next vB version will be released, what it will be named/numbered or if his modification will still work on that future version.

Why would someone be concerned about a future version that has not yet come out? When it comes out, the author can update the hack properties.

Marco van Herwaarden 11-23-2006 07:14 PM

If the author wanted to do that, he could already edit the description and place a line saying "This will only work until version x.x.x".

Since i don't see anyone doing that, i am assuming that it wouldn't be updated if there was a special field or it either. And if there is a field for it, but it is let empty by the author, then a reader would asume that it is still working for the latest released version.

akanevsky 11-23-2006 07:30 PM

Quote:

Originally Posted by Marco van Herwaarden (Post 1123876)
If the author wanted to do that, he could already edit the description and place a line saying "This will only work until version x.x.x".

Since i don't see anyone doing that, i am assuming that it wouldn't be updated if there was a special field or it either. And if there is a field for it, but it is let empty by the author, then a reader would asume that it is still working for the latest released version.

Coders do not do that (or at least I do not do that) because I believe that users do not bother reading through the long introductory posts. They obviously do look at hack properties though since their questions are based on that.

It is not necessary to allow to leave the field blank.

evenmonkeys 11-24-2006 06:46 AM

It's also possible that a modification would work for 3.6.0, 3.6.1, 3.6.4... but it doesn't work for 3.6.2 and 3.6.3. So this wouldn't really work well in that situation. In any case, people will always ask questions that are easily answered by reading the first post; or even reading the title of the thread. I like the idea, but it wouldn't fix every related problem.


All times are GMT. The time now is 02:12 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01129 seconds
  • Memory Usage 1,738KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (4)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (2)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete