Also, please see this:
http://wordpress.org/support/topic/215395


On 20 Jan., 08:47, Saphod <[email protected]> wrote:
> Hmmm....
>
> Onhttp://www.w3schools.com/php/php_ajax_xmlhttprequest.aspit says
> that it is the way to make am AJAX request. The problem - as always -
> is that there are 2 possible ways depending on which browser is being
> used (FF or IE).
>
> I must admit: I am having some trouble reproducing the error right
> this instant - everything is fine. But that's what it was before. It's
> hard that it just doesn't appear each time, that makes it harder to
> track it down.
>
> Maybe you are right. I can remember that issue being mentioned within
> the Javascript console of Firefox, also - I guess. So, if Firebug only
> reproduces the messages of the JavaScript console, then indeed it
> shouldn't be a Firebug issue.
>
> What amazes me is that I never had that issue before, it kind of
> "suddenly" arose.
>
> On my website post, a visitor made a comment that he changed the order
> of this AJAX request within the createAJAX function of tw-sack.js to
> first check for Firefox and then for IE, and that it helped preventing
> the error.
>
> I am still not convinced to believe that the problem lies within a
> JavaScript code that is so heavily used. But maybe I will address the
> author of that JavaScript.
>
> Thanks jjb, I will try to keep you updated here.
>
> Kind regards
> Marco
>
> On 20 Jan., 00:02, John J Barton <[email protected]> wrote:
>
> > The line with the error message is, according to your pages:
> > this.xmlhttp = new ActiveXObject("Microsoft.XMLHTTP");
> > It's not valid code, so it gives an error.  Not a great message I
> > agree. But the error messages are given by Firefox, not by Firebug.
>
> > What do you see in Firefox > Tools > Error Console when you see the
> > message in Firebug?  I guess the same message?
> > jjb
>
> > On Jan 19, 2:45 pm, Saphod <[email protected]> wrote:
>
> > > Please have a look at the website link provided and the comments.
> > > I also posted an issue on the fbug site.
>
> > > Thousands of bloggers are using WordPress, I think the code should be
> > > valid.
> > > Haven't had this problem in Firebug 1.2.1 (or similar - the one before
> > > 1.3.0).
>
> > > Kind regards
> > > Marco
>
> > > On 19 Jan., 15:57, John J Barton <[email protected]> wrote:
>
> > > > Please include some information on why you think this is a Firebug
> > > > problem.  Based on what you have posted here and the bug report, it
> > > > looks like a site error.
> > > > jjb
>
> > > > On Jan 19, 2:11 am, Saphod <[email protected]> wrote:
>
> > > > > Thanks - I started a new issue 
> > > > > #1396:http://code.google.com/p/fbug/issues/detail?id=1396
>
> > > > > On 19 Jan., 05:33, John J Barton <[email protected]> wrote:
>
> > > > > > There several bug reports involving 
> > > > > > wordpress:http://code.google.com/p/fbug/issues/list?can=2&q=wordpress
>
> > > > > > jjb
>
> > > > > > On Jan 18, 2:56 pm, Saphod <[email protected]> wrote:
>
> > > > > > > Hi,
>
> > > > > > > I am using WordPress, and I always get a "Components is not 
> > > > > > > defined"
> > > > > > > error whenever the SACK functionality (AJAX) seems to be used.
>
> > > > > > > As I have posted this issue on my website and got some additional
> > > > > > > comments, I would like you to visit my post under
>
> > > > > > >http://www.saphod.net/2008/10/17/firebug-and-the-mysterious-component...
>
> > > > > > > because I don't want to repeat myself here.
>
> > > > > > > I hope this issue hasn't been posted before, if so I apologize for
> > > > > > > posting it again - I haven't found it using the search.
>
> > > > > > > Thanks!
>
> > > > > > > Kind regards
> > > > > > > Marco
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to