Re: Paste figure from Clipboard, CKEditor 4.5.1 and Firefox 42, posted by Simon Däster on Mon Nov 23 10:32:37 2015
|
Updating CKeditor did work, thanks for the tip. |
unknown user name in "Admin user" line invalidates all entries, posted by Hanno Perrey on Wed Jun 17 10:52:16 2015
|
Hej,
I just noted that when having an unknown (or presumably misspelled) user name in the "Admin user" line in the
config file, that the other users are no longer treated as admins and do not see the corresponding link to the
admin page e.g. on the list page. In my specific situation, I in fact have only one user registered (new
password file) but two users still on the admin list (old config file). The one user is only treated as admin
after removing the offending name from the list of admins.
I understand that this might be the intended behavior -- but I wonder if this could lead to a situation where
one locks oneself out, e.g. when adding a misspelled user name to the list.
Thanks and cheers,
Hanno |
Draft saved is treated as an entry edit, posted by Daniel Sajdyk on Fri Aug 28 21:01:42 2015
|
Hello.
In Elog i have attribute called "Zmieniano" (eng. changed) which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)".
From version V3.1.1-3f311c5 I have problem with that.
When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:
- Oryginalny wpis (eng. oryginal entry),
- Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... )
The second value is autosave time.
Is this a bug?
Regards
Daniel.
|
Re: Draft saved is treated as an entry edit, posted by Andreas Luedeke on Mon Aug 31 09:38:38 2015
|
Hi Daniel,
this is an undesired side effect of a new feature. I wouldn't call it a bug ;-)
There is no straight forward way for elog to distinguish between a "Submit" and an automatic save. Therefore the "... on edit = ..." kicks in when an entry is saved automatically.
I guess Stefan can figure out a workaround, but for the moment I would sugest that you just switch off the auto save feature -- if you want to keep your save history:
Save drafts = 0
Cheers
Andreas
Daniel Sajdyk wrote:Save drafts = 0 |
Hello.
In Elog i have attribute called "Zmieniano" (eng. changed) which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)".
From version V3.1.1-3f311c5 I have problem with that.
When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:
- Oryginalny wpis (eng. oryginal entry),
- Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... )
The second value is autosave time.
Is this a bug?
Regards
Daniel.
|
|
Re: Draft saved is treated as an entry edit, posted by Daniel Sajdyk on Mon Aug 31 13:12:09 2015
|
Hi Andreas and thank you very much for explanation ;)
So, we'll have to wait for new version which will correct this.
Cheers
Daniel.
Andreas Luedeke wrote: |
Hi Daniel,
this is an undesired side effect of a new feature. I wouldn't call it a bug ;-)
There is no straight forward way for elog to distinguish between a "Submit" and an automatic save. Therefore the "... on edit = ..." kicks in when an entry is saved automatically.
I guess Stefan can figure out a workaround, but for the moment I would sugest that you just switch off the auto save feature -- if you want to keep your save history:
Save drafts = 0
Cheers
Andreas
Daniel Sajdyk wrote:Save drafts = 0 |
Hello.
In Elog i have attribute called "Zmieniano" (eng. changed) which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)".
From version V3.1.1-3f311c5 I have problem with that.
When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:
- Oryginalny wpis (eng. oryginal entry),
- Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... )
The second value is autosave time.
Is this a bug?
Regards
Daniel.
|
|
|
Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 08:06:36 2016
|
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
Re: Multiple outcomes to a conditional attribute, posted by Andreas Luedeke on Tue Jul 12 08:31:37 2016
|
Hi Sofian,
it should work like this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif
It is described under "Multiple conditions" in the documentation (https://midas.psi.ch/elog/config.html#conditional).
Cheers and good luck!
Andreas
Sofian Jafar wrote: |
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
|
Re: Multiple outcomes to a conditional attribute, posted by Stefan Ritt on Tue Jul 12 08:37:42 2016
|
What about this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif
-Stefan
Sofian Jafar wrote: |
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
|
|