Wordpress comments and Firefox
I've had this problem since version 44.0, but when I post comments to WordPress (https://wordpress.com/) blogs, what happens is not what is supposed to happen - the comment either automatically posting or saying "awaiting administration" - but the page reloads as if the comment went through, but instead it takes me back up to the top of the page, more particularly to the address bar and the url is the url of the page, but with a "#" sign at the end.
I considered this may be the problem with a particular WordPress blog, so I wrote the creator. He told me he hadn't blocked me and that other's comments were coming through. So, I've seen been on other pages, but the same problem occurs. All I can think of is that it must be a particular personal Firefox setting or the browser as a whole.
Anyone else having this problem?
Избрано решение
I never found any way to get off the Akismet "list" once you're on it.
Прочетете този отговор в контекста 👍 0Всички отговори (20)
Many site issues can be caused by corrupt cookies or cache.
- Clear the Cache and
- Remove Cookies
Warning ! ! This will log you out of sites you're logged in to.
Type about:preferences<Enter> in the address bar.
- Cookies; Select Privacy. Under History, select Firefox will Use Custom Settings. Press the button on the right side called Show Cookies. Use the search bar to look for the site. Note; There may be more than one entry. Remove All of them.
- Cache; Select Advanced > Network. Across from Cached Web Content, Press Clear Now.
If there is still a problem, Start Firefox in Safe Mode {web link} While you are in safe mode;
Type about:preferences#advanced<Enter> in the address bar.
Under Advanced, Select General. Look for and turn off Use Hardware Acceleration.
Poke around safe websites. Are there any problems?
Then restart.
This does not solve my problems. Where it asks for a commenter to leave a reply, I type in my emails address and screenname I want to use. After I post the comment, this is what is shown at the url on the page after I press "post comment."
- comment
See if this helps; https://support.mozilla.org/en-US/kb/update-firefox-latest-version 46.0.1
Use this link to check that your plugins are up-to-date. If any are listed as unknown or research, do not worry about them.
FredMcD said
See if this helps; https://support.mozilla.org/en-US/kb/update-firefox-latest-version 46.0.1
Use this link to check that your plugins are up-to-date. If any are listed as unknown or research, do not worry about them.
Huh? I always keep my Firefox and its add-ons updated. Is this some kind of joke?
FireFoxFan1 said
After I post the comment, this is what is shown at the url on the page after I press "post comment."
#comment
The #comments at the end of the URL should cause Firefox to scroll to the comments section of the page. That sometimes fails. After the page loads, if you click in the address bar and press Enter, does Firefox jump to the comments? If your comment there?
jscher2000 said
FireFoxFan1 saidAfter I post the comment, this is what is shown at the url on the page after I press "post comment."
#commentThe #comments at the end of the URL should cause Firefox to scroll to the comments section of the page. That sometimes fails. After the page loads, if you click in the address bar and press Enter, does Firefox jump to the comments? If your comment there?
No, it doesn't jump down to the comments. And, no, my comments never show up, which is the problem.
When I make the comment and post it, I'm taken back to the top of the page, and that's it. The only other change is the #comment in the url.
I use WordPress, but on my own site. Can you post a comment: http://www.jeffersonscher.com/ttw/ ?
You might want to open the Browser Console first to collect any error messages that appear when you submit the comment. Either:
- menu > Developer > Browser Console
- Ctrl+Shift+j
Once the console stops adding messages, click the Clear button at the top. Then leave that window open and switch back to the blog, enter and submit your comment, and then check the console for any error messages. You may see style rule warnings with little blue triangles, you can ignore those.
(Note: on my blog any post with a link goes to moderation.)
FireFoxFan1 said
I always keep my Firefox and its add-ons updated
Your system details shows;
Application User Agent: Mozilla/5.0 (Windows NT 6.1; rv:46.0) Gecko/20100101 Firefox/46.0
The current is 46.0.1
Hi FredMcD, Firefox masks the user agent string to only show the major version. We only can tell the point level accurately if the poster uses the Share Data button while submitting the question. It doesn't seem to be the case here (no extensions listed, etc.).
jscher2000 said
I use WordPress, but on my own site. Can you post a comment: http://www.jeffersonscher.com/ttw/ ? You might want to open the Browser Console first to collect any error messages that appear when you submit the comment. Either:Once the console stops adding messages, click the Clear button at the top. Then leave that window open and switch back to the blog, enter and submit your comment, and then check the console for any error messages. You may see style rule warnings with little blue triangles, you can ignore those. (Note: on my blog any post with a link goes to moderation.)
- menu > Developer > Browser Console
- Ctrl+Shift+j
Thank you. I've tried posting to your blog. The only thing I get is:
JQMIGRATE: Migrate is installed, version 1.4.0
This is repeated twice. It doesn't appear to be an error.
FireFoxFan1 said
Thank you. I've tried posting to your blog. The only thing I get is:
JQMIGRATE: Migrate is installed, version 1.4.0
This is repeated twice. It doesn't appear to be an error.
I agree, that doesn't seem to be an important message.
Like most people, I use the Akismet anti-spam filter from WordPress. It threw all 3 of your comments into spam. I'm going to unmark them. See whether that lets you post now or whether it happens again.
jscher2000 said
FireFoxFan1 saidThank you. I've tried posting to your blog. The only thing I get is:
JQMIGRATE: Migrate is installed, version 1.4.0
This is repeated twice. It doesn't appear to be an error.I agree, that doesn't seem to be an important message.
Like most people, I use the Akismet anti-spam filter from WordPress. It threw all 3 of your comments into spam. I'm going to unmark them. See whether that lets you post now or whether it happens again.
Thanks. It does appear it went through this time. That's weird because the other wordpress blog I posted to and contacted told me that my I hadn't been treated as spam. Maybe they were lying. Should I try a few others?
What could be the cause of me being treated as spam if that is what's happening? I tried using different email addresses on the other board, but that didn't seem to work. Could it be every email service I'm using is marked as spam?
I don't know how Akismet works. Based on what you tried, maybe it doesn't like your IP address?
jscher2000 said
I don't know how Akismet works. Based on what you tried, maybe it doesn't like your IP address?
Can you kick this to the higher-ups? BTW, I vaguely remember renewing my IP address, but do you know how to do that? Do you think that may help?
Are you saying this is a Firefox-only problem, you can comment on these same blogs using another browser? Possibly Akismet cares what browser you use, but either way, this is determined on the server side and isn't something Mozilla could fix.
Your IP address is associated with your internet connection, either home ISP, wi-fi hotspot, private VPN, or other connection. If you have inherited a bad IP address which is associated with abuse by a former user, maybe your ISP will assign you a new one.
jscher2000 said
Are you saying this is a Firefox-only problem, you can comment on these same blogs using another browser? Possibly Akismet cares what browser you use, but either way, this is determined on the server side and isn't something Mozilla could fix. Your IP address is associated with your internet connection, either home ISP, wi-fi hotspot, private VPN, or other connection. If you have inherited a bad IP address which is associated with abuse by a former user, maybe your ISP will assign you a new one.
How would I go about doing that? I'd think had I been marked for abuse of the address that they would have contacted me, or if I inherited a bad address that I'd have problems on other sites and kind of sites. This only seems to be happening with Wordpress.
I'm just curious what you think the problem is. Don't you find it strange that everything I posted even to you seems to be sent to spam, but that when you looked and removed something you could see my messages?
What does that mean?
The Akismet service allows individual sites to make exceptions to its rules. So on my site, you are no longer treated as a spammer, even if other WordPress sites using Akismet still treat you as a spammer. When I check spam on my site, it's never borderline/questionable, it's always extreme, so in this case, I don't think Akismet has a problem with your comment, but instead your email address or IP address. Other than that, you now know as much as I do.
Променено на
jscher2000 said
The Akismet service allows individual sites to make exceptions to its rules. So on my site, you are no longer treated as a spammer, even if other WordPress sites using Akismet still treat you as a spammer. When I check spam on my site, it's never borderline/questionable, it's always extreme, so in this case, I don't think Akismet has a problem with your comment, but instead your email address or IP address. Other than that, you now know as much as I do.
I was just posting to another Wordpress site, again, and this is still happening.
Избрано решение
I never found any way to get off the Akismet "list" once you're on it.
jscher2000 said
I never found any way to get off the Akismet "list" once you're on it.
Jscher,
I did a bit more research, and was able to find this form where you can contact Akismet about problems like this:
Hopefully, they will be able to help. I guess this isn't a Firefox issue, but perhaps this could help people with similar questions in the future to rule out the browser as the cause.