There are people with similar problems, I talked to the other techs to find out if we had made any recent changes that might have caused such a problem which is not the case, there's not a specific browser or OS that causes the problem and thanks/likes seem to be working for most, I suggest trying to figure out what you might have done (such as installing/updating a internet security application or browser extension) and what might have caused this on your system yesterday.
I'm having the same problem since a while ago!
well this might be just a random question but i was wondering why i haven't been able to like or thank any post for a while now , any possible reason and solution for that?
To those whose thanks/likes aren't working:
If you're using Firefox, open Web Console by pressing Control-Shift-K. Click right mouse button on console window and enable "Log Request and Response Bodies". Try to thank my post, it will generate a new entry in the console window such as POST http://mangahelpers.com/forum/thanks.php [HTTP/1.1 200 OK 250 ms]. Click on that entry, it'll open a new window with request details. At the bottom of this window, you'll see "Response Body", post the text below it here. It may give us a clue about the source of the problem.
I noticed this stopped working for me as well, so I did as you mentioned...
Clicking like or thank did not create any activity on the console - the last line there was already there before clicking like/thanks and nothing changed after I clicked.
FWIW Firefox 26.0 on Ubuntu 12.04
also tried iPhone4 w/ Safari, no dice.
I know I have liked/thanked posts and I have not been a member too long so change must have been fairly recent. Its possible some of them might have been from computer at work (win7, ie) which I have not tested recently, but I am sure I have thanked/liked from home/phone.
I am only an intermediate techie but if anything I can help with I'll try.
Last edited by TStew; January 04, 2014 at 01:10 AM.
Same results. I started up the console as soon as I reset firefox in safe mode, and it generated lots of activity navigating through mangahelpers but as soon as I loaded into this thread, I got the "The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page."
Maybe its time I try another browser, might help to see if its firefox related. Maybe Chromium? I'll play around with it today.
Last edited by TStew; January 04, 2014 at 03:35 PM.
The weird thing is even if members change their browsers/devices to access MH, they still experience the same problem which leads me to believe the thanks/likes plugin may have some sort of bug. I've performed some maintenance tasks, hopefully it'll fix the problem, at least it worked for some other forum admins. If the problem persists, I'm not sure what we can do other than upgrading the plugin which still may not solve the problem.
Ok so I did install Chromium, and after another reboot still does not work on either FF or CM. My machine has recent updates, but I don't pay attention to whats being updated really, and I usually install the updates on a weekly basis. For all I know its been updated a few times since it stopped working so hard to say what update it could have been if that was the cause. I'll be into work tomorrow, I'll try there.
When you're at it, can you try one more thing? Open Firefox web console (Control-Shift-K) on this page (after the page fully loads) and run this command:
You'll see a new GET entry on the console window.Code:$.getScript("http://mangahelpers.com/forum/dbtech/thanks/clientscript/thanks.js");
Try to thank my post after you run this command, let's see if it'll work.Code:GET http://mangahelpers.com/forum/dbtech/thanks/clientscript/thanks.js [HTTP/1.1 200 OK 150 ms]
Tried the command but nothing different happened.
Havent got a chance to try from work, this winter storm is really making a job crazy busy the last couple days.
Ok, thanks. Possibly one of the other scripts interferes with the correct functioning of the thanks/likes script but it's hard to find the source of the problem without being able to reproduce it. If I can figure out a way that can help solve the issue, I'll try it later.