On Jan 12, 9:48 am, FND <[email protected]> wrote:
> As you've guessed, it's a missing feature in the TiddlyWeb adaptor for
> now. It's nothing massively complicated - I simply haven't gotten around
> to it yet.
>
> > creating a new tiddler is't working! I think the necessary fields for
> > syncing are missing
>
> That sounds likely.
>
> However, a few weeks ago we made TiddlyWeb instances create a "common"
> bag by default, and the TiddlyWebConfig plugin then sets the respective
> variable (config.defaultCustomFields) accordingly.
>
> So if that bag and all the latest plugins (TiddlyWebAdaptor,
> TiddlyWebConfig, ServerSideSavingPlugin) are present, everything should
> be working fine.
> Maybe it's just that the "common" bag is missing because you'd created
> your instance before we implemented this change?
I'd like to piggyback on this thread and post some observations to
share in the 'saving' issue pool.
My question is given that the default recipe is set to "server.bag":
"common", is there a way to save to a bag other than common, ie imwiki
to new bag?
I was happy to be able to save to the default recipe under 0.0.9.3 so
I haven't tested 095 when it came out. Also I wasn't able to save to a
bag other than common (python2.5)
Now upgrading to 095 I can't save anymore unless I use an old instance
made in 093 using ServerSideSavingPlugin v3.2
I failed this test that v095 saves to default recipe where
{{{config.defaultCustomFields = {
"server.bag": "common"};
}}}
and this test that v095 saves to different bag
*made new instance
*made new bag
*imported existing tiddlers into new bag
When the "server.bag": "common" is set to <new bag>,
http://127.0.0.1:8080/recipes/<new
bag>/tiddlers.wiki has losted editing capability with the
chkHttpReadOnly is set to true and was only accessible from
AdvancedOptions as the backstage area disappeared.
Unchecking the chkHttpReadOnly to false to regain editing mode
persisted after a relaunch but subsequently modifying an existing
tiddler resulting in the usual 'You must save this tiddler.. " dialog
So conclusion, I was unable to save to a different bag other than
'common' in 093 and 095.
Under 095, I was able to change and save back in the ServerConfig
tiddler to "server.bag": "common" but unable to save again in general,
unlike 093.
Only successful save was to change the server.bag custom field to
'wiki' and back to 'common' but unable to save to SiteTitle nor
GettingStarted, nor new tiddler :-(
As evident in the server log and a $ls -R showing 1, 2 and 3 revisions
of ServerConfig:
{{{
127.0.0.1 - GUEST [12/Jan/2009:16:59:22 ] "PUT /bags/system/tiddlers/
ServerConfig?nocache=0.6353539275179345 HTTP/1.1" 2
04 - "http://127.0.0.1:8080/recipes/default/tiddlers.wiki"; "Mozilla/
5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5)
Gecko/2008120122 Firefox/3.0.5 Ubiquity/0.1.4"
}}}
I tried doing a $twanager update but that still didn't let me save
under 0.9.5
I tried making a new instance but that too didn't work.
I saved my old instance from 093 and double checked was able to save
again. whew!
ran a diff between ServerSideSavingPlugin 3.2 and 3.3 and the new
addition was this line: {{{readOnly = false; //# enable editing over
HTTP}}}
The thing I don't get is why I can save under the instance in 093 but
not the new instance made from 095. I guess ServerConfig is not the
only plugin that needs editing, but a $ grep -R "common" * in my
instance doesn't show any other tiddler with the specific
"server.bag": "common" parameter.
Eduard had saving success with 095, so I'll keep checking.
Anyway, it is still nice to save under v093 and i await the beta
launch :-)
Best,
tony
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
