From: Johan V. <jvr...@sq...> - 2008-11-01 11:04:17
|
"Stéphane Charette" <ste...@gm...> writes: > As I think about this some more, other ideas come to mind: Actually, only one. > 1) creating .htaccess for the entire NarrativeWeb tree > 2) placing .htaccess only media directories > 3) placing .htaccess only in subdirectories, meaning all the indexes > remain available These 3 options are not really GRAMPS tasks. The necessary .htaccess files are easily created manually by the user (they need manual intervention, anyway) and should stay untouched when a new tree is generated. > 4) placing .htaccess only in directories with html pages and images of > people that are alive It would be sufficient to have a directory 'private' that contains all the sensitive pages. It may contain a shadow file system tree for convenience: gallery.html images/ img/ index.html ... plc/ ppl/ private/ gallery.html images/ img/ index.html ... thumb/ sources.html src/ ... thumb/ Again, the user needs to place a .htaccess in the private directory only once since it should stay untouched when a new tree is generated. This also opens the possibility to always show the 'public' pages, and provide a link 'Show full info (requires authentication)' on pages that have a private counterpart. It may be easier, though, to generate two trees: index.html private/ gallery.html images/ img/ index.html ... thumb/ public/ gallery.html images/ img/ index.html ... thumb/ It is a bit more work (two passes), but requires less changes to the way the pages are written out. On systems that support linking, the public and private pages that are indentical could be linked to save space. Note that generating two trees is currently already possible with carefully chosen report options and a simple script: #!/bin/sh gramps -a report -p name=navwebpage,target=web/private,living=99,incpriv=1 gramps -a report -p name=navwebpage,target=web/public,living=2,incpriv=0 -- Johan |