Get the new PortableApps.com Platform 10.0: Gorgeous themes, a full portable app store and advanced functionality
Announcing the World's Best Flash Drive: The PortableApps.com Companion | Did you see a malware warning on Friday?

Local Html File Paths Are Messed Up

johnywhy - July 19, 2010 - 3:12pm

hello

when i double-click a local html file, the filename incorrectly gets incorrectly changed to the old dos 8-character naming, and spaces are treated as separate files.

for example, if i double-click a local file called:
C:\Users\john\Documents\Clients\Jeffrey\Footprints\Walking Tour\avatar\googleMapsAPItest.html

firefox portable opens the following two tabs:

file:///C:/Users/john/DOCUME~1/Clients/Jeffrey/Footprints/Walking

http://www.tour.com/avatar/googleMapsAPItest.html

how can i fix this?

note, firefox portable is set as the default program for local html files.


( categories: )

How is it default?

Did you perhaps make a batch file that uses %1 as the input parameter?

If so, try changing the %1 to "%1" which will force Windows to NOT break the input string at the space (which is how it sees it as two parameters).

neutron1132 (at) usa (dot) com

No, i used a free app called

No, i used a free app called registerfp.
http://www.winhelponline.com/blog/register-firefox-portable-with-default...

Did that do what you say?

Thanks

Johny why

Bad Registration

Basically the URL is being improperly passed to FirefoxPortable.exe. It's being passed without quotes. But, since there is a space in the path, it *HAS* to have quotes. Otherwise Firefox will interpret it as separate URLs and try to open each one as you see. The issue is not with Firefox Portable but with the registry key, so ultimately it was improperly set by registerfp.

Sometimes, the impossible can become possible, if you're awesome!

Can't check

Sorry, I can't check using the setup you describe, so pointing you in the right direction is the best I can do.

(I see that John has clarified the issue)

neutron1132 (at) usa (dot) com

registerfp 1.1 is up

Thanks for reporting this, folks.
This problem is fixed in v1.1.