"Authentication Required" box displaying in the New SiteBuilder

  • 1
  • Problem
  • Updated 5 years ago
  • Solved
In using New SiteBuilder for working on my blog for my site today, in the combi of Mozilla Firefox 20.0.1 in WindowsXP Professional (to aid in server debugging), I encountered at least twice the alert "Authentication Required--Enter your username and password for helplines4u.com."

Suspecting such was a bug, I closed the alert.

I'm not sure if this may be a bug on your end vis-a-vis New SiteBuilder, or if others as are using same have encountered the bug; hence, my bringing this up at this time for a possible enquiry.

Your timely attention would be greatly appreciated.
Photo of Exaggerator

Exaggerator

  • 50 Posts
  • 2 Reply Likes

Posted 5 years ago

  • 1
Photo of Stefan

Stefan, Official Rep

  • 4448 Posts
  • 190 Reply Likes
Hello Exaggerator

Can you please specify what the exact steps are when this error occurs? So you open your website in the Sitebuilder, go to the blog page, and then? Does the error always occur, or just once in a while? I'd like to try and replicate.

Also, I've noticed that there is a lot of custom code on your pages, embedding third party services. It is possible that one of these widgets causes the problem.
Photo of Exaggerator

Exaggerator

  • 50 Posts
  • 2 Reply Likes

Can you please specify what the exact steps are when this error occurs? So you open your website in the Sitebuilder, go to the blog page, and then? Does the error always occur, or just once in a while? I'd like to try and replicate.

Basically, you described it exactly--open the New SiteBuilder, go to my blog page, and then the "Authentication Required" alert displays.
Photo of Stefan

Stefan, Official Rep

  • 4448 Posts
  • 190 Reply Likes
Hello Exaggerator

I've tried to replicate this error on a WinXP machine, using Firefox 20, but everything worked fine for me.

Judging from the text of the message you're getting which includes a URL to another website, I'd assume that this is caused by one of your widgets where you added custom coding. Unless we get more of the same reports from other users, I'm afraid that we don't have the capacity to check which of your custom elements is causing this. The only way to find out would be to save your blog page as a test page, then remove widget by widget to see when the error stops.
Photo of Exaggerator

Exaggerator

  • 50 Posts
  • 2 Reply Likes
I didn't encounter this problem yesterday; hence, it may be safe to suggest that the case be closed.

As well, one custom-coded widget was deleted, per your suggestion.