Re: Response is very slow with beta3, posted by Emiliano Gabrielli on Thu Aug 4 11:19:53 2005
|
[quote="Stefan Ritt"][quote="Emiliano Gabrielli"]for every image elog has to serve one can see something similar to the above ... lot of time lost in selects..
then a lot of data (serving an image I suppose), then a lot of time in select again and again ... untill everything is sent, in a couple of minutes or
more ;-(
|
|
Re: Reset a user's password, posted by Stefan Ritt on Fri Oct 28 16:41:11 2016
|
Sure. Hit "Config", select other user, and click on "Change password".
Stefan
Val |
|
Re: Required and {}, posted by Stefan Ritt on Fri Feb 16 17:19:30 2007
|
[quote="bob"]generally, can one handle "Required" and "{}" or "{ , }", ...[/quote]
For simple configuration files, that should work. If I have for example:
|
|
Re: Required and {}, posted by bob on Mon Feb 19 20:46:39 2007
|
[quote="Stefan Ritt"][quote="bob"]generally, can one handle "Required" and "{}" or "{ , }", ...[/quote]
For simple configuration files, that should work. If I have for example:
|
|
Re: Required Attributes, posted by Stefan Ritt on Fri May 14 17:03:36 2010
|
Eric Krise wrote:
Is there a way to require a certain attribute on reply, but not on an original entry? In some |
|
Re: Request: make $text available for "subst", posted by Stefan Ritt on Mon Mar 22 15:10:12 2021
|
$text is the full body text and can go over many lines. Since attributes are restricted to single lines, it's not possible to substitute them with
the body text.
Stefan |
|
Re: Request: make $text available for "subst", posted by Andreas Luedeke on Mon Mar 22 19:59:13 2021
|
While the input widget of text attributes is a single line, they can easily be multi-line in the display - when you use HTML at least.
And of course the user can parse the text field and generate a single line, if he wants to.
If you leave it to me, I'll create wonderful applications to that feature :-) |
|
Re: Request: make $text available for "subst", posted by Sebastian Schenk on Tue Mar 23 13:42:27 2021
|
I am not Stefan, but maybe I can add to this issue.
Personally I think it is not a good way to dump all the information into the text field and try to let the server parse it.
This could be archived more simply by using e.g. the python elog scripts or using the elog command tool to directly submit well structured elog |