vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin.org Site Feedback (https://vborg.vbsupport.ru/forumdisplay.php?f=7)
-   -   Suggestion for Hack Creators (https://vborg.vbsupport.ru/showthread.php?t=50196)

assassingod 05-27-2003 09:29 PM

Actually I believe they aren't in the forum.

I'm not sure but dont certain hacks older than x amount of days disappear?

Logician 05-28-2003 07:31 AM

I don't know Erwin and Stefan would want to bother with further hacking of Hack DB but IMO:
a) Hack DB search should be using a different algorithm and it should be possible to remove 3 letter restriction for hack DB searches only. Since hack db has very few records (compared to huge post db), it will return results in a blink even you search single letters.
b) In hack db search form I believe that either:
i) * are appended in the keyword automatically.
or
ii) There should be a checkbox (selected by default!) to decide whether to append * in the keyword.
or
iii) At least a warning&info line about wildcards..

The existing searches are confusing and does not return any results for many users, not only newbies.

For instance when you are searching for my Birthday Greeting hack, very surprisingly neither "birthday" nor "greeting" returns any results because script waits you to enter "birthdays" or "greetings" as hack title is plural. This is very confusing to everybody and I strongly believe that appending wildcards should be automatic to avoid such confusions.

This applies to all hacks where hack title keywords are not seperated with space. For instance there is no way for you to match hack "Fast Access to Visibility/Invisibility" if you search "visibility" or "invisibility" (because they are not seperated by space but /). Or keywords "Webtemplates" does not return you hack "WebTemplates: Your Vbulletin powered non-vb pages" as it has a : appended in the word webtemplates.

I learned these tricks and now naming my own hacks more wisely (like using name "WebTemplates : Your Vbulletin powered non-vb pages") instead of "WebTemplates: Your Vbulletin powered non-vb pages"), but well how many other author's are careful about it anyway?

I think this is one of the reasons why we are having so many "I know it exists but I couldn't find hack X" posts in requests forum.. :)

Xenon 05-28-2003 10:05 AM

we won't hack up the hack db anymore like Logician said.
We really have a lot to do, believe us ;)

with vb3 we have to rewrite the whole hack system, so, we will see how we can avoit such problems :)


All times are GMT. The time now is 05:04 PM.

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.01181 seconds
  • Memory Usage 1,716KB
  • 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
  • (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
  • (3)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