საიტის გასაუმჯობესებელი სამუშაოების მიმდინარეობისას, შესაძლებლობების ნაწილი შეიზღუდება. თუ სტატიით ვერ მოახერხებ ხარვეზის გამოსწორება და შეკითხვის დასმა გსურთ, ჩვენი მხარდაჭერის გუნდი დაგეხმარებათ @FirefoxSupport გვერდის მეშვეობით Twitter-ზე და /r/firefox განყოფილებაში Reddit-ზე.

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

Can't post comments on blogspot-hosted blogs

  • 2 პასუხი
  • 1 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 5 ნახვა
  • ბოლოს გამოეხმაურა cpenny86

I am unable to post comments on blogs hosted at blogspot.com or running their software on a custom domain. I have no issue with blogs that are hosted on wordpress.com or using their software.

What happens: I can fill in the comment box and other fields as usual. When I hit "submit", "publish", or "preview" everything in those fields disappears. They aren't being held in a moderation queue; they aren't going through to the website at all.

My add-ons are AdBlock and Privacy Badger. I don't think it's a mixed-security issue as the green icon in the location bar shows that I have a secure connection in all cases. It is not being caused by my pop-up blocker as the comment forms in these cases are embedded within the main site, not pop-ups.

Any insight you may have would be appreciated.

I am unable to post comments on blogs hosted at blogspot.com or running their software on a custom domain. I have no issue with blogs that are hosted on wordpress.com or using their software. What happens: I can fill in the comment box and other fields as usual. When I hit "submit", "publish", or "preview" everything in those fields disappears. They aren't being held in a moderation queue; they aren't going through to the website at all. My add-ons are AdBlock and Privacy Badger. I don't think it's a mixed-security issue as the green icon in the location bar shows that I have a secure connection in all cases. It is not being caused by my pop-up blocker as the comment forms in these cases are embedded within the main site, not pop-ups. Any insight you may have would be appreciated.

გადაწყვეტა შერჩეულია

Hi cpenny86, have you tested with your content blockers disabled to rule them out?

I don't want to post a "TEST" comment if I can help it, and I noticed different blog templates are set up differently anyway, so hopefully you can look into this a little more deeply. In particular, maybe you could try checking for error messages in the Web Console. Here's how:

Open the Web Console in the lower part of the tab using either:

  • "3-bar" menu button > Web Developer > Web Console
  • (menu bar) Tools > Web Developer > Web Console
  • (Windows) Ctrl+Shift+k

Then try clicking the Preview or Publish button again. Any interesting new messages in the Web Console? Sometimes it's helpful to reload the page and then testing again. Before doing that, click the "Persist Logs" checkbox above the right end of the console so you can keep all the context together.

პასუხის ნახვა სრულად 👍 1

ყველა პასუხი (2)

შერჩეული გადაწყვეტა

Hi cpenny86, have you tested with your content blockers disabled to rule them out?

I don't want to post a "TEST" comment if I can help it, and I noticed different blog templates are set up differently anyway, so hopefully you can look into this a little more deeply. In particular, maybe you could try checking for error messages in the Web Console. Here's how:

Open the Web Console in the lower part of the tab using either:

  • "3-bar" menu button > Web Developer > Web Console
  • (menu bar) Tools > Web Developer > Web Console
  • (Windows) Ctrl+Shift+k

Then try clicking the Preview or Publish button again. Any interesting new messages in the Web Console? Sometimes it's helpful to reload the page and then testing again. Before doing that, click the "Persist Logs" checkbox above the right end of the console so you can keep all the context together.

Ah! It appears to have been Privacy Badger at work. I have sent them a bug report. Thank you!