I want to try what looks like a really cool tool. I've dl'd the FF version from http://www.huttar.net/dimitre/XPV/TopXML-XPV.html.
I open XPathMain.htm in FireFox, Browse to the provided test1.xml file, click Process File, with the default //* in the XPath window. In FF, I get this:
[Exception... "Access to restricted
URI denied" code: "1012" nsresult:
"0x805303f4 (NS_ERROR_DOM_BAD_URI)"
location:
"file:///Users/doug/Dev/XPV-FF/XPathMain.htm
Line: 43"]
I also opened it in Safari, followed the above, and nothing happened, when I clicked Process File.
Once I get it working, what am I expecting to see? I assume I will see the xml file in the big window with selected nodes highlighted?
I'm on OS X 10.6.6 and FF 3.5.16. Thank you.
I experienced this error also and after a bit of trial and error, I resolved the problem by placing my .xml file in the same directory as XPathMain.htm. It then immediately rendered in the lower window after selecting the Process File button.
Moving the authors.xml file outside the XPV-FF/ generates the same error. Perhaps this is the same origin policy type security?
I am not sure what could be an issue-- I cannot reproduce the reported problem.
Just downloaded and installed FF 4, opened file:///C:/Temp/XPV-FF/XPathMain.htm
and then specified:
C:\Temp\XPV-FF\authors.xml
The XPV works as expected.
Please, try to work with the file authors.xml that comes with the XPV and is in the same folder as the XPV starting page. If you can work with this file, this definitely means that there is a permission problem with the file that has the reported issue.
Related
I am currently using Pyzo and changed its font and background color according to the instructions on their website (http://www.pyzo.org/pyzo_themes.html) by changing the init() in the base.py file. Everything was fine until I wanted to change the settings back to normal. When I try to open any .py file Pyzo gives me the error
"Error loading file: local variable fore1 referenced before assignment".
On closing the error message, the Shell just keeps warming up and nothing happens. On the left side where the editor would have been, there is a small white box with a smaller yellow one inside.
Opening up Pyzo on its own does not give the error, but the same problem with the Shell and editor.
I tried:
changing the settings in base.py manually to their default value
copying the backup file I made before the changes back into the directory
uninstalling Pyzo with IOBit Uninstaller to catch all hidden files and reinstall it (about 10 times already)
I thought reinstalling it would resolve the matter but obviously there must be a different issue here. I really hope someone had the same problem, thanks in advance for any help!
I've created an extension using kango-framework, it works ok in Chrome and Opera 20, but when installing it on Firefox 27 or 28, I get error "aAddon._repositoryAddon is null".
Any guess? Thanks
I don't think aAddon has _repositoryAddon as a parameter. Find out by including Console.jsm and then going console.log('aAddon',aAddon). (Try just doing console.log Console.jsm might already be included). Then open up Browser Console. then in browser console, should be latest entry, find your aAddon msg then on the link next to it, click it, and it opens in variable viewer. There you can see what all properties aAddon has.
http://smg.photobucket.com/user/noitidart/media/i20dont20see20nsIInterfaceRequestor_zps7bfc9d43.png.html?sort=3&o=12
http://smg.photobucket.com/user/noitidart/media/my20code20works_zpsdd244f45.png.html?sort=3&o=11
Whenever I press on the open in IE icon, I get an error in the console:
Error: NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIProcess.init]
Source File: chrome://openinie/content/openinie.js
Line: 126 (This happened ever since upgrade to 16.0 and I assume it's probably security related)
I found that js file to be inside some "openinie#wittersworld.com.xpi" file (which I cleverly renamed to zip), and saw the offending line:
var iePath = openinie.getIEPath();
// create an nsILocalFile for the executable
var file = Components.classes["#mozilla.org/file/local;1"].createInstance(Components.interfaces.nsILocalFile);
file.initWithPath(iePath);
// create an nsIProcess
var process = Components.classes["#mozilla.org/process/util;1"].createInstance(Components.interfaces.nsIProcess);
process.init(file); // <-line 126
is it possible to fix it and "re-compile" it zipping and renaming?
(I assume it's something with security maybe).
can I debug this using for example an alert box to display values of variables?
is it possible to fix it and "re-compile" it zipping and renaming
Yes, you can simply replace a file in the ZIP archive, most extensions aren't signed (you can remove the META-INF directory from the XPI file if this one is). In fact, for your debugging it is better to unpack openinie#wittersworld.com.xpi into a directory named openinie#wittersworld.com in the same folder and remove the original file - this way you won't need to pack/unpack on each change. You should also start Firefox with the -purgecaches command line parameter, otherwise the file you are changing might get cached.
can I debug this using for example an alert box to display values of variables?
Yes. However, I would rather recommend Components.utils.reportError() method that will log to the Error Console (press Ctrl-Shift-J to open it) without opening modal dialogs. In this particular case I would write:
Components.utils.reportError(iePath);
This seems to point to a non-existent file meaning that the getIEPath() function is faulty.
Good luck!
Some of the webpages I visit have stubborn save file dialogs for executables. I would like to do one of the following using an extension:
Save the file by default and close the dialog box. I looked at http://kb.mozillazine.org/File_types_and_download_actions It doesn't really work for these files (the problem is described at: http://kb.mozillazine.org/File_types_and_download_actions under 'Unable to set automatic action. I verified the headers.)
I guess I can use browser.download.manager.closeWhenDone from https:// developer.mozilla.org/en/Download_Manager_preferences , if I figure out the first part :)
Suppress the download manager from showing any such dialogs altogether.
I found https:// developer.mozilla.org/en/nsIDownloadManager#addListener() and https:// developer.mozilla.org/en/Download_Manager_improvements_in_Firefox_3 that look promising. I don't really know how to extract the source URI for the transfer either. I'm curious if anyone has any existing examples for using these or if there's a better way to do this. Or if someone knows what part of Firefox's code I could poke, that would be useful too.
Thanks!
PS: Sorry,I had to break the hyper-links above with an unnecessary space after https:// - apparently I need 10 reputation to do that :)
FWIW, I managed to work around this - though my solution probably wont work for most others.
Fortunately I'm behind a proxy I control, so I just corrected the obnoxious headers (Content-Disposition and Content-Type) before they reached Firefox. These were forcing Firefox to open the File Save Dialog box despite my specified preference to 'Always save file of this type'. Furthermore, I set 'browser.download.manager.closeWhenDone' property to True. Works for me, and I cruise through such sites w.o being interrupted.
I am working on a new version of a firefox extension, but after releasing it, and incrementing the em:version in install.rdf and update.rdf, when I click "Find updates" Firefox reports that "No updates were found." When I run it with debugging on, the output in the console is actually identical to what I see when I don't put the update live.
It starts with RDFItemUpdater:checkForUpdates with all of the parameters, and returns with Addon Update Ended and status: 8.
I verified with McCoy tool that the extension is signed, and has the same Id as the old one, etc. I'm not sure what else to try. Any advice would be appreciated. This is with Firefox 3 (and the extension is marked as compatible with it... that didn't change).
Make sure your update.rdf file is being served with an appropriate Content-Type, i.e. text/rdf, text/xml or application/xml+rdf
If you've only recently changed update.rdf, maybe it's cached. Load it in the browser then Shift-Refresh.
here are some nice tips that helped me: https://developer.mozilla.org/en/Extension_Versioning,_Update_and_Compatibility
but, auto update function will not work if extension is marked "experimental".
I'm having a similar issue, and think it's due to an invalid rdf file. Did you check that yours parsed with this tool? http://www.w3.org/RDF/Validator/
There are lots of things to mess up, one of which is installing an extension from AMO and expecting it to update when you change your update.rdf :)
I was having the same problem. In my update.rdf, I had a wildcard in my minVersion attribute:
minVersion="3.0.*"
Removing the wildcard fixed the status 8:
minVersion="3.0"
The update works now (console shows status 1). This was using Firefox 3.0.18.
My guess is that status 8 means there was a problem understanding the contents of the file (not necessarily an RDF parsing problem). If your minVersion doesn't have a wildcard, maybe there's an invalid character hiding somewhere.