Topic: [ERROR] Forum inbox [-1#msg.....] (Read 955 times)
Ok , thank you guys ! I will close this topic.
Yeah you're right , I've deactivate the plugin and now it works properly . So at the end it's an adBlock plus problem ?
Yeah Ad block tends to interfere with a lot of things it shouldn't.
Yeah you're right , I've deactivate the plugin and now it works properly . So at the end it's an adBlock plus problem ?
Yes.
Everytime I see a complaint with that symptom it ends up being adblock or some derivative. Run without extensions/addons and see if it happens.
Yeah you're right , I've deactivate the plugin and now it works properly . So at the end it's an adBlock plus problem ?
Everytime I see a complaint with that symptom it ends up being adblock or some derivative. Run without extensions/addons and see if it happens.
Yup, someone has reported a similar problem in Sept https://bitcointalksearch.org/topic/workaround-for-firefox-adblock-clickable-pms-776487 but there is nothing theymos can do to fix it.
redsn0w, if the problem goes away after disabling adblock, you may try the workaround mentioned in that thread.
Everytime I see a complaint with that symptom it ends up being adblock or some derivative. Run without extensions/addons and see if it happens.
By click into a message do you mean reply?
No no , click on the subject of the message. I remember that when I click in a subject it automatically redirects me to the message.
By click into a message do you mean reply?
Hey guys,
I've find an error in the forum inbox ("my messages") , when I click into a message it will appear -1#msg3073002 (in the url bar).
At the end it doesn't redirect me to the message. Is it only my error , can you try ?
Thanks for the attention and I hope theymos can fix this error.
Cheers,
redsn0w
I've find an error in the forum inbox ("my messages") , when I click into a message it will appear -1#msg3073002 (in the url bar).
At the end it doesn't redirect me to the message. Is it only my error , can you try ?
Thanks for the attention and I hope theymos can fix this error.
Cheers,
redsn0w
Jump to: