| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68505
|
Thu Dec 15 14:44:32 2016 |
 | Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Bug report | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
Hello Stefan, thanks for your answer. So I made a new logbook, without entries. I generated, as you, two new entries and I discover that this problem come out when in the URL the command for the sorting follow the command of the display mode. So for example the following URL give me the issue:
http://local.host.com:8080/65+nm/?mode=summary&sort=Record+date
But if I put:
http://local.host.com:8080/65+nm/?sort=Record+date&mode=summary
This last URL is working. This means that the issue come out, when I change the dispay mode by the buttons "Full, Summary, Threaded" and then I click on the Coloumn "Record date" for sorting it. Hope you understand and you can reproduce it. Many thanks
EDIT: I'm facing the same problem on another MAC with a fresh installation of elogd.
| Stefan Ritt wrote: |
|
I tried your config file on my Mac and it just worked fine without any crash:
Could it be that on entry has corrupt data and is killing your server? Have you tried on a pristine new logbook?
Stefan
| stefano bonaldo wrote: |
|
Hello,
I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded.
For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL:
http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date
Can you please help me?
Here I reduced my elogd.cfg at minimum and I still get this issue:
[global]
port = 8080
[65 nm]
Attributes = Record date
Type Record date = datetime
Preset Record date = $date
List Display = Record date
Start page = ?sort=Record date
|
|
|
|
68506
|
Thu Dec 15 15:04:53 2016 |
| Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Question | Mac OSX | 3.1.2 | Re: MacOS install failure - cannot find ssl.h |
Currently, in my MacBook Pro with Sierre, the search path /opt/local/include of the prprocessor is not included.
cpp -v
Apple LLVM version 8.0.0 (clang-800.0.38)
Target: x86_64-apple-darwin16.1.0
....
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/8.0.0/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
/usr/include
/System/Library/Frameworks (framework directory)
/Library/Frameworks (framework directory) |
|
68509
|
Fri Dec 16 02:44:53 2016 |
| Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Bug report | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
Hello Alan,
I tried with a new logbook with an attribute without "date" name, but unfortunately I got the same error. Any other suggestions?
Thanks
| Alan Grant wrote: |
|
Hi Stefano.
This may or may not have anything to do with your specific problem but I notice you have the single word "date" as part of your attribute name and Date is actually a reserved word in Elog. Although your attribute is not exclusively called "date" I have found that even using "date" as an isolated word within an attribute name (eg: Record date vs Record_date) can cause some issues. In my case, it caused a problem with the elog client when trying to update records which was only resolved when I changed the name of the attribute to Date/Time Received from Date and Time Received. Long story short, I avoid using any reserved words as part of attribute names.
Alan.
| stefano bonaldo wrote: |
|
Hello,
I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded.
For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL:
http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date
Can you please help me?
Here I reduced my elogd.cfg at minimum and I still get this issue:
[global]
port = 8080
[65 nm]
Attributes = Record date
Type Record date = datetime
Preset Record date = $date
List Display = Record date
Start page = ?sort=Record date
|
|
|
|
68512
|
Fri Dec 16 14:44:19 2016 |
 | Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Bug fix | Mac OSX | 3.1.2 | Re: elogd crash on sorting the entries by an datetime attribute |
Bug FIXED! Many thanks Stefan and my warmest congratulations for the elog project.
Stefano
| Stefan Ritt wrote: |
|
Ok I found it!
Was tricky. In my development environment (XCode) it worked fine. Only when I compiled elogd under Sierra on the command line, the probelm occured. That's why I did not see it earlier. It has to do with some functions Apple apparently changed ("strlcpy"). These function now have a new "functionality": When two parameters overlap, the function just aborts the process. This is specific to Sierre, so on any other Linux this does not happen. I changed now the soruce code to take care of the modified functions, and now it works fine. Please update to the newest GIT revision of elogd and recompile.
Stefan
|
|
|
68676
|
Tue Aug 22 18:29:02 2017 |
 | Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Question | Mac OSX | v3.1.2 | Hide logbook tab when not authorized |
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? |
|
68679
|
Wed Aug 23 20:09:39 2017 |
| Stefano Bonaldo | stefano.bonaldo.13@gmail.com | Question | Mac OSX | v3.1.2 | Re: Hide logbook tab when not authorized |
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?
|
|
|
|
Draft
|
Wed Sep 23 23:57:43 2015 |
 | Stefano | stefano.colafranceschi@gmail.com | Question | Linux | 3.1.0 | elog from php |
Hi,
I need to run elog command in an online php script. The problem I see is that the script works from the command line but not from the browser. In the script I just use:
system(elog -h mypc -p 8080 -l bla -a Author=\'io\' -a Type=\' ..etc.etc
any suggestions? |
|
68128
|
Sat Sep 26 03:34:44 2015 |
| Stefano | stefano.colafranceschi@gmail.com | Question | Linux | 3.1.0 | Re: Elog command not working properly |
Yes it was a path issue PHP was not loading correctly environmental path
> > <p>Hi,</p>
> >
> > <p>I have a problem running elog command from php script. Basically in the php I call system("elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache
> logfile no problem), any suggestions?</p>
>
> Hey,
> this sounds more like a PHP issue.
> Which PHP version are you using?
> Which webserver?
> Which php function are you using: shell_exec() or exec()? Try looking at the return of exec()
> Is the elog file set to the correct file permissions to be executed by the webserver?
> Is the elog file in the PHP path or do you take care of defining the correct path?
>
>
> eddy |