ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65871
|
Tue May 6 21:40:05 2008 |
| Bill Pier | bpier@clove.org | Question | Linux | 2.7.3-2058 | any support of encrypted logfiles? |
I'm sure this topic has been visited previously, but a search of this forum didn't show any results.
Is there are support or already proven method of encrypting the logfiles that Elog serves up?
thanks,
Bill
|
66213
|
Thu Feb 19 18:19:12 2009 |
| Bill Pier | bpier@clove.org | Question | All | 2.7.3 | Re: scrollable text section only when viewing a log entry |
Bill Pier wrote: |
IStefan Ritt wrote: |
Bill Pier wrote: |
Stefan Ritt wrote: |
Bill Pier wrote: |
Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?
|
Unfortunately no.
|
Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only", just a few CSS tweaks can enable exactly what I am desiring.
For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:
- moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
- in the style sheet, added attribute "position:fixed" to the "frame table" section;
- in the style sheet, added attribute sections for journal entry content and footer div sections:
- #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
- #footer: text-align:center;bottom:0;position:fixed;width:100%;
Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.
In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release.
|
Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)
|
Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously. I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.
Thu Feb 19 18:18:20 2009 Did this suggestion ever get considered for implementation?
|
|
66555
|
Wed Oct 7 01:31:05 2009 |
| Bill Pier | bpier@clove.org | Request | All | 2.7.7 | feature req.: identify ELOG web pages via META element |
* Withdrawn *
The HTML layout produced by elogd is horrendous to deal with programmatically; I give up.
Hi,
I'm writing a greasemonkey script to slightly alter the look of the pages served by the ELOG server. One difficulty that I'm struggling with is how to identify what type of page ELOG has created. While I have several methods to determine the page type, such as a log entry vs. log entries summary, the solutions are not straight forward and not clean. As far as I tell, there's no specific identification in HTML document currently that describes and identifies the type of page being served by the ELOG server.
So, I'm requesting that the pages created by ELOG be identified in some fashion with the META element, such as:
<meta name="description" content="elog log entry" />
or
<meta name="description" content="elog log summary" />
or even using the keywords attribute:
<meta name="keywords" content="elog log summary" />
Thanks!
|
66845
|
Thu Jun 10 15:10:19 2010 |
| Bill Pier | bpier@clove.org | Question | Linux | 2.7.8 | drop in replacement for FCKeditor? |
Is it possible to use a drop-in replacement for the FCKeditor? |
66848
|
Thu Jul 1 22:59:41 2010 |
| Bill Pier | bpier@clove.org | Question | Linux | 2.7.8 | Re: drop in replacement for FCKeditor? |
Stefan Ritt wrote: |
Bill Pier wrote: |
Is it possible to use a drop-in replacement for the FCKeditor?
|
What is a drop-in replacement?
|
A configuration option to specify a different/alternate javascript based editor. |
66915
|
Thu Sep 23 17:22:43 2010 |
| Bill Pier | bpier@clove.org | Question | Windows | 2.7.6-2230 | Re: SQL Database |
What about using something like MySQLfs to get a db backend transparently to ELOG? I use ENCFS, (a FUSE backend), currently to achieve encrypted logbooks and it works fine -- ELOG never knows anything other than reading and writing to logbook files. From what I've read, the MySQLfs backend would work the same, and you likely would gain some of the caching benefits of MySQL, which might help with your read/search times, given the memory requirements of the database of course.
Bill
lance wrote:
|
We have been running elog for a few years now and its solid. The only thing is we are getting to 140k entries over a few books and its starting to slow down whist searching. My questions is can we go to an SQL type database rather than a flat file? Is it worth it? Is anyone running this type of configuration?
|
|
523
|
Thu Apr 8 15:05:43 2004 |
| Bertram Metz | bmetz@sbs.com | Question | Windows | 2.5.2 | Global password file together with guest account |
Hello,
is it possible to have an guest account together with a global password file?
I tried to put the password file statement into the global section of
elogd.cfg. But in this case every user must login and it is not possible to
have a read only guest account.
But if I put the password file statemnet into the logbook sections, it is
possible to access the logbooks in read-only mode without logging in. The
drawback of this solution is, that you have to login into every logbook
seperately.
Bertram |
525
|
Thu Apr 8 15:42:52 2004 |
| Bertram Metz | bmetz@sbs.com | Question | Windows | 2.5.2 | Re: Global password file together with guest account |
> > Hello,
> >
> > is it possible to have an guest account together with a global password file?
> >
> > I tried to put the password file statement into the global section of
> > elogd.cfg. But in this case every user must login and it is not possible to
> > have a read only guest account.
> > But if I put the password file statemnet into the logbook sections, it is
> > possible to access the logbooks in read-only mode without logging in. The
> > drawback of this solution is, that you have to login into every logbook
> > seperately.
> >
> > Bertram
>
> Right, guest access is not possible with a global password file. This comes from
> the fact that people wish to protect their logbook selection page. What I can do
> is add another flag "protect selection page = 0 | 1". If "0", the logbook
> selection page can be seen without logging in. Is that what yo want?
>
> - Stefan
Yes, that is what I want.
Bertram |