I got a report of an error last night, and this morning alright. Last night was due to an accidental import statement that somehow slipped in before I did my commit - that's been fixed. This morning, I only noticed it now so I'm not 100% certain why, but I'll take a glance at it.
Files are not yet uploadable via the web interface, but I'll be working on that today. The subpages was a bit of a quick hack so that pages wouldn't get completely lost if nothing linked to them. A tree widget would be nice alright. Perhaps you could file a bug about the things you need/want most? That way they can be tracked and I can work towards them. As for "home.html" and "home", well they're essentially the same thing. The url's are supposed to be "nice", so they will always display "mypage" rather than "mypage.html", but links can point to "mypage.html" - url will change to "mypage". The internal link browser will always point to the "mypage.html" though. Reason for this is that the content is stored in flat files, and is browseable without anyserver or style sheets and links will still work as they use real file names. I can see why this is misleading though and might change the breadcrum navigation to display the page without the ".html" extention. Maybe I should create a google groups list for discussing this further... Tim ^,^ On Thu, Aug 28, 2008 at 7:06 AM, Thomas Guettler <[EMAIL PROTECTED]> wrote: > > Hi, > > I just tested your demo. Somehow there were some 500 pages (internal > server error). > > Nevertheless it looks to have most features I need. > > I the top, I would not display "home.html" but only "home". And the > subpages should > be a tree. But I guess that can be customized or hacked somehow. > > How can you upload files? > > Thomas > > Tim Kersten schrieb: >> Yes, quite correct, it doesn't require a database. I wanted to keep >> the requirements as minimal as possbile and thought it would be good >> to let something designed for keeping revisions do the heavy lifting. >> I know I have a good way to go with timiki yet, but it's already in >> heavy use and therefor under improvement. >> >> I can understand you prefering a database solution and it was a >> difficult decision not to use a database. In the end I wanted >> something that would be easy to deal with in the case of something >> going wrong. The urls have a 1-to-1 mapping with the files on the file >> system, so backups, restores and exporting/importing any data should >> be simple as the entire content is pure (x)html. >> >> I just set up a demo page here so that progress can be viewed: >> http://timikidemo.io41.com/ >> >> Tim ^,^ >> >> >> > > -- > Thomas Guettler, http://www.thomas-guettler.de/ > E-Mail: guettli (*) thomas-guettler + de > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
