html code in reply window, posted by Tom Plancon on Thu Jul 31 17:16:20 2008
|
Hello,
Recently upgraded to 2.7.3 and I'm seeing html code filling up the reply window. Before I would just see [quote] and [/quote] around the original entry. Did I miss something in the upgrade? Thanks! |
Re: html code in reply window, posted by Stefan Ritt on Thu Jul 31 17:22:23 2008
|
| Tom Plancon wrote: |
|
Hello,
Recently upgraded to 2.7.3 and I'm seeing html code filling up the reply window. Before I would just see [quote] and [/quote] around the original entry. Did I miss something in the upgrade? Thanks!
|
Probably you did not install the FCKeditor. Just try a reply to this message, and you will see the many formatting icons on top of the page coming from that HTML editor. Without the editor, you will only see the plain HTML. You can switch back however to the old behavior by selecting the ELCode encoding. You can make this permanent with the "Default encoding =0" option. |
|
2 questions :: different colors in list view based on "type" + change verbage of "type", posted by dale cooper on Fri Aug 8 00:44:26 2008
|
hello all,
#1 i love ELOG : excellent app! i would like to ask/present a question here -- I have a couple of TYPE's defined as;
Options Type = Day Shift, Swing Shift, Night Shift
What I'd love to be able to do, is depending on what TYPE was selected during the creation of a NEW ENTRY in the ELOG "shift log" I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...
for example, if someone chose "Day Shift" that would be listed with a GREEN background, if someone chooses "Swing Shift" that gets a BLUE background, and so forth... I am wondering how one would go about implementing this?
second question... instead of listing the column named TYPE, can I just change it somewhere in the config to "SHIFT" so that in the list view, and even when in the NEW ENTRY form, I'd like it to show "Shift" instead of TYPE --- really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?
Thanks for the app, I look forward to any reponses! I been editing the CSS, and once done think I'll add it to yr Config Examples, as I don't see many CSS themes there...
-peace- |
|
Re: 2 questions :: different colors in list view based on "type" + change verbage of "type", posted by Yoshio Imai on Fri Aug 8 14:20:27 2008
|
| dale cooper wrote: | | I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected... |
You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should addStyle Shift Day = background-color:green
Style Shift Swing = background-color:blue (and so on) to the config file.
| Quote: | | really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable? |
As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a lineAttributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on> and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ... |
|
Re: 2 questions :: different colors in list view based on "type" + change verbage of "type", posted by dale cooper on Mon Aug 11 06:56:56 2008
|
PERFECT, you answered my questions EXACTLY with what I am looking for! thanks soo much!
agentdcooper
| Yoshio Imai wrote: |
| dale cooper wrote: | | I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected... |
You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should addStyle Shift Day = background-color:green
Style Shift Swing = background-color:blue (and so on) to the config file.
| Quote: | | really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable? |
As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a lineAttributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on> and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ... |
|
|
Deny Wildcards, posted by Neo on Wed Oct 8 15:10:25 2008
|
|
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ...
Allow New = admin1, admin2, admin3
Allow Edit = admin1, admin2, admin3
Deny New = *
Deny Edit = * |
|
Re: Deny Wildcards, posted by Stefan Ritt on Wed Oct 8 15:23:56 2008
|
| Neo wrote: |
| Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = * |
Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them. |
|
Re: Deny Wildcards, posted by Neo on Wed Oct 8 15:31:49 2008
|
| Stefan Ritt wrote: |
|
| Neo wrote: |
| Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = * |
Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them.
|
I tried it in a global group configuration
[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1
But I as admin2 am still able to create new entries in the corresponding log books.
Is this configuration only for logbooks? |
|