Re: Pre-fill Attribute with last entry, posted by Stefan Ritt on Wed Mar 24 19:45:41 2021
|
That would actually be my recommendation. There is a "execute new" which you can call when submitting a new entry.
Stefan
Dominic |
Re: Pre-fill Attribute with last entry, posted by Dominic Schneider on Thu Mar 25 07:48:24 2021
|
Thank you very much.
So far I testet all functionalities and scripts to reach my goal. I will post a dummy of the solution later on for future purposes.
Best wishes |
Re: Pre-fill Attribute with last entry, posted by Sebastian Schenk on Thu Mar 25 12:50:08 2021
|
I am glad, we could help.
I can see a caveat in the recommendation.
By having "Execute New = echo $attrib > /path/last_attrib" and "Preset attrib = $shell(cat /path/last_attrib)" as the most |
Re: Pre-fill Attribute with last entry, posted by Richard Stamper on Tue Mar 30 13:43:46 2021
|
Just noting that, depending on what you want to achieve, you may be able to use the threading functionality so that a "new" entry is actually
a "reply" to a previous entry. This will allow you to populate attributes with values from that previous entry without having to rely on
storing information outside the system, with all the attendant concurrency risks already identified. |
Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?, posted by Niklas Hoglund on Mon Jun 19 07:48:49 2017
|
Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?
Example:
toc()
< h1>test
< h2>test1
< h1>test2
< h2>test3
< h1>test4 |
Re: Is it possible to generate a table of contents based on h1/h2/h3 HTML tags?, posted by Stefan Ritt on Mon Jun 19 08:33:07 2017
|
This is not possible.
Stefan
Niklas |
my elogd crashes when editing the configuration, posted by Niklas Hoglund on Tue Jun 20 14:32:29 2017
|
Hi,
my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?
|
Re: my elogd crashes when editing the configuration, posted by Stefan Ritt on Thu Jun 22 20:55:36 2017
|
Might be some bad data in your elogd.cfg file. Have a look at that file with a text editor to see if there's anything wrong. Start with a pristine config
file from the
|