Firefox allows "save changes" but not "save as"

[Eric Weir]

I'm just getting established on a new MacBook. Firefox will let me do
"save changes" but not "save as." Below is the message I got. I think it
was a "page load error."

Firefox can't find the file at
/AAAAAAHKAAIAAAxNYWNpbnRvc2ggSEQAAAAAAAAAAAAAAAAAAADErCocSCsAAAALHOEVYmFja3VwTVBUV0VyaWMncy5odG1sAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsc6sV/11YAAAAAAAAAAP////8AAAkgAAAAAAAAAAAAAAAAAAAACHR3YmFja3VwABAACAAAxKxiXAAAABEACAAAxYAdpgAAAAEAFAALHOEACxzHAAn6eAAJ+mEAAHtbAAIAT01hY2ludG9zaCBIRDpVc2Vyczplcmljd2VpcjpEb2N1bWVudHM6VGlkZGx5V2lraTp0d2JhY2t1cDpiYWNrdXBNUFRXRXJpYydzLmh0bWwAAA4ALAAVAGIAYQBjAGsAdQBwAE0AUABUAFcARQByAGkAYwAnAHMALgBoAHQAbQBsAA8AGgAMAE0AYQBjAGkAbgB0AG8AcwBoACAASABEABIAQlVzZXJzL2VyaWN3ZWlyL0RvY3VtZW50cy9UaWRkbHlXaWtpL3R3YmFja3VwL2JhY2t1cE1QVFdFcmljJ3MuaHRtbAATAAEvAAAVAAIAD///AAA=.

* Could the item have been renamed, removed, or relocated?
* Is there a spelling, capitalization, or other typographical
error in the address?
* Do you have sufficient access permissions to the requested item?

I don't know if this is enough information for anyone to help, but if
anyone can help it would be appreciated. Let me know if more information
is needed.

Thanks,

Eric Weir
Decatur, GA USA

[Daniel Baird]

That looks very weird and I can't explain it, but anyway:
Don't do a "Save As", browsers don't save TiddlyWikis properly that
way. Go into Finder and copy + rename the .html file.

;Daniel

--
Daniel Baird
/to be or not to be/ => /(2b|[^2]b)/ => /(2|[^2])b/ => /.b/
...optimise your regexes, people!

[Eric Weir]

Daniel Baird wrote:
> That looks very weird and I can't explain it, but anyway:
> Don't do a "Save As", browsers don't save TiddlyWikis properly that
> way. Go into Finder and copy + rename the .html file.
>
>

Thanks, Daniel. That's certainly an option, but "saving as" is a lot
more convenient. I did it routinely in Windows. It was my solution to
keeping backups. I found TW's built in way of doing it arcane and not
very helpful -- or maybe overly helpful. I want to control when backups
are made.

Regards,

[Eric Shulman]

> Daniel Baird wrote:
> > Don't do a "Save As", browsers don't save TiddlyWikis properly

> Thanks, Daniel. That's certainly an option,
> but "saving as" is a lot more convenient.
> I did it routinely in Windows.
> It was my solution to keeping backups.
> I found TW's built in way of doing it arcane and not
> very helpful -- or maybe overly helpful.
> I want to control when backups are made.

TiddlyWiki might *seem* like a full-blown application, but please
remember that, underneath it all, it's built from HTML, CSS and
Javascript, supported by the brower's built-in functionality... and
the browser isn't "Windows"... it's a just browser... with browser-
centric, security-restricted file I/O functionality.

*Not* using the browser's native "Save As" command isn't an
*option*.... it's an unfortunately necessity... as Daniel very clearly
stated: "browsers don't save TiddlyWikis properly". Wanting it to be
different doesn't make it possible.

Nonetheless, I tend to agree with you that the "save as" functionality
can be very convenient when spawning new documents from existing ones,
or creating manual backups, temporary test files, etc.

Fortunately, while there is simply no way to use the brower's native
"Save As" command, there *is* a way to provide the "save as"
functionality from *within* TiddlyWiki, by using this plugin:
http://www.TiddlyTools.com/#SaveAsPlugin
http://www.TiddlyTools.com/#SaveAsPluginInfo

The plugin automatically adds a "save as" command to the TW backstage
menu, making it really easy to create new documents from the current
one. In addition, the plugin defines a <<saveAs>> macro, which can be
used to apply optional 'tag filtering' to select a subset of tiddlers
to be written to the new file with one of the following output
formats:
* a full TiddlyWiki HTML document
* a TiddlyWiki "PureStore" file (just tiddlers, no core code)
* a plain text file listing of tiddler source content
* an RSS NewsFeed XML file

The "PureStore" format is particularly useful for creating backups of
a set of tiddlers: because the file contains a 100% TW-compatible
"tiddler store area", the tiddlers it contains can be directly read in
to a document by using the TW backstage>import feature.

enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

[Eric Weir]

Eric Shulman wrote:

> Fortunately, while there is simply no way to use the brower's native
> "Save As" command, there *is* a way to provide the "save as"
> functionality from *within* TiddlyWiki, by using this plugin:
> http://www.TiddlyTools.com/#SaveAsPlugin
> http://www.TiddlyTools.com/#SaveAsPluginInfo
>

My apologies for the misunderstanding. I did say "Firefox won't let me,"
because the error message said "Firefox can't find the file at," but
what I was referring to was saving using the "SaveAsPlugin," which I
think I have installed in all my TWs.

