vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   Reply to thread not functioning after upgrade to 4.1.4 (https://vborg.vbsupport.ru/showthread.php?t=265260)

clubplanet 06-15-2011 08:52 PM

Reply to thread not functioning after upgrade to 4.1.4
 
I'm having some issues with my forum after a recent upgrade.
In chrome, when my users click on "reply to thread" nothing happens. I get a small circular spinning logo in the quick reply area as though it's attempting to load a page but nothing happens.

In IE it DOES work, but it takes FOREVER to load.
Quick reply functions as normal, if the user clicks on "go advanced" in quick reply it functions as normal.
If the users right click on the "reply to thread" icon and copy the URL and paste into the address bar it functions as normal.

Any ideas?
TIA

strudinox 06-15-2011 09:27 PM

I've had some users report this as well. It seems to be random, working for some, and not working for others. I'd also be interested in a fix.

clubplanet 06-15-2011 09:44 PM

Turns out it is a new "feature."

https://www.vbulletin.com/forum/show...ot-functioning

--------------- Added [DATE]1308178686[/DATE] at [TIME]1308178686[/TIME] ---------------

Quote:

Originally Posted by strudinox (Post 2208249)
I've had some users report this as well. It seems to be random, working for some, and not working for others. I'd also be interested in a fix.

Single click works in IE, not in chrome.

I found a way to disable this "feature" though.

Go into showthread and there are two parts in there that cause this. They are new id's that cause the doubleclick thing.

id="newreplylink_top" and id="newreplylink_bottom". With these id's removed, the single click functionality comes back.

After doing that I saw that the "reply with quote" thing still required a double click so I edited my postbit legacy to remove the qrwq_ out of the raw post.posted id.

If you need specific instruction on where the code is and what to remove I can post it later.

strudinox 06-15-2011 10:11 PM

What a pointless feature. I mean who double clicks links on webpages anyways? Thanks for your help!

alfanexus 04-22-2012 10:02 AM

Thanks clubplanet

I removed the reply to thread right after they added this stupid useless feature. But You solution is better. Now I still have the buttons, but they function the way users expect.

I actually had several users who thought the thread was closed or not functioning when they clicked the button and it just scrolled the page down.


All times are GMT. The time now is 01: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.00987 seconds
  • Memory Usage 1,719KB
  • 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)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (5)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
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete