I haven't found anything in the forums about this. Apologies if its a duplicate.

I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work. 

Currently looking to do some updates to one of the instances with the Date Type setting.

We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.

Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).

However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.

Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?

Syntax manual didn't help much for this issue.

 Tried using the Time format setting, however I only want the time to be selected, so when i enter the datetime type it shows the date and time.

If there was a way to just have the time to be drop down menus vs the date and time all together, I would find that helpful.

As for the "$entry time" suggestion, it only serves to log the exact time the entry was made into elog. Where as I want it to be manually set.

In this example we've created an sql script to pull information from an oracle database, which then creates an elog entry.

We have multiple fields which are populated and locked so only admin can edit them.

Our contractor then edits the entry with a date / time / location, and a few other things.

the Date and Time are separate attributes. We'd prefer to keep it like that just because of the other scripts that run on the elog entries, (pulls day by day reports and formats and calculates summaries in excel automatically).

Any other suggestions would be helpful.

Thanks for your reply.

Hello All,

The subject is roughly what i'm asking about so here are the details. I have combed through the forums for an answer and didn't come up with anything regarding what i need.

Issue:

Below is what the logbook is setup as. However once there are more than 10 entries on the page, when a user views the logbook, elog automatically puts them to the higher value page # (ie entry number 11 is on page 2).

As I am sorting the entries by status and by Dist or Beat to organize entries for quicker viewing and access, I would prefer that elog always shows on page 1 when a user views the log book. The statuses are setup for sorting properly but when reverse sort is turned on, status "3-Closed" appears at the top instead of status "1-Open" to appear at the top, Status "2-Sent to Next Shift" next, then "3-Closed" after that.

Is there a to just view page 1 without doing the reverse sort?

Theme = default
Page Title = ELOG - $logbook
Entries per page = 10
Attributes = Entered By, Call Type, Date/Time Reported, Customer Name, Customer Phone Number, Location, Dist or Beat, Description, Badge, Updated By, Action Taken, Report Time, Status
List Display = Entered By, Call Type, Date/Time Reported, Customer Name, Location, Dist or Beat, Description, Badge, Updated By, Status
Locked Attributes = Entered By, Updated By
Preset Entered By = $long_name
Preset on edit Updated By = $long_name
Options Status = 1-Open, 2-Sent to Next Shift, 3-Closed
Preset Status = 1-Open
Cell Style Status 1-Open = background-color:red
Cell Style Status 2-Sent to Next Shift = background-color:yellow
Cell Style Status 3-Closed = background-color:green
Type Date/Time Reported = Datetime
Type Customer Phone Number = numeric
Type Report Time = Datetime
Sort Attributes = Status, Dist or Beat
Reverse sort = 0
Use Lock = 0
Summary lines = 0
Self Register = 0

Thanks in advance.

G

 Well it would appear i answered my own problem.

Start page = page1

 G'day everyone.

Looking for some input on this idea.

I work for an organization which uses elog extensively for day to day operations.

In several of our logbooks we use a "location" attribute where we would enter an address or intersection.

I am working with the google places api and am able to create the auto complete form in a separate html page, but am interested if anyone has a good direction how i could change the input box into the google map autocomplete search box.

I have the code already for the api search box. but when i add it to the config it doesn't really do anything different.

Attached is the html file i setup with the api code.

the autocomplete works great, now i just want it to work in elog.

Any help is much appreciated!

And perhaps the Elog Powers that be might be interested in making it a function down the road? :)

 Hello, you can use the "Deny" flag in the config file for each logbook.

Deny <function> = <user>

Example: Deny Edit = Gian

simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.

Hope that helps.

Elog Syntax guide is helpful for this stuff too.

 I haven't found a specific way to block viewing a log book. 

I use the top groups settings to keep users in the logbooks they only need access to.

Example

Top Group = Logbook Group1, Logbook Group 2

Group Logbook Group 1 = Logbook1, Logbook2

Group Logbook Group 2 = Logbook3, Logbook4

Then only assign users for logbook1 and logbook2 that you wish to view those logbooks only. They would have to go to the specific top group url in order to view the logbooks.

Then you can go to http://elogurl/(top group)/

And essentially just have the users view the only logbooks they are assigned to.

> On many of my logbooks when I specify the menu commands to appear i will get one, usually 'List', which has a
> link not back to the logbook itself but to the root of the elog web server i.e. http:/hostname.domain:8080 
> But nothing will respond without the logbook name after the port number.  This also seems to be happening to the
> "back" submit button.  I can't seem to figure out how to address it.  Suggestions?

Can you show us your config? I had this issue when i was initially trying to integrate elog with apache.