ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 456 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6460 Entries

Goto page Previous 1, 2, 3 ... 455, 456, 457 ... 806, 807, 808 Next

Thu Aug 5 12:26:12 2010

Re: Important security update of ELOG

Stefan Ritt wrote:

Dear ELOG users,

this is to announce an important security update. As proposed by Lukasz Olejnik (CERN/PSNC), ELOG has now switched to strong encryption of password. So everybody concerned in security is advised to update to the new version 2.8.0. Existing password files for Windows users and Linux users not using HAVE_CRYPT are automatically converted. Those installations which used HAVE_CRYPT in the past under Linux have to ask their users to re-enter their password (via the link "Forgot password") after the upgrade to version 2.8.0.

Best regards,

Stefan Ritt

I just realized that the command line elog utility did not yet use the new encryption. So automatic elog submissions using passwords are broken in version 2.8.0. I made an intermediate version 2.8.0-2 which fixes that. However you only need to update it if you use the elog utility and have problems with the 2.8.0 version.

2210

Tue Apr 24 12:26:32 2007

bob wrote:

Hi,
it is possible to import the file *.log of Elog towards another Elog?
thank you
Bob

There are three methods:

Copy over the *.log files from one Elog to the other. Make sure not to have entries with the same ID twice then.
Set-up mirroring between two servers. This ensures a 1:1 copy of the server
Export entries in CSV format (comma-separated-values) via 'Find', 'Mode = CSV', and do a 'CSV import' on the other side.

2211

Tue Apr 24 14:43:07 2007

Stefan Ritt wrote:

bob wrote:

Hi,
it is possible to import the file *.log of Elog towards another Elog?
thank you
Bob

There are three methods:

Copy over the *.log files from one Elog to the other. Make sure not to have entries with the same ID twice then.
Set-up mirroring between two servers. This ensures a 1:1 copy of the server
Export entries in CSV format (comma-separated-values) via 'Find', 'Mode = CSV', and do a 'CSV import' on the other side.

thank you,
but the last method (simplest for me) does not import the comment.
it's a pity...

2228

Thu May 10 13:03:51 2007

bob wrote:

thank you,
but the last method (simplest for me) does not import the comment.
it's a pity...

Ok, I implemented the XML import which also includes the text body. However there are currently two limitations:

If you want to import entries which contain replies, it only works if import them into an empty logbook, where the imported entries can obtain the same entry IDs as in the original logbook.
The names of possible attachments are correctly imported, but not the files themselves. These you have to copy by hand.

66166

Thu Jan 22 09:30:13 2009

Re: Import csv with another date

Michael Dannmeyer wrote:

Hello,

i have problems with importing csv files. What i want to do is the following:

Import a list of log entries from a csv file with another date like the actual date

I tried to do this but the only thing which happend was that all the entries have the actual date in elog. Then i created a seperate Date column in the csv file an tried to import this.

It worked but in the default date column i have the import date and in a second date column i have the date from the csv file.

Is there a chance to get the csv column imported in the standard Date field?

Or is there a possibility to hide/supress the default date field and only display the imported date field?

Thanks

Michael

Importing dates from CSV files was not implemented for a good reason: There are dozens of date formats (such as "1/22/09", "Jan 1 2009", "Mon 1 January '09") and it is almost impossible to handle all formats. I changed now the code to catch at least some formats, such as the internal RFC2822 compliant date which is also used internall by elog. An example of this format is "Thu, 22 Jan 2009 09:26:00". This date format will also be used if you export a logbook via a CSV file. Another format I added is "1/22/09". So give a try to the new code (I made an intermediate release for windows V2.7.5-3) and see if it works for you.

67226

Mon Apr 2 15:48:25 2012

Ben wrote:

I am trying to import a CSV file in to a logbook. The Attributes seem to import fine but it kicks out the first 2 columns of data and shifts the data over to the left by 2 columns. Has anyone tried to do this?

The CSV file must be wrongly formatted. But I don't see it I can't tell you what's wrong.

67228

Mon Apr 2 16:07:48 2012

Stefan Ritt wrote:

Ben wrote:

The CSV file must be wrongly formatted. But I don't see it I can't tell you what's wrong.

Here is an example of the CSV I am trying to import.

Attachment 1: _Universal_SIM_tracker-test.csv

SIM #,Mobile #,Type,Activated,Supported in S/W,Location,Login,Administration ,Access Point Name (APN),Username/password
8901258000000000,882800000589,Jasper,Y,Y,Lab,http://att.com/,cesmart/test,M2M,[blank]/[blank]
8901158000000000,882800000576,Jasper,Y,Y,,http://att.com/,cesmart/test,M2M,[blank]/[blank]
8901158000000000,882350000577,Jasper,Y,Y,Randy,http://att.com/,cesmart/test,M2M,[blank]/[blank]

67229

Mon Apr 2 17:06:33 2012

Ben wrote:

Stefan Ritt wrote:

Ben wrote:

The CSV file must be wrongly formatted. But I don't see it I can't tell you what's wrong.

Here is an example of the CSV I am trying to import.

Thanks for reporting this bug. I fixed it now in SVN revision 2446.

Goto page Previous 1, 2, 3 ... 455, 456, 457 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6