[tw] newline syntax for QuickEdit replace plugin?
Has anyone figured out how to find the newline character with QuickEdit replace? I'm really enjoying the productivity gains from Eric's QuickEdit_replace plugin http://www.tiddlytools.com/#QuickEditPlugin It's great having find and replace editing in the tiddler without having to open up an external text editor. But sometimes I replace new lines and I have yet to figure out what the syntax is to put in the find field. I've tried: \n \\n '\n' "\n" \u0085 \\u0085 any ideas? Best, tony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en -~--~~~~--~~--~--~---
[tw] tiddlywiki: Toggling tags with CheckboxPlugin macro syntax to prevent recursion overflow?
Hi, Toggling tags works fine with ToggleTagPlugin, but I can't seem to get it to work with CheckboxPlugin. Despite the documentation in CheckboxPluginInfo, I'm finding that the syntax for the checkbox target works in reverse (e.g., tiddlername| tagname) When I add this macro syntax to the ViewTemplate, it works adding a checkbox to all tiddlers and toggles 'tag1' for TestTiddler. When I use , it too works this time toggling tag1 for all tiddlers, but I'm coming up with a "RangeError: Maximum call stack size exceeded" on Safari and "InternalError: too much recursion" in Firefox when I click on a WikiWord or reload the Tiddlywiki document I get a Error in macro <> [1] I think I'm incorrectly specifying the macro syntax improperly specifying that the toggling should apply to all tiddlers by leaving the tiddlername blank. The checkbox behavior works, but has erroneous consequences. Does anyone use/know of an alternative syntax for macro usage ? Best, tony [1] I guess I'm getting a recursion error similiar to this thread: http://groups.google.com/group/TiddlyWiki/browse_frm/thread/33706a22b6af79ca/d912c4068e7e338b?lnk=gst&q=group%3Atiddlywiki+recursion#d912c4068e7e338b --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~--~~~~--~~--~--~---
[tw] Re: an open source version of the tiddlyspot server
On Feb 12, 4:43 am, "cd...@peermore.com" wrote: > On Feb 12, 11:58 am, Daniel Baird wrote: > > > Imagine if you could just download and unzip some PHP files, and > > instantly have a tiddlyspot-type server running behind your corporate > > firewall, on your school server, or just on the Mac Mini in the back > > of your broom cupboard. > > This is very cool. I think it will be very useful to lots of people. > > At your leisure I think it would be great for you guys, Simon, Cool > Cold, BidiX, Frank (of WikklyText) and me and Fred to have some chats > about where, if anywhere, there are overlaps between TiddlySpot, > TiddlySpeck, ccTiddly, TiddlyHome, WikklyText and TiddlyWeb. They all > have slightly different goals and attitudes but I've never seen a > single location that delineates all that. Might be useful. As a user, this is all very exciting to see the mix of similiar streams in the serverside river. I'm really enjoying the TiddlyWeb metaphor of TiddlerExchange, so hopefully your serverside discussions will lead to some fruitful cross fertilization or thee holy grail of TiddlyUniverses. As for the easy to install question, the unzip and go works for me! A good example of ease is tweebox at http://gimcrackd.com/etc/src/. Back in the day you could download php5, twee, and go forth on a usb drive, but Chris Klimas has done a nice job of packaging up all that story engine. That ease of install (or having to explain how to other ppl) is what makes TiddlyWiki so attractive and hopefully can be reflected on these other serverside incarnations as well. As for finding a non-local host, add another vote for the Pseudo's suggestion of python + GoogleAppEngine like http://code.google.com/p/tiddlyhost/ under BSD Silly Names: TiddlyMote SpeckMote SpeckMode Specky SeeSpotTiddler HTiddlyML (c)(tm)(r) if that last name goes big, feel free to send remittance to tony at ... :-) Best, tony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~--~~~~--~~--~--~---
[tw] Re: Tiddler links in Freemind ImageMap
On Jan 25, 12:44 pm, skye riquelme wrote: ...Firefox blocks it as an unauthorised > popup. And it won´t let me unblock myself. Seems I can only authorise/ > unblock "http://..."-type addresses...and not a local file! > > Any ideas! how to let freemind open the local tiddler!!! > Hi Skye, I'm not sure I follow, but Freemind supports tiddler permalinks when I have my tiddlywiki under local file:// You can paste the permalink into the node URL. Clicking the Freemind node will launch the browser under file:// (example) file:///Users/me/wiki.html#Tiddler In the past for lookup, I've embedded freemind mindmaps into tiddler's using juanpedro's flash browser for Freemind http://freemind.sourceforge.net/wiki/index.php/Flash_browser Presumably, the resulting node url as rendered in flash in a tiddler should open the local tiddler permalink referenced therein. I got dizzy typing that. I haven't tried that hotspot mapping with url, sounds cool. Thanks for sharing. Best, tony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~--~~~~--~~--~--~---
[tw] Re: Maximum number of Tiddlers?
On Jan 22, 4:38 pm, "ti...@timon.info" wrote: > > After having readhttp://www.tiddlywiki.org/wiki/Performance_IssuesI > realize that several MB are already a lot for TiddlyWiki and > converting my current content would result in a huge unusable thing. > Managing a lot of content efficiently probably really takes some > server software that can do preprocessing and caching and ideally > includes a full fledged database. Right now I think I will have to > leave my current content on my private machine at home. At work I'll > start with a blank TiddlyWiki and hope I'll get by with it for a > while, before it grows to large. Hopefully I have a better idea by > then 8-) > Hi Timon, I too have confronted the same issue and I don't know how Eric at TiddlyTools.com does it- dense and rich but still loads quick! Nevertheless here are some observations of my experiments on scale: I've successfully tested TiddlyWiki for a knowledge base I help coordinate and found that I had to offload the assets to the filesytem and use TW more as a frontend viewer than a single all encompassing repository in order to contain the scale issue - So that large topics of styled content are contained in iframes on a shared or local drive as in tiddler body: Images are handled in the same way: [img(480px,auto)[file:///path/to/your/image]] It was under 3MB covering 1000's of topics and associated images along with an issue log. But nothing like 17MB! Judicious use of an archival method to further segregate old from new content also helps. I've used this effective combo: ToDoTogglePlugin with CheckboxPlugin along with the essentials from Eric's TiddlyTools: Import and Export Tiddlers Plugins to manage that archival process. Udo's YourSearch along with his other plugins are also excellent for culling. I also tried using a flat file system with the data and going csv with the DataListPlugin at the http://baggr.tiddlyspot.com/ which leverages Udo's DataTiddlerPlugin. It's great for long list lookups but ultimately stayed with the tiddler as unit KISS route as is much more familiar UI. Before that I did do a taste of running php5 locally then used BidiX's upload plugin http://tiddlywiki.bidix.info/#[[UploadPlugin%204.1]] for a flavor of local serverside, but abandoned once I got proof of concept. Finally, I've been experimenting with TiddlyWeb (AKA mother of all server sides) since it currently uses a local text store where tiddlers are file revisions in folders. You can make recipes from bags of tiddlers and mix and match rolling your own collection. The thing about TiddlyWeb is that my puny brainz doesn't have to know how to configure Apache or some other server magic, but sounds like you have the smart for that and serverside is not an issue for you. Chris Dent http://peermore.com/tiddlyweb/dist/ and FND works with TiddlyWeb. So there are options if you want to stay local, but as we've seen over the years, scale is an important question when working lots of stuff in TW. And it sounds like you've acumulated a lot of stuff, so a small army of TWs may be needed with a good workflow! :-) hth Best, tony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~--~~~~--~~--~--~---
[tw] Re: TiddlyWeb latest experience
On Jan 20, 2:43 pm, EduardWagner wrote: > Hi, we do have a lot of recipes now > and each of them has it's own workspace bag, where we put the > corresponding TiddlyWebConfig entry "server.workspace": "bags/ > workspace" > We don't have a TiddlyWebConfig in the system bag any more and so only > one is loaded with the recipes bags. > I don't now if there is a feature for multiple workspaces right now, > there is a tiddlersourceplugin, but i don't now if it's obsolete now. Whew, I think I finally figured out a workaround to save to different workspaces thanks to Eduard and FND's advice of either having a new tiddler macro set to the target bag or adding a custom config in the local bag: above and http://groups.google.com/group/TiddlyWikiDev/browse_thread/thread/94cdb9613200687c# with a slight hiccup of having to restart twanager server with the first save still going to the common bag. Basically I chose the latter as suggested: there needs to be a local config in the new bag (not system, not common) that will override the TiddlyWebConfig in the system bag. I copied the TiddlyWebConfig from the system bag into 2 test bags: foo and bar Then I changed config.defaultCustomField, "server.workspace": "bags/ common" to "bags/foo" and "bags/bar" respectively. so $ less store/bags/foo/tiddlers/TiddlyWebConfig/1 should have "server.workspace": "bags/foo" and $ less store/bags/bar/tiddlers/TiddlyWebConfig/1 should have "server.workspace": "bags/bar" more importantly in the system bag $ less store/bags/system/tiddlers/TiddlyWebConfig/1 will be "server.workspace": "bags/common" and if I'm reading correctly saving default to 'default' bag! -http:// www.tiddlywiki.org/index.php?title=Dev_talk:TiddlyWeb&action=edit§ion=2 I made the usual recipe of foo recipe = system + foo bag with imported empty.html and bar recipe = system + bar bag with imwiki empty.html I then started the server and created a foo tiddler from the foo recipe and saved Unfortunately when I checked the foo bag (not foo recipe) I didn't see my foo tiddler. It got saved to the common bag even though I went on the command line and edited it to bag/foo: 2009-01-20 16:23:06,707 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:16:23:06 ] "PUT /bags/common/tiddlers/FooTiddler?nocache =0.07761599014055898 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/ foo/tiddlers.wiki" 2009-01-20 17:17:27,651 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:17:17:27 ] "PUT /bags/common/tiddlers/FooTiddler?nocache =0.34582476555036457 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/ foo/tiddlers.wiki" So I restarted the server and tried creating a bar tiddler in bar recipe bingo it worked as shown PUT to bags/bar 2009-01-20 17:18:06,104 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:17:18:06 ] "PUT /bags/bar/tiddlers/BarTiddler?nocache=0. 5101406414486139 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/bar/ tiddlers.wiki" NT Then I tried foo again, bingo that worked with PUT to bags/foo: 2009-01-20 17:20:16,963 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:17:20:16 ] "PUT /bags/foo/tiddlers/FooTiddler?nocache=0. 9306065403541731 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/foo/ tiddlers.wiki" NT another bar tiddler just in case, I'm not going crazy: 2009-01-20 17:22:01,646 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:17:22:01 ] "PUT /bags/bar/tiddlers/BarTiddler2?nocache=0 .7775235943857574 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/bar/ tiddlers.wiki" NT Maybe change the title to Bar (testing save to existing tiddler): 2009-01-20 17:22:08,396 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:17:22:08 ] "PUT /bags/bar/tiddlers/SiteTitle?nocache=0.4 650678830220858 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/bar/ tiddlers.wiki" NT 5 And another foo tiddler 2 2009-01-20 17:23:13,663 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:17:23:13 ] "PUT /bags/foo/tiddlers/FooTiddler2?nocache=0 .1970655670193442 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/foo/ tiddlers.wiki" NT And lastly title change: 2009-01-20 17:23:19,600 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:17:23:19 ] "PUT /bags/foo/tiddlers/SiteTitle?nocache=0.0 2641447881101089 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/foo/ tiddlers.wiki" NT So it works but is a bit of a kludge as the user has to go on the command line and edit the TiddlyWebConfig manually ie save was set to common bag. The only hiccup is that the initial save for some reason saves to the common bag. I'll keep testing. Sorry for all the long posts, but it helps to refer back when i need to test again on the next iteration, hopefully beta! I would have thrown these notes to the wiki, but i don't think it is useful as tiddlyweb is still evolving. Thanks again for all the input, it was a good learning experience Best, tony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from th
[tw] Re: TiddlyWeb latest experience
On Jan 20, 12:00 pm, ccahua wrote:
> On Jan 20, 9:49 am, FND wrote:
>
> Do I add this custom line (server.workspace": "bags/myBag") in
> TiddlyWebConfig/config.defaultCustomFields
> for every new bag? or do I add new set of config.defaultCustomFields
> witht the custom line?
>
> Basically, what do I change in order to save in more than 1 bag, ie
> common, bag1, bag2, bag3?
...
>
> Now i just have to find out how to set the TiddlyWebConfig/
> config.defaultCustomFields so I can save in more than one bag
A bit more checking...
I tested again with another bag and I think the server needs a restart
in order to save after the TiddlyWebConfig save.
For some reason twanager is picking up the old server.workspace custom
config in revision 1. Only after a restart of the server, does the
custom config in TiddlyWebConfig/revision 2 work and tiddlers are
saved to the new bag.
This was apparent when I tried to save to a new journal tiddler and
found that the tiddler saved to bag2/tiddlers/20 January 2009
was instead saved to bag1/tiddlers/20 January 2009 even though
server.workspace": "bags/bag2"
After I restarted the server, twanager correctly PUTS to the new bag.
For multiple workspaces...
Ha! I thought I could get away with just adding more workspaces to
TiddlyWebConfig:
config.defaultCustomFields = {
"server.type": "tiddlyweb",
"server.host": store.getTiddler("TiddlyWebConfig").fields
["server.host"],
"server.workspace": "bags/bag1"
"server.workspace": "bags/bag2"
};
Got a good save to bag1, but then I got a PluginManager error when I
tried to open bag2. Oh well.
I guess I don't understand how TiddlyWeb separates the custom
configs. :-\
Perhaps there is an issue if there are identical named tiddlers in
different bags but the TiddlyWebConfig in the System bag is the source
of all recipes?
Best,
tony
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to TiddlyWiki@googlegroups.com
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/TiddlyWiki?hl=en
-~--~~~~--~~--~--~---
[tw] Re: TiddlyWeb latest experience
On Jan 20, 9:49 am, FND wrote: > > I can confirm this. I thought we had addressed this issue, but it seems > > it's not resolved entirely. > > There was a small bug in TiddlyWeb's ETag handling. > Chris has fixed this and released v0.9.7: > http://tiddlyweb.peermore.com/dist/CHANGES > > -- F. >From FND Mon, 12 Jan 2009 17:48:44 + >However, we've recently changed the understanding of workspace so you >don't have to worry about the TiddlyWeb-specific server.bag anymore. >So instead of that, you should use the following now: "server.workspace": "bags/myBag" Thank you all, Chris, FND, Eduard.. one more question: Do I add this custom line (server.workspace": "bags/myBag") in TiddlyWebConfig/config.defaultCustomFields for every new bag? or do I add new set of config.defaultCustomFields witht the custom line? Basically, what do I change in order to save in more than 1 bag, ie common, bag1, bag2, bag3? >Does that help? yes, but, a wee hiccup (FYI) For 1 new bag, I'm able to save to existing tiddlers and save new tiddlers to an imported bag, hooray! but the first time I tried to save didn't work. Subsequent saves now work which is wonderful. (I love the automatic creation of the tiddlyweb.log btw.) Here's what i did: I installed 097 and was successful in saving to existing tiddlers in a new bag (not common) but not saving new tiddlers. 1 made new instance 2 made new bag, w3c 3 imported this test tiddlywiki: http://osmosoft.com/~psd/TiddlyWikiDeviceAccess/ 4 made new recipe, 'test' = system + w3c 5 Test saving to existing tiddler - started the server and successfully saved to existing tiddler to the common bag but not a new tiddler. 6 Test saving to new tiddler: Then I tried changing the "server.workspace": "bags/common" to "server.workspace": "bags/w3c" as follows: go into recipe as tiddlers.wiki http://127.0.0.1:8080/recipes/test/tiddlers.wiki go to the backstage, TiddlyWebConfig change the field to "server.workspace": "bags/w3c" you should get a saved dialog, something like "TiddlyWebConfig saved successfully" I make a new tiddler and get a successful save dialog. looks good right? But when i go back into the 'common' bag, all the new saved tiddlers are there even after changing the server.workspace to bags/w3c as shown in the log: Looking at the tiddlyweb.log shows a PUT to the TiddlyWebConfig (changing the server.workspace to bags/w3c instead of bags/common, creating revision 2 in TiddlyWebConfig): 2009-01-20 09:20:07,028 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:09:20:07 ] "PUT /bags/system/tiddlers/TiddlyWebConfig?no cache=0.4641619112542664 HTTP/1.1" 204 - "http://127.0.0.1:8080/ recipes/test/tiddlers.wiki" "Mozilla/5.0 (Windows; U; Wi ndows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 Ubiquity/0.1.5" This entry shows a PUT of the new tiddler to common bag (not w3c) even though I made a new revision 2 above?! 2009-01-20 09:23:09,466 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:09:23:09 ] "PUT /bags/common/tiddlers/test%20saving%20to %20the%20test%20recipe?nocache=0.7691834834896291 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/test/tiddlers.wiki"; "Mo zilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/ 2008120122 Firefox/3.0.5 Ubiquity/0.1.5" A bit later, Tiddlyweb is saving fine to the w3c bag: 2009-01-20 11:21:09,502 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:11:21:09 ] "PUT /bags/w3c/tiddlers/SavingTest?nocache=0. 1053583499357923 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/test/ 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.5" 2009-01-20 11:24:43,573 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:11:24:43 ] "PUT /bags/w3c/tiddlers/AnotherSavingTest?noc ache=0.4253931028008009 HTTP/1.1" 204 - "http://127.0.0.1:8080/recipes/ test/tiddlers.wiki" "Mozilla/5.0 (Windows; U; Win dows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 Ubiquity/0.1.5" Journal tiddlers work too: 2009-01-20 11:26:04,825 INFO 127.0.0.1 - GUEST [20/Jan/ 2009:11:26:04 ] "PUT /bags/w3c/tiddlers/20%20January%202009?n ocache=0.4119574336488333 HTTP/1.1" 204 - "http://127.0.0.1:8080/ recipes/test/tiddlers.wiki" "Mozilla/5.0 (Windows; U; W indows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 Ubiquity/0.1.5" Now i just have to find out how to set the TiddlyWebConfig/ config.defaultCustomFields so I can save in more than one bag Best, tony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~--~~~~--~~--~--~---
[tw] Re: tiddlyweb installation
On Jan 12, 9:48 am, FND 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 ,
http://127.0.0.1:8080/recipes//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 TiddlyWiki@googlegroups.com
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/TiddlyWiki?hl=en
-~--~~~~--~~--~--~---
