ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
974
|
Mon Mar 7 16:05:22 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | rev. 1.51 | Display <attribute> do erroneously encoded |
Display subject = <b>$subject</b>
is printed to the browser encoded, so that it is diplayed as is.. |
975
|
Tue Mar 8 13:16:14 2005 |
| Paul Harrington | paul.harrington@oup.com | Question | All | | Re: length of fields |
The reason for the earlier question is that we are trying to use Elog to store
data in a form we'd need to store more 1500 characters in more than one field.
Is it possible to get around this problem by having more then one main text field
per record?
thanks
Paul
> > > When creating/updating entries in elog, excluding the main text field are
> > > there any limits on the size of the other fields?
> >
> > Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
> > currently set to 1500 characters. You can try to increase this and recompile,
> > but at some point you will produce a stack overflow and elogd will crash. So
> > the current length is a compromise.
> >
> > - Stefan
>
> Thanks. Thats useful to know.
>
> Paul |
979
|
Tue Mar 8 20:28:49 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: length of fields |
> Is it possible to get around this problem by having more then one main text field
> per record?
No, not at the moment. You can increase the 1500 characters by recompiling elogd, but
at some point you will hit the stack limit and elogd will crash. I plan a major
redesign with completely dynamic memory allocation, thus permitting any number of
characters on any attribute. But this will take a couple of months or so. |
982
|
Mon Mar 14 21:11:11 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | rev. 1.51 | Re: Display <attribute> do erroneously encoded |
>
> Display subject = <b>$subject</b>
>
> is printed to the browser encoded, so that it is diplayed as is..
I fixed that in revision 1.587. Note however that you should do the formatting
of attributes better using the CSS functionality, since it gives you more
possibilities. See for example the subject of this forum, which has it's own
CSS class "subjname", which has a larger font size. You select your own class like
Format Subject = 0, subjname, subjvalue
in the configuration file. Then add the classes into the CSS file.
Now elog shows each attribute which contains a "<b>" encoded (as HTML). But if you
want to write a subject line like "For bold use <b> in HTML", then the "<b>"
triggers the HTML display, so it is not written as is, which is not what you want in
that case. Since there is no switch "Submit as HTML text" for the attributes, it is
hard for elog to "guess" if you want HTML encoded or not. |
995
|
Fri Mar 18 11:14:58 2005 |
| Rob de Bruin | rdbruin@zernike.nl | Question | All | 2.5.6 | Asing a user to an log |
Hello,
I'm looking for an option to attach a user to a log?
For example:
Rob is making the log, and whant's to dedicate the log to a stagaire,
the stagiare recieves an E-mail so that he can do the job?
Bud we all want recieve the mail bud the stagiare see's that the job is for
him.
Is there a solution for it?
Best regards Rob de Bruin |
996
|
Fri Mar 18 13:36:19 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.5.6 | Re: Asing a user to an log |
> I'm looking for an option to attach a user to a log?
>
> For example:
>
> Rob is making the log, and whant's to dedicate the log to a stagaire,
> the stagiare recieves an E-mail so that he can do the job?
>
> Bud we all want recieve the mail bud the stagiare see's that the job is for
> him.
Maybe use an attribute for that?
Like
Attributes = Author, ..., stagaire
Options stagaire = Jim, Joe, ...
So Rob can select a stagaire from the list, and the email contains this name.
- Stefan |
1018
|
Thu Mar 24 13:21:28 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | 2.5.8 | Re: HTML 4.1 transitional validation fails |
> as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> it should be used an HTML entity instead of the ampersand sign.
Stefan, the validation still fails on the ampersand ...
here is an example of your online Demo elog:
http://validator.w3.org/check?verbose=1&uri=http%3A//midas.psi.ch/elogs/Forum/920 |
1020
|
Thu Mar 24 13:59:06 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.5.8 | Re: HTML 4.1 transitional validation fails |
> Stefan, the validation still fails on the ampersand ...
> here is an example of your online Demo elog:
> http://validator.w3.org/check?verbose=1&uri=http%3A//midas.psi.ch/elogs/Forum/920
Ok, I fixed that, the validation link above show a valid page. |