[firebug-lite-1.3.2] Library path not found.
1,282 views
Skip to first unread message
Steven
May 11, 2011, 10:54:02 AM5/11/11
to Firebug
In IE6, I get this alert error when loading Firebug Lite 1.3.2, the
Stable version [1] locally. It seems like the code is looking for
debugging/extension libraries. No other Firebug Lite artifact, besides
the one .js file, resides in my project JS directory. I haven't run
into this requirement before (if it needs a "full installation" of
Firebug Lite compressed contents: /plugin, /content, etc) in previous
versions of Firebug Lite. I have not set <html debug="true"> or any
Firebug-specific debug options, merely included the .js script in
<head>.
Have I missed something?
[1] http://getfirebug.com/firebuglite#Stable
Stable version [1] locally. It seems like the code is looking for
debugging/extension libraries. No other Firebug Lite artifact, besides
the one .js file, resides in my project JS directory. I haven't run
into this requirement before (if it needs a "full installation" of
Firebug Lite compressed contents: /plugin, /content, etc) in previous
versions of Firebug Lite. I have not set <html debug="true"> or any
Firebug-specific debug options, merely included the .js script in
<head>.
Have I missed something?
[1] http://getfirebug.com/firebuglite#Stable
Pedro Simonetti Garcia
May 11, 2011, 2:58:43 PM5/11/11
to fir...@googlegroups.com
I just tested on IE6 and I see no problems using the stable local installation.
Is there any chance you're having this issue?
http://code.google.com/p/fbug/issues/detail?id=3549
"Library path not found" message occurs when Firebug Lite cannot detect which script tag loaded the app. The code relies on the filename "firebug-lite[-optionalsuffix].js". Are you changing the name of the file?
You should not see this method, so let me know if the problem persists, because if it is not one of the two cases above, then it is a bug.
regards,
Pedro Simonetti.
Is there any chance you're having this issue?
http://code.google.com/p/fbug/issues/detail?id=3549
"Library path not found" message occurs when Firebug Lite cannot detect which script tag loaded the app. The code relies on the filename "firebug-lite[-optionalsuffix].js". Are you changing the name of the file?
You should not see this method, so let me know if the problem persists, because if it is not one of the two cases above, then it is a bug.
regards,
Pedro Simonetti.
2011/5/11 Steven <ecc1...@gmail.com>
--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To post to this group, send email to fir...@googlegroups.com.
To unsubscribe from this group, send email to firebug+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
Steven
May 12, 2011, 11:37:43 AM5/12/11
to Firebug
Yes. I had renamed the file to "firebug-lite-[version].js" (e.g.
"firebug-lite-1.3.2.js"). That was causing the library error. After
reverting the name, that error is gone. So if you say that's a valid
filename, I'm guessing this is a bug, but please confirm.
- Steven
On May 11, 1:58 pm, Pedro Simonetti Garcia <pedrosimone...@gmail.com>
wrote:
"firebug-lite-1.3.2.js"). That was causing the library error. After
reverting the name, that error is gone. So if you say that's a valid
filename, I'm guessing this is a bug, but please confirm.
- Steven
On May 11, 1:58 pm, Pedro Simonetti Garcia <pedrosimone...@gmail.com>
wrote:
> I just tested on IE6 and I see no problems using the stable local
> installation.
>
> Is there any chance you're having this issue?http://code.google.com/p/fbug/issues/detail?id=3549
> installation.
>
>
> "Library path not found" message occurs when Firebug Lite cannot detect
> which script tag loaded the app. The code relies on the filename
> "firebug-lite[-optionalsuffix].js". Are you changing the name of the file?
>
> You should not see this method, so let me know if the problem persists,
> because if it is not one of the two cases above, then it is a bug.
>
> regards,
>
> Pedro Simonetti.
>
> 2011/5/11 Steven <ecc11...@gmail.com>
> "Library path not found" message occurs when Firebug Lite cannot detect
> which script tag loaded the app. The code relies on the filename
> "firebug-lite[-optionalsuffix].js". Are you changing the name of the file?
>
> You should not see this method, so let me know if the problem persists,
> because if it is not one of the two cases above, then it is a bug.
>
> regards,
>
> Pedro Simonetti.
>
Pedro Simonetti Garcia
May 12, 2011, 8:47:58 PM5/12/11
to fir...@googlegroups.com
Okay. That name won't work because of the "dots". The name "firebug-lite-132.js" should work.
You can see how Firebug Lite detects the file / location here:
http://code.google.com/p/fbug/source/browse/lite/branches/firebug1.4/content/firebug/lib.js#312
The problem using version numbers at the file name is that maybe Firebug Lite won't be able to located the proper skin to use. It will depend upon factors like the name of the file, the options used, if debug is enabled, the location of that file, if it is loaded locally or remotely.
If you can use external links I suggest loading the individual versions online:
For instance to load the last stable 1.3 version:
<script type="text/javascript" src="https://getfirebug.com/releases/lite/1.3/firebug-lite.js"></script>
If you need more granular control, you can also use a link to your SVN and specify the exact revision number (the number 10000 can be any revision number):
<script type="text/javascript" src="http://fbug.googlecode.com/svn/!svn/bc/10000/lite/branches/firebug1.4/build/firebug-lite.js"></script>
If you want to work locally without external dependencies, checkout the whole Firebug Lite branches tree, then link to each specific version located at "<version-number>/build/firebug-lite.js":
http://fbug.googlecode.com/svn/lite/branches/
regards,
Pedro Simonetti.
You can see how Firebug Lite detects the file / location here:
http://code.google.com/p/fbug/source/browse/lite/branches/firebug1.4/content/firebug/lib.js#312
The problem using version numbers at the file name is that maybe Firebug Lite won't be able to located the proper skin to use. It will depend upon factors like the name of the file, the options used, if debug is enabled, the location of that file, if it is loaded locally or remotely.
If you can use external links I suggest loading the individual versions online:
For instance to load the last stable 1.3 version:
<script type="text/javascript" src="https://getfirebug.com/releases/lite/1.3/firebug-lite.js"></script>
If you need more granular control, you can also use a link to your SVN and specify the exact revision number (the number 10000 can be any revision number):
<script type="text/javascript" src="http://fbug.googlecode.com/svn/!svn/bc/10000/lite/branches/firebug1.4/build/firebug-lite.js"></script>
If you want to work locally without external dependencies, checkout the whole Firebug Lite branches tree, then link to each specific version located at "<version-number>/build/firebug-lite.js":
http://fbug.googlecode.com/svn/lite/branches/
regards,
Pedro Simonetti.
2011/5/12 Steven <ecc1...@gmail.com>
Reply all
Reply to author
Forward
0 new messages