I still have no solution to this problem. I am resubmitting this in  
the hope that there will be a clue in it for someone that will lead to  
a diagnosis of problem. I will also post about another message I got  
when trying to do "save as" with the same TiddlyWiki under slightly  
different circumstances. Your patience with me is greatly appreciated.

On Jan 24, 2009, at 12:17 PM, Eric Weir wrote:

> Eric Shulman wrote:
>>
>>>     File Not Found
>>>
>>>     Firefox can't find the file at /AAAAAAG+AAIAAAxNYWNpbnRvc2ggSEQ
>>>     AAAAAAAAZAAAAAAAAAADErCocSCsAAAALHOESYmFja3VwRW
>>>     1wdHlUVy5odG1sAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>>>     AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsc5cTqCDoAAAAAA
>>>
>> ...
>>
>> Clearly, the problem is that you are somehow telling the browser to
>> open an invalid URL (i.e., "/AAAAAAG+....").
>>
>> Some questions that come to mind:
>>
>> The browser only attempts to open a URL when you SaveAs if you  
>> include
>> the 'open' keyword in the <<saveAs>> macro.  If that keyword is
>> present, try removing it so the browser won't try to open the new
>> URL.  In that situation, does the error still occur?
"Open" does not appear in the macro. The macro call is in my  
SidebarOptions, and the only thing that's there is <<saveAs>>.
>
>> Is this problem only under OSX?  Does the same document work properly
>> under Windows?  If so, then the problem is obviously platform-
>> specific, which narrows the possibilities.
I just tested it to make sure. Running the same TiddlyWiki "save as"  
goes through just fine on my XP machine.
>> Was a new *file* actually written to the local harddrive
No. Nothing is written to the hard drive.
>> ... and the Big Question: where the heck is that invalid URL string
>> coming from?
>>
>> One possible clue: the string *looks* like binary content that has
>> been converted into base64-encoded text... which can be combined with
>> the data:// protocol to create a URL...
>>
>> SaveAsPlugin uses the current document.location.href to determine the
>> default *path* in which to write the new file... so perhaps the
>> document.location.href value is somehow not being reported correctly
>> from the browser.


That's a bit beyond me. I don't know if it's relevant, but this  
TiddlyWiki was simply copied from my XP machine to the Mac. It was not  
created/established on the Mac. [Though I've tried installing the  
SaveAs plugin on a fresh TiddlyWiki on the Mac and then trying to use  
it and get the same result.] But perhaps none of this is relevant to  
what you're wondering about.
>
>> Lastly, please describe the *exact* step-by-step actions you took in
>> every detail: what command did you click?  Did you get a 'save a  
>> file'
>> dialog box?  Did you see any TW messages?  Is the browser trying to
>> open a new tab/window or overwrite the current one? etc.
>>
> Here are the steps:
>
> Put <<saveAs>> in SidebarOptions.
> Click 'save changes' and reload.
> Click 'save as'.
> Finder opens to TiddlyWiki folder. [All file names are greyed-out.]
> Navigate to my backup folder [twbackup]. [Again, all file names  
> greyed-out.]
> Select backup file to write to.
> Click 'Save'.
> FF notifies that file exists.
> Click 'Replace'.
> Weird string displayed in the TW I'm trying to backup where save  
> result is normally reported.
> Click on the string.
> New FF window opens with 'Page Load Error' tab.
That's it.

I hope there are additional clues somewhere above.

Thanks,
----------------------------------------------------------------------
Eric Weir
Decatur, GA  USA
[email protected]





----------------------------------------------------------------------
Eric Weir
Decatur, GA  USA
[email protected]






--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" 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/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to