Never mind, I went back and looked at your settings.json, and then tested something. And it appears that datafolders are not working correctly if linked to directly. For now, the work around should be to put the data folder inside another folder.
On Sat, Jun 24, 2017 at 12:22 PM, Arlen Beiler <arlen...@gmail.com> wrote: > The top page shows what I set up in settings.json but I am unable to drill >> down and get anything a all. I'll try to set up some bare bones tiddlywiki >> --server contents and see if I get the same results. > > > Let me know what you come up with, because that is the next thing I was > thinking of. Also try using /DayLog/ or whatever the exact casing is and > see if that does anything. Then send me the console output. > > > > On Fri, Jun 23, 2017 at 11:10 PM, jwd <jwd...@gmail.com> wrote: > >> Slightly different results after updating to the current master but still >> no joy. >> >> I now get >> $ node server.js >> Settings file: /Volumes/CM/TiddlyServer/settings.json >> Open you browswer and type in one of the following: >> 192.168.1.14:8080 >> complete >> twboot: 502.720ms >> [2017-06-23T22:48:56.184-0400] GET 302 ::ffff:192.168.1.14 >> /daylog 511.828 ms - >> - >> complete >> twboot: 380.684ms >> [2017-06-23T22:48:56.707-0400] GET 404 ::ffff:192.168.1.14 >> /daylog/ 382.331 ms - >> - >> syncer-server-filesystem: Dispatching 'save' task: >> $:/config/tiddlyweb/host >> FileSystem: Saved file /Volumes/CM/TW/DayLog/tiddlers >> /$__config_tiddlyweb_host.tid >> syncer-server-filesystem: Dispatching 'save' task: $:/StoryList >> FileSystem: Saved file /Volumes/CM/TW/DayLog/tiddlers/$__StoryList.tid >> syncer-server-filesystem: Dispatching 'save' task: >> $:/config/tiddlyweb/host >> FileSystem: Saved file /Volumes/CM/TW/DayLog/tiddlers >> /$__config_tiddlyweb_host.tid >> syncer-server-filesystem: Dispatching 'save' task: $:/StoryList >> FileSystem: Saved file /Volumes/CM/TW/DayLog/tiddlers/$__StoryList.tid >> [2017-06-23T22:52:13.988-0400] GET 200 ::1 / >> 8.746 ms - - >> [2017-06-23T22:52:14.021-0400] GET 200 ::1 /directory.css >> 6.425 ms - 120 >> [2017-06-23T22:52:14.034-0400] GET 200 ::1 /icons/folder.png >> 3.310 ms - 634 >> [2017-06-23T22:52:14.052-0400] GET 200 ::1 /icons/datafolder.png >> 4.695 ms - 839 >> APP 2017-06-23 22:52:14 [IPv6-::1] state error Not Found >> [2017-06-23T22:52:14.078-0400] GET 404 ::1 /icons/category.png >> 8.362 ms - - >> [2017-06-23T22:52:14.947-0400] GET 200 ::1 / >> 8.231 ms - - >> APP 2017-06-23 22:52:15 [IPv6-::1] state error Not Found >> [2017-06-23T22:52:15.100-0400] GET 404 ::1 /icons/category.png >> 8.860 ms - - >> [2017-06-23T22:52:15.110-0400] GET 200 ::1 /favicon.ico >> 13.389 ms - 5430 >> [2017-06-23T22:52:44.676-0400] GET 302 ::1 /daylog >> 4.911 ms - - >> [2017-06-23T22:52:44.704-0400] GET 302 ::1 /daylog >> 2.962 ms - - >> [2017-06-23T22:52:44.714-0400] GET 404 ::1 /daylog/ >> 4.399 ms - - >> >> In answer to your questions >> >> > Isn't your operating system using case sensitive filenames? >> >> Yes it is. I am on MacOS; and while it's filesystem is generally case >> preserving but case insensitive I arrange things so that my TiddlyWiki >> contents are on a case sensitive filesystem. >> >> > Hmm, everything looks good so far. Are there any errors in the web page >> console (F12)? >> >> Nope, nothing in Chrome. Firefox is noting "The character encoding of >> the plain text document was not declared. The document will render with >> garbled text in some browser configurations if the document contains >> characters from outside the US-ASCII range. The character encoding of the >> file needs to be declared in the transfer protocol or file needs to use a >> byte order mark as an encoding signature. daylog" but there is no content >> showing at all on that 'daylog' tiddlywiki page (not even when I display >> page source.) Similarly if I access the page contents with `curl >> http://localhost:8080/daylog. >> >> The top page shows what I set up in settings.json but I am unable to >> drill down and get anything a all. I'll try to set up some bare bones >> tiddlywiki --server contents and see if I get the same results. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWiki" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to tiddlywiki+unsubscr...@googlegroups.com. >> To post to this group, send email to tiddlywiki@googlegroups.com. >> Visit this group at https://groups.google.com/group/tiddlywiki. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/tiddlywiki/4c204afb-4d0e-4ace-a8d9-ad5a8c257e14%40googlegroups.com >> <https://groups.google.com/d/msgid/tiddlywiki/4c204afb-4d0e-4ace-a8d9-ad5a8c257e14%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSQx21MeSffWOosT%2B_-ZmE8iAGZpj7110KLHVhCCnJjqZQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