So does that put it in a different light, i.e., any ideas about what's
going on and how I might solve the problem?

A possible clue: when I do "save as" -- in my TW! -- in the browse-able
directory that opens up all the file names are greyed out, as if they're
not available to be written to.

Glad at least to hear that the "SaveAsPlugin" should be working, and I
apologize again for the misunderstanding.

Sincerely,

[Eric Weir]

Eric Weir wrote:
> A possible clue: when I do "save as" -- in my TW! -- in the browse-able
> directory that opens up all the file names are greyed out, as if they're
> not available to be written to.
>
>
>

Another one. When I do "save as" -- again, in the TW -- the name that's
suggested is not the name of the TW I'm saving. It is, instead, "new.html."

That's always been the case with this particular TW. It's always puzzled
me, but it wasn't a problem in Windows. I would just change the name to
the correct name and go ahead with the save.

Hope that helps.

[Daniel Baird]

On Sun, Jan 4, 2009 at 9:58 AM, Eric Weir <eew...@bellsouth.net> wrote:
> [..] what I was referring to was saving using the "SaveAsPlugin," which I

> think I have installed in all my TWs.

Ahh I see. I had the same misunderstanding as Eric S. Sorry..

;D

[Eric Weir]

Daniel Baird wrote:
> Ahh I see. I had the same misunderstanding as Eric S. Sorry..
>

As I said, I was partly responsible.

Regards,

[Eric Weir]

Eric Weir wrote:
> Eric Shulman wrote:
>
>> Fortunately, while there is simply no way to use the brower's native
>> "Save As" command, there *is* a way to provide the "save as"
>> functionality from *within* TiddlyWiki, by using this plugin:
>> http://www.TiddlyTools.com/#SaveAsPlugin
>> http://www.TiddlyTools.com/#SaveAsPluginInfo
>>
>> My apologies for the misunderstanding. I did say "Firefox won't let me,"
>> because the error message said "Firefox can't find the file at," but
>> what I was referring to was saving using the "SaveAsPlugin," which I
>> think I have installed in all my TWs.

Having clarified that this problem occurs when I attempt to SaveAs my
TW, I still have the problem. Again, when I do SaveAs I get the
following message:

File Not Found

Firefox can't find the file at /AAAAAAG+AAIAAAxNYWNpbnRvc2ggSEQ
AAAAAAAAZAAAAAAAAAADErCocSCsAAAALHOESYmFja3VwRW
1wdHlUVy5odG1sAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsc5cTqCDoAAAAAA
AAAAP////8AAAkgAAAAAAAAAAAAAAAAAAAACHR3YmFja3VwA
BAACAAAxKxiXAAAABEACAAAxOpAegAAAAEAFAALHOEACxzH
AAn6eAAJ+mEAAHtbAAIATE1hY2ludG9zaCBIRDpVc2Vyczplcmljd2Vpc
jpEb2N1bWVudHM6VGlkZGx5V2lraTp0d2JhY2t1cDpiYWNrdXBFbXB0eV
RXLmh0bWwADgAmABIAYgBhAGMAawB1AHAARQBtAHAAdAB5AF
QAVwAuAGgAdABtAGwADwAaAAwATQBhAGMAaQBuAHQAbwBzA
GgAIABIAEQAEgA/VXNlcnMvZXJpY3dlaXIvRG9jdW1lbnRzL1RpZGRse
Vdpa2kvdHdiYWNrdXAvYmFja3VwRW1wdHlUVy5odG1sAAATAAEvAA
AVAAIAD///AAA=.

* Could the item have been renamed, removed, or relocated?
* Is there a spelling, capitalization, or other typographical
error in the address?
* Do you have sufficient access permissions to the requested item?

Recently I've encountered the same problem when I attempt to import
tiddlers. In sum, with my preferred method of doing backups unavailable
to me, and being unable to do imports, my TWs are less secure and less
usable than they should be.

I don't know if I explained initially that this problem occurred after I
moved from an XP to an OS X environment. In making that move I simply
copied my TW foldler over to my new Mac. Today I downloaded a brand
new TW, installed the SaveAs plugin, and tired doing SaveAs again. Same
problem.

My guess is that the problem has to do with the third question above,
i.e., that it has to do with permissions. Problem is, I don't know what
to give permission to or how to do it. Perhaps I should be posting to a
Mac forum, but that would involve explaining the intricacies of TW. If
anyone here could help I would greatly appreciate it.

Sincerely,
------------------------------------------------------------------------

Eric Weir
Decatur, GA USA

eew...@bellsouth.net

[Eric Shulman]

>     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?

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...

Was a new *file* actually written to the local harddrive?

... 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.

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.

[Eric Weir]

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?
  

I don't know anything about 'open' in the macro. I simply put <<saveAs>> into my SidebarOptions tiddler.

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.
  

The problem began occurring after I moved from Windows to OSX. Again, when I made that move I simply copied my TiddlyWiki folder over to the OSX directory.

Was a new *file* actually written to the local harddrive
  

The problem initially appeared with TWs that I'd been using on Windows and just copied over to OSX. Immediatelly prior to this post I downloaded and saved an empty TW from TiddlyWiki.com. After installing SaveAs the problem is still present.

... 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.
  

This is getting a bit beyond me, but is there a way to determine whether this is happening?

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. Makes me think it's a permission problem.]
• 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.

Thanks for trying to help with this, Eric.

Sincerely,

---