Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Isolated spinning wheel issue

  • 1 个回答
  • 0 人有此问题
  • 23 次查看
  • 最后回复者为 BAMimages

more options

Hi

I have admin access to four Wordpress blogs. Three are working fine. But on the fourth blog, when I click on my notifications to access comments that have been left on posts I get a blank screen and a spinning wheel.

The site works fine in other browsers, so the issue lies with Firefox not Wordpress.

I've done all the usual, like clear cache and cookies. I've tried disabling extensions/add ons, although if this were the problem the other three Wordpress blogs would be affected. Nothing makes any difference and I'm still getting the spinning wheel and am unable to access any notifications for this one site.

Firefox is up to date. I use Windows 11.

Any help appreciated as I'm at a loss as to why only this one Wordpress blog is affected or how to solve the problem.

Hi I have admin access to four Wordpress blogs. Three are working fine. But on the fourth blog, when I click on my notifications to access comments that have been left on posts I get a blank screen and a spinning wheel. The site works fine in other browsers, so the issue lies with Firefox not Wordpress. I've done all the usual, like clear cache and cookies. I've tried disabling extensions/add ons, although if this were the problem the other three Wordpress blogs would be affected. Nothing makes any difference and I'm still getting the spinning wheel and am unable to access any notifications for this one site. Firefox is up to date. I use Windows 11. Any help appreciated as I'm at a loss as to why only this one Wordpress blog is affected or how to solve the problem.

所有回复 (1)

more options

p.s. the issue is still there if I start Firefox in Troubleshooting mode.