feature req.: identify ELOG web pages via META element, posted by Bill Pier on Wed Oct 7 01:31:05 2009
|
* 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!
|
drop in replacement for FCKeditor?, posted by Bill Pier on Thu Jun 10 15:10:19 2010
|
Is it possible to use a drop-in replacement for the FCKeditor? |
Re: drop in replacement for FCKeditor?, posted by Bill Pier on Thu Jul 1 22:59:41 2010
|
| 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. |
|
Re: SQL Database, posted by Bill Pier on Thu Sep 23 17:22:43 2010
|
|
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?
|
|
Global password file together with guest account, posted by Bertram Metz on Thu Apr 8 15:05:43 2004 
|
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 |
|
Re: Global password file together with guest account, posted by Bertram Metz on Thu Apr 8 15:42:52 2004
|
> > 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 |
Re: Global password file together with guest account, posted by Bertram Metz on Tue Apr 13 11:13:53 2004
|
> > Yes, that is what I want.
>
> I implemented a switch "protect selection page" in revision 1.318, which can be
> obtained at http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.318. If this
> switch is not set to "1", the selection page can be seen without having to log in.
Stefan,
thank you for the fast implementation of this feature. I compiled the new revision and
it worked as expected.
Kind regards,
Bertram |
|
Long lines in printout, posted by Bertram Metz on Wed Aug 10 10:50:55 2005
|
Hi,
long lines in an entry are not printed correctly (the lines are cut off), if the text is encoded as plain text. This works correctly, if the text is encoded as ELCode. I tried this with Firefox and Internet Explorer. Does anybody know a solution for this?
Thanks,
Bertram |