vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.6 Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=194)
-   -   Show Thread Enhancements - [AJAX] Post Groan Hack (https://vborg.vbsupport.ru/showthread.php?t=129975)

itsblack 04-06-2007 07:23 PM

OK, I see. Thank you.

Tulsa 04-06-2007 11:11 PM

Anyone that may have made some adjustments in their groan templates, like I did to reduce the font size, remember you'll have to revert that template and make your change again or the groaned from member names won't show up in the table.

NolF 04-07-2007 10:17 AM

Found an error Abe, on line 334 of post_groan_admin.php
it says delete_groans($postinfo, $userid);
while on functions_post_groan.php (includes folder) on line 359 it says function delete_groan($postinfo, $userid)

as you can see, the second one is missing an s, therefor the mass delete groan function doesn't work ^^

-----
After some more testing, I think that the post_groan_admin.php is the one with the extra s

Abe1 04-08-2007 01:26 AM

Version 3.0.1 (04/07/07):
  • Fixed a bug in the post_groan_admin.php file. No other changes. Official version is still 3.0.

BozzaJos 04-25-2007 11:26 AM

Does anyone know if this hack also works for 3.5? I know there is a Post Groan Hack for 3.5 but it hasn't been updated for a long time so I bet a lot of features won't be included in that one or am I wrong?

Abe1 05-14-2007 11:17 PM

Version 3.1 (05/14/07):
  • No more template edits You do not have to make any template edits to run this hack.
  • better cache of templates
  • vBulletin 3.6.6 and up is needed to run this version
  • Fixed extra queries from running if you had no thanks on a page.
  • Fixed deleting all of a users thanks.
  • A few more tweaks here and there.

Tulsa 05-14-2007 11:25 PM

Do we need to remove the template edits we've made?

Abe1 05-14-2007 11:27 PM

Quote:

Originally Posted by Tulsa (Post 1247699)
Do we need to remove the template edits we've made?

If you would check the email sent out, I said yes.

redlabour 05-15-2007 05:53 AM

BUG at 3.1:

The Button appears at the wrong direction after the Quickreply Button!

Abe1 05-15-2007 11:42 AM

Quote:

Originally Posted by redlabour (Post 1247864)
BUG at 3.1:

The Button appears at the wrong direction after the Quickreply Button!

Not a bug.

vB placed the '$template_hook[postbit_controls]' there. You can move it right under '<!-- controls -->' if you'd like.


All times are GMT. The time now is 08:07 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.01161 seconds
  • Memory Usage 1,734KB
  • 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
  • (2)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)pagenav_pagelinkrel
  • (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