Re: Sharing logbooks among "Top Groups", posted by Andreas Luedeke on Mon Aug 21 08:51:09 2017
|
Hi Satyajit,
I think you've just answered your own question. There is no magic switch - as far as I know - that would change that behaviour.
Probably there are ways to achieve your desired behaviour (using mirror servers and synchronising the logbooks) but that would require a large effort and would make your installation a lot more complicated.
With kind regards, Andreas
| Satyajit Jena wrote: |
|
Hi,
I tried without success. Logbook is not sharing, it is displaying only under one "Top Group" whereever it appears first.
With regards,
satyajit
| Andreas Luedeke wrote: |
|
I don't know if that works. Why don't you just try?
| Satyajit Jena wrote: |
|
Hi,
I am currently trying to configuring elog top groups, which are supposed to separate from each other. However, I would like to have a common logbook that should be visible in each group. Is there a way to share logbooks among Top Groups for example
Top Group Electronics = Elec1, Elec_EEE, Ele2
Top Group Processing = P_AA1, PPP2, Elec_EEE
Top Group Monitoring = Mon1, Mon2, Mon3, Mon4
Top Group Data = Data1, PPP2, Data2
I would like logbook to be viewed:
- Electronics:
- Processing:
- Monitoring:
- Data:
- Data1
- PPP2
- Data2
- Mon3
- Mon4
Could you please suggest me if it is possible to set in this way (Color codes t show the common sharing).
Many thanks and regards,
satyajit
|
|
|
|
|
Re: Bug with Drafts and Language German, posted by Andreas Luedeke on Mon Aug 21 12:16:05 2017
|
I've quickly checked: there are a couple more commands in the source code that are not language encoded. I guess some of them needs correction.
> egrep -n "cmd=[A-Za-z]" elogd.c
10293: rsprintf(" r.open('GET', '?jcmd=Unlock&edit_id=%d', true);\n", message_id);
11784: ("<label for=\"ELCode\"><a target=\"_blank\" href=\"?cmd=HelpELCode\">ELCode</a> </label>\n");
13663: "\r\n%s URL : %s?cmd=Config&cfg_user=%s&unm=%s\r\n", loc("Logbook"),
14562: redirect(lbs, "?cmd=Config");
14625: sprintf(str, "../%s/?cmd=Config", getparam("lbname"));
14678: sprintf(str, "../%s/?cmd=Config", lbn);
15703: combine_url(lbs, host, "?cmd=GetMD5", url, sizeof(url), &ssl);
16378: strcat(str, "?cmd=GetConfig"); // request complete config file
16380: strcat(str, "?cmd=Download"); // request config section of logbook
16570: strcat(str, "?cmd=GetPwdFile"); // request password file
17575: rsprintf("<br><b><a href=\"../%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
17577: rsprintf("<br><b><a href=\"%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
17579: rsprintf("<br><b><a href=\"../%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
18959: if (strstr(ref, "cmd=Search&"))
18960: strlcpy(strstr(ref, "cmd=Search&"), strstr(ref, "cmd=Search&") + 11, sizeof(str));
26728: rsprintf("<a href=\"?cmd=Synchronize\">%s</a></td>\n", loc("Synchronize all logbooks"));
| Andreas Luedeke wrote: |
|
Hi Stefan,
when one creates a new entry, and a draft entry exists for the logbook, then a menu appears (see attachment).
If one select "Neuen Eintrag anlegen" then it should ignore the draft and create a new entry.
This feat is done by adding a "&ignore=1" to the "new" command: "<URL>/?cmd=New&ignore=1".
The problem is, that it should not be "cmd=New&..." but "cmd=Neu", since the commands are part of the translation.
Due to this, no new entry can be created as long as a draft exists; at least not in any language other than english.
This problem apparently existed since the beginning of drafts, but it only created problems at our site recently.
Kind Regards
Andreas
PS: Here's a patch that works:
diff elogd.c elogd.c-orig
9575,9576c9575,9576
< rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='?cmd=%s&ignore=1';\">\n", loc("Create new entry"),
< loc("New"));
---
> rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='%s';\">\n", loc("Create new entry"),
> "?cmd=New&ignore=1");
|
|
|
Re: HTML in attribute values, posted by Stefan Ritt on Tue Aug 22 14:26:42 2017
|
- As you can see...
- <UL> is possible
| Richard Stamper wrote: |
|
When one has "Allow HTML = 1" to permit HTML in attribute values, is it only a subset of HTML that is rendered?
I find that <br> and <a href="..."> tags are properly rendered, for example, but lists with <ol> and <ul> are not.
|
|
|
Re: HTML in attribute values, posted by Richard Stamper on Tue Aug 22 14:36:46 2017
|
Isn't that list in the message text rather than as an attribute value?
| Stefan Ritt wrote: |
- As you can see...
- <UL> is possible
| Richard Stamper wrote: |
|
When one has "Allow HTML = 1" to permit HTML in attribute values, is it only a subset of HTML that is rendered?
I find that <br> and <a href="..."> tags are properly rendered, for example, but lists with <ol> and <ul> are not.
|
|
|
|
Re: HTML in attribute values, posted by Stefan Ritt on Tue Aug 22 14:37:44 2017
|
Sorry, I misread your question. Only following HTML tags are allowed in attributes:
<a>
<img>
<b>
<i>
<p>
<br>
<hr>
This is for some internal reason. Probably you can mimick <ul> with bullets and <p> tags.
Stefan
| Richard Stamper wrote: |
|
Isn't that list in the message text rather than as an attribute value?
| Stefan Ritt wrote: |
- As you can see...
- <UL> is possible
| Richard Stamper wrote: |
|
When one has "Allow HTML = 1" to permit HTML in attribute values, is it only a subset of HTML that is rendered?
I find that <br> and <a href="..."> tags are properly rendered, for example, but lists with <ol> and <ul> are not.
|
|
|
|
|
Re: Hide logbook tab when not authorized, posted by Andreas Luedeke on Wed Aug 23 11:36:22 2017
|
Hi Stefano,
I think your assessment is correct: it is not possible to hide a logbook based on your read/write privileges.
And I'm not even sure that this would make much sense: at least you need to be able to get to the login page of the logbook.
But if you don't have read privileges for a logbook, you'll be automatically redirected to the login page, as soon as you select this logbook.
Kind Regards, Andreas
| Stefano Bonaldo wrote: |
|
Hello, I read carefully the manual, but I didn't find a way to hide the logbooks in the logbook bar and in the initial logbook selection for which the user does not have the access. So, if a user1 does not have the access to a specific logbook, user1 is not able to see that logbook in the bar and neither in the initial logbook selection. How can I do this without using the top groups?
|
|
|
Re: Problems with german_UTF8 language, posted by Andreas Luedeke on Wed Aug 23 15:11:32 2017
|
Just an update: I've re-compiled, reinstalled and restarted elogd for other reasons and now the corrupted strings are all gone. Everthing looks fine now.
But I never worry when a problem goes away before I could understand it: I'm confident that I will have plenty of time later, when the problem magically re-appears - likely I'll be called on a Friday night :-)
| Andreas Luedeke wrote: |
|
Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas
|
|
|
Re: Hide logbook tab when not authorized, posted by Stefano Bonaldo on Wed Aug 23 20:09:39 2017
|
Hi Andreas,
many thanks for your answer. I partially agree with you, because sometimes "for privacy" of my working group I don't want that other users (external users) know the existance of the other logbooks.
Do you think that will be implemented in future?
Best regards, Stefano
| Andreas Luedeke wrote: |
|
Hi Stefano,
I think your assessment is correct: it is not possible to hide a logbook based on your read/write privileges.
And I'm not even sure that this would make much sense: at least you need to be able to get to the login page of the logbook.
But if you don't have read privileges for a logbook, you'll be automatically redirected to the login page, as soon as you select this logbook.
Kind Regards, Andreas
| Stefano Bonaldo wrote: |
|
Hello, I read carefully the manual, but I didn't find a way to hide the logbooks in the logbook bar and in the initial logbook selection for which the user does not have the access. So, if a user1 does not have the access to a specific logbook, user1 is not able to see that logbook in the bar and neither in the initial logbook selection. How can I do this without using the top groups?
|
|
|
|